Tool roles, alternatives, selection tradeoffs, and compatibility caveats.
Agent skills: authoring & distribution (skills CLI)
John uses: the skills CLI (26.4k; npx skills add <source> --skill <name>, skills.sh) with canonical skills in ~/.agents/skills symlinked into each agent's skill dir. Section 07 even publishes an installable skill on the workshop page itself.
| Alternative | What it is | How it differs | License |
|---|---|---|---|
| anthropics/skills | Anthropic's public repository of Agent Skills | Official first-party skill collection to copy from rather than an installer CLI | none listed |
| superpowers | An agentic skills framework and software-development methodology | Opinionated bundled methodology (brainstorm→plan→implement) vs à-la-carte skill installs | MIT |
| Claude Code plugins/marketplaces (built-in) | Native plugin + marketplace system bundling skills, commands, hooks, MCP servers | First-party distribution channel; Claude-Code-only where skills.sh targets many agents | product |
| MCP servers | Model Context Protocol: distribute agent capabilities as tool servers rather than markdown skills | Tools-as-processes vs instructions-as-markdown; complementary, heavier to build | open spec (MIT) |
Pick this if…
- anthropics/skills — you want first-party, well-audited skills to copy from.
- superpowers — you want a whole opinionated methodology, not à-la-carte installs.
- Claude Code plugins — you're Claude-Code-only and want first-party distribution.
- MCP — the capability needs real code/tools, not instructions.