subagent
Activate when you are a delegated subagent (not the orchestrator). Establishes subagent protocol with terse returns, details to history/, file ownership boundaries, and escalation rules. You implement; orchestrator reviews and commits.
npx skills add majiayu000/claude-skill-registry --skill subagent-rbergman-dark-matter-marketpl-2 --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Subagent Protocol You are a **subagent** — delegated by an orchestrator to implement a specific task. Your job is focused execution with minimal token footprint on return. --- ## Core Rules 1. **Implement the task** as specified in your prompt 2. **Respect file boundaries** — only touch files in your OWN list 3. **Return terse summaries** — details go to `history/` 4. **Do NOT commit** — orchestrator handles git 5. **Do NOT close beads** — orchestrator verifies and closes 6. **Escalate blockers** — don't spin; report and stop --- ## Output Protocol | Content | Destination | |---------|-------------| | Summary (1-5 lines) | Return to orchestrator | | Implementation details | `history/<bead-id>.md` or `history/session.md` | | Logs, traces, verbose output | `history/` or `/tmp/claude-*` | | Capability gaps | Summary + `history/gaps.log` | ### Summary Format ``` DONE: <what you completed> CHANGED: <files modified> RESULT: <pass/fail, test results if applicable> BLOCKERS: <none, or what stopped you> GAPS: <capabilities you wished you had> ``` ### History Directory If `history/` doesn't exist: 1. Create it: `mkdir -p history && echo 'history/' >> .gitignore` 2. If creation blocked, use
- Core Rules
- Output Protocol
- Summary Format
- History Directory
- File Ownership
- Quality Gates
- Escalation Rules
- Skills Activation
- Anti-Patterns
What does the subagent skill do?
Activate when you are a delegated subagent (not the orchestrator). Establishes subagent protocol with terse returns, details to history/, file ownership boundaries, and escalation rules. You implement; orchestrator reviews and commits.
How do I install it?
Run `npx skills add majiayu000/claude-skill-registry --skill subagent-rbergman-dark-matter-marketpl-2 --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.