$npx -y skills add chacosoldier/compabob --skill add-agentScaffold a new specialized agent for this assistant. Use for "/add-agent", "create a new agent", or "I want an agent that does X".
| 1 | # Add Agent |
| 2 | |
| 3 | Create a new agent so the assistant grows with the user's work. This is the main way to customize the kit. |
| 4 | |
| 5 | ## Steps |
| 6 | |
| 7 | 1. **Ask four things** (one short round of questions, not an interrogation): |
| 8 | - **Name** — kebab-case, e.g. `recruiting` or `product-research`. |
| 9 | - **Purpose and triggers** — what it owns, and the phrases or domains that should route to it. This becomes the `description`, which is what actually drives routing. |
| 10 | - **Tools** — the minimum it needs (4 to 6). Advice-only agents get read tools only: `Read, Glob, Grep, WebFetch, WebSearch`. |
| 11 | - **Model** — `sonnet` is the default; `opus` for genuinely hard reasoning. |
| 12 | 2. **Check for overlap.** Read the existing agents in `.claude/agents/`. If the new agent overlaps an existing one, say so and suggest either editing the existing agent or sharpening both descriptions so routing stays clean. |
| 13 | 3. **Scaffold.** Copy `.claude/agents/_agent-template.md` to `.claude/agents/<name>.md` and fill it in: frontmatter, Purpose, When to use / when not to, Output format, Safety. |
| 14 | 4. **Register it.** Add a one-line row for the new agent to `.claude/agents/_orchestrator-reference.md` and to the routing section of `CONSTITUTION.md`. |
| 15 | 5. **Test routing.** Suggest two or three prompts that should land on the new agent, and one that should *not* (to confirm it does not over-trigger). |
| 16 | |
| 17 | ## Principles |
| 18 | |
| 19 | - The `description` is the routing signal. Write it as "Use for X, Y, Z", and name what it is *not* for. |
| 20 | - Keep the tool list minimal. An agent with every tool routes badly. |
| 21 | - One agent, one job. If it needs a paragraph to describe, it is two agents. |