Portable skills across coding agents
You want the same SKILL.md workflows available in every coding agent without hand-copying skill folders.
Updated November 15, 2026
Short answer: keep skills in a portable registry, then project them into each harness’s native skill path. BrigadeStack’s skills component installs reviewed skills (and optional Skillet packs) into Claude Code, Codex, Grok, Hermes, OpenClaw, and 14 other harness adapters, with install history and rollback snapshots per harness.
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 BrigadeStack path
brigadestack skills adapters list # the harness skill paths it knows
brigadestack skills install brigade-work --target all
# or a single harness:
brigadestack skills install security-review --target codex
brigadestack skills install security-review --target grok
brigadestack skills fleet status # which installed copies are current, stale, or missing
Default 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 components
| Job | Component / tool |
|---|---|
| Portable skills | brigadestack skills / Skillet |
| MCP tools | brigadestack mcp |
| Memory handoffs | brigadestack handoff (handoffs page) |
When this is enough
Use BrigadeStack 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. BrigadeStack manages both, but they are different components.
Does install overwrite my hand-edited skills? Installs write into the harness skill directories BrigadeStack knows about, refuse to overwrite an existing copy without --force, and are recorded in brigadestack skills history. brigadestack skills rollback <skill> --target <harness> restores the snapshot taken before the last forced reinstall of that skill. Prefer reviewed registry skills over unreviewed copies.
See skills docs and the Skillet product page.