Useful skills for agents and claws.
1,083
stars
239
commits
Python
primary language
Sep 9, 2026
updated

Shared skills for coding agents that work on OpenClaw projects.
This repo is the public canonical source for common workflows such as review
closeout and remote validation. The goal is simple: write a workflow once,
reuse it everywhere, and avoid hand-copying long SKILL.md files across every
repo. See VISION.md for catalog boundaries and admission principles.
agent-transcript: local-only, redacted PR/issue transcript provenance.autoreview: structured closeout/code-review workflow plus helper script.behavior-validator: source-blind validation of user-visible behavior against
a contract.beam: self-contained, authenticated, redacted
publication of local coding sessions to a read-only OpenClaw catalog.crabbox: Crabbox/Testbox remote validation workflow for broad or CI-parity
proof.handoff: path-free prompt handoff workflow for delegating a task to another
agent.readme-standard: house README structure, badge row, tone, and verification
gates for steipete/openclaw repos.session-viewer: local searchable HTML viewer for agent session JSONL.Repo-specific product skills should stay in the repo they describe. For example,
an acpx usage skill belongs in openclaw/acpx; a general review helper belongs
here.
Clone the repo:
git clone https://github.com/openclaw/agent-skills.git
cd agent-skills
List available skills:
scripts/install-skills --list
Preview an install without changing files:
scripts/install-skills --dry-run
Install all skills into the default agent skill directory:
scripts/install-skills
Install only selected skills:
scripts/install-skills autoreview crabbox
Install somewhere else:
scripts/install-skills --target ~/.codex/skills autoreview
Use copies instead of symlinks:
scripts/install-skills --mode copy --target ~/.agents/skills
Replace an existing installed skill:
scripts/install-skills --force autoreview
Symlinks are best for local development because changes in this checkout are immediately visible. Copies are better for portable or locked-down setups.
For Codex, symlink this repo into ~/.codex/skills:
mkdir -p ~/.codex/skills
ln -sfn "$(pwd)/skills" ~/.codex/skills/agent-skills
For Claude Code, symlink this repo into ~/.claude/skills:
mkdir -p ~/.claude
ln -sfn "$(pwd)/skills" ~/.claude/skills
If ~/.claude/skills already points at another shared skills folder, add
symlinks inside that folder instead:
ln -sfn "$(pwd)/skills/autoreview" /path/to/shared-skills/autoreview
ln -sfn "$(pwd)/skills/crabbox" /path/to/shared-skills/crabbox
Recommended one-liner for repo AGENTS.md files:
Shared agent workflows: install or symlink https://github.com/openclaw/agent-skills for `autoreview`, `crabbox`, and other common skills; do not vendor shared skills here unless this repo intentionally needs a zero-setup snapshot.
Some important repos should work for contributors who only cloned that repo and
never installed shared skills. Those repos may vendor a generated snapshot under
.agents/skills/<name>.
That snapshot is a distribution artifact, not the source of truth:
autoreview is a good candidate for a zero-setup snapshot in flagship repos
because review closeout is part of the contribution workflow. Large operational
skills should be vendored only when the repo genuinely needs them available
without setup.
skills/
agent-transcript/
SKILL.md
scripts/
autoreview/
SKILL.md
scripts/
behavior-validator/
SKILL.md
references/
beam/
README.md
SKILL.md
references/
scripts/
crabbox/
SKILL.md
handoff/
SKILL.md
session-viewer/
SKILL.md
scripts/
scripts/
install-skills
validate-skills
Each skill lives in skills/<name>/ and must contain SKILL.md. Helper scripts
belong inside that skill's scripts/ directory.
Run this after edits:
python3 -m venv .venv
. .venv/bin/activate
python -m pip install -r requirements-dev.txt
scripts/validate-skills
python3 -m py_compile scripts/install-skills scripts/install-skills.test.py scripts/validate-skills scripts/validate-skills.test.py
python3 scripts/install-skills.test.py
python3 scripts/validate-skills.test.py
bash -n skills/autoreview/scripts/test-review-harness
python3 -m py_compile skills/autoreview/scripts/autoreview skills/autoreview/scripts/test-review-harness.py skills/autoreview/scripts/autoreview_test.py
python3 -m unittest skills/autoreview/scripts/autoreview_test.py skills.autoreview.tests.test_autoreview_hardening
node --check skills/agent-transcript/scripts/agent-transcript
node --check skills/beam/scripts/beam
node --check skills/beam/scripts/beam-session.js
node --test skills/agent-transcript/scripts/agent-transcript.test.mjs skills/beam/scripts/beam.test.mjs skills/session-viewer/scripts/session-viewer.test.ts
The validator checks every skills/*/SKILL.md for YAML frontmatter plus required
name and description.
Session exports can contain sensitive conversation data. Treat session-viewer
HTML as local/private output unless it has been separately redacted and reviewed.
MIT.
Python
72.0%
TypeScript
14.5%
JavaScript
13.4%
Useful skills for agents and claws.
1,083
stars
239
commits
Python
primary language
Sep 9, 2026
updated

Shared skills for coding agents that work on OpenClaw projects.
This repo is the public canonical source for common workflows such as review
closeout and remote validation. The goal is simple: write a workflow once,
reuse it everywhere, and avoid hand-copying long SKILL.md files across every
repo. See VISION.md for catalog boundaries and admission principles.
agent-transcript: local-only, redacted PR/issue transcript provenance.autoreview: structured closeout/code-review workflow plus helper script.behavior-validator: source-blind validation of user-visible behavior against
a contract.beam: self-contained, authenticated, redacted
publication of local coding sessions to a read-only OpenClaw catalog.crabbox: Crabbox/Testbox remote validation workflow for broad or CI-parity
proof.handoff: path-free prompt handoff workflow for delegating a task to another
agent.readme-standard: house README structure, badge row, tone, and verification
gates for steipete/openclaw repos.session-viewer: local searchable HTML viewer for agent session JSONL.Repo-specific product skills should stay in the repo they describe. For example,
an acpx usage skill belongs in openclaw/acpx; a general review helper belongs
here.
Clone the repo:
git clone https://github.com/openclaw/agent-skills.git
cd agent-skills
List available skills:
scripts/install-skills --list
Preview an install without changing files:
scripts/install-skills --dry-run
Install all skills into the default agent skill directory:
scripts/install-skills
Install only selected skills:
scripts/install-skills autoreview crabbox
Install somewhere else:
scripts/install-skills --target ~/.codex/skills autoreview
Use copies instead of symlinks:
scripts/install-skills --mode copy --target ~/.agents/skills
Replace an existing installed skill:
scripts/install-skills --force autoreview
Symlinks are best for local development because changes in this checkout are immediately visible. Copies are better for portable or locked-down setups.
For Codex, symlink this repo into ~/.codex/skills:
mkdir -p ~/.codex/skills
ln -sfn "$(pwd)/skills" ~/.codex/skills/agent-skills
For Claude Code, symlink this repo into ~/.claude/skills:
mkdir -p ~/.claude
ln -sfn "$(pwd)/skills" ~/.claude/skills
If ~/.claude/skills already points at another shared skills folder, add
symlinks inside that folder instead:
ln -sfn "$(pwd)/skills/autoreview" /path/to/shared-skills/autoreview
ln -sfn "$(pwd)/skills/crabbox" /path/to/shared-skills/crabbox
Recommended one-liner for repo AGENTS.md files:
Shared agent workflows: install or symlink https://github.com/openclaw/agent-skills for `autoreview`, `crabbox`, and other common skills; do not vendor shared skills here unless this repo intentionally needs a zero-setup snapshot.
Some important repos should work for contributors who only cloned that repo and
never installed shared skills. Those repos may vendor a generated snapshot under
.agents/skills/<name>.
That snapshot is a distribution artifact, not the source of truth:
autoreview is a good candidate for a zero-setup snapshot in flagship repos
because review closeout is part of the contribution workflow. Large operational
skills should be vendored only when the repo genuinely needs them available
without setup.
skills/
agent-transcript/
SKILL.md
scripts/
autoreview/
SKILL.md
scripts/
behavior-validator/
SKILL.md
references/
beam/
README.md
SKILL.md
references/
scripts/
crabbox/
SKILL.md
handoff/
SKILL.md
session-viewer/
SKILL.md
scripts/
scripts/
install-skills
validate-skills
Each skill lives in skills/<name>/ and must contain SKILL.md. Helper scripts
belong inside that skill's scripts/ directory.
Run this after edits:
python3 -m venv .venv
. .venv/bin/activate
python -m pip install -r requirements-dev.txt
scripts/validate-skills
python3 -m py_compile scripts/install-skills scripts/install-skills.test.py scripts/validate-skills scripts/validate-skills.test.py
python3 scripts/install-skills.test.py
python3 scripts/validate-skills.test.py
bash -n skills/autoreview/scripts/test-review-harness
python3 -m py_compile skills/autoreview/scripts/autoreview skills/autoreview/scripts/test-review-harness.py skills/autoreview/scripts/autoreview_test.py
python3 -m unittest skills/autoreview/scripts/autoreview_test.py skills.autoreview.tests.test_autoreview_hardening
node --check skills/agent-transcript/scripts/agent-transcript
node --check skills/beam/scripts/beam
node --check skills/beam/scripts/beam-session.js
node --test skills/agent-transcript/scripts/agent-transcript.test.mjs skills/beam/scripts/beam.test.mjs skills/session-viewer/scripts/session-viewer.test.ts
The validator checks every skills/*/SKILL.md for YAML frontmatter plus required
name and description.
Session exports can contain sensitive conversation data. Treat session-viewer
HTML as local/private output unless it has been separately redacted and reviewed.
MIT.
Python
72.0%
TypeScript
14.5%
JavaScript
13.4%