Short answer: keep skills in a portable registry, then project them into each harness’s native skill path. Brigade’s skills station installs reviewed skills (and optional Skillet packs) into Claude Code, Codex, Grok, Hermes, OpenClaw, and other adapters with per-harness receipts.
The problem
Every coding agent invented a slightly different place for “skills” or “slash tools.” Copying a SKILL.md into .claude/skills/ does not put it in Codex or Grok. Teams end up with half the agents missing the workflow that saved the last session.
The Brigade path
brigade skills list
brigade skills install brigade-work --target all
# or a single harness:
brigade skills install security-review --target codex
brigade skills install security-review --target grokDefault installs include the work-loop skills that feed verify → capture → handoff. Optional Skillet skills cover audits, security sweeps, releases, and more after you add the roster.
Related stations
| Job | Station / tool |
|---|---|
| Portable skills | brigade skills / Skillet |
| MCP tools | brigade mcp |
| Memory handoffs | brigade handoff (handoffs page) |
When this is enough
Use Brigade skills when you run two or more harnesses and want the same reviewed workflows everywhere. Use a single-harness plugin marketplace if you only ever use one agent CLI.
Questions
Are skills the same as MCP servers? No. Skills are instruction packs and workflows. MCP servers are tool processes. Brigade manages both, but they are different stations.
Does install overwrite my hand-edited skills? Installs write into the harness skill directories Brigade knows about and leave receipts. Prefer reviewed registry skills over unreviewed copies.
See skills docs and the Skillet product page.