add-agent
Skill34 starsChanged 23 days agoMITView on GitHub
Scaffold a new specialized agent for this assistant. Use for "/add-agent", "create a new agent", or "I want an agent that does X".
9 other projects use a version of this.
Adopted by
Most recently taken up by
- venkateshv1266/pi-harnesstheir own version, first seen Nov 1, 2026
- axrmxv/claude-configtheir own version, first seen Oct 13, 2026
- FISHers6/clawBrotheir own version, first seen Oct 8, 2026
- rgoerwit/ai-investment-agenttheir own version, first seen Oct 8, 2026
- mattolson/agent-sandboxtheir own version, first seen Oct 8, 2026
- microsoft/Sicotheir own version, first seen Jun 11, 2026
Other versions9 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 9
- microsoft/Sico★ 253same name
- mattolson/agent-sandbox★ 212same name
- BerriAI/litellm-skills★ 84same name
- rgoerwit/ai-investment-agent★ 71same name
- FISHers6/clawBro★ 28same name
- venkateshv1266/pi-harness★ 2same name
- axrmxv/claude-config★ 1same name
- theopengroup/rune-harness★ 1same name
- tjg37/ironclaw★ 1same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository21 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- build-listSkill
- chart-tufteSkill
- councilSkill
- design-precheckSkill
- document-exportSkill
- handoverSkill
- index-memorySkill
- log-decisionSkill
- mcp-debugSkill
- meeting-prepSkill
- memory-debtSkill
- merge-contactsSkill
- morning-briefSkill
- post-callSkill
- reflectSkill
- setupSkill
- system-auditSkill
- tasksSkill
- visual-explainerSkill
- weekly-reviewSkill
The file
We split this skill into the rules it gives an agent
4 rules. 0 are common, 2 are distinctive, and 2 are very specific to this project.
0
Common
Most of the 7 edited versions we read keep these.
2
Distinctive
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 8
Create a new agent so the assistant grows with the user's work.
- Very specific: line 17
Check for overlap: Read the existing agents in .claude/agents/.
- Very specific: line 19
Register it: Add a one-line routing rule for the new agent to the Agent Architecture & Routing section of CONSTITUTION.md.
- Distinctive: line 25
Keep the tool list minimal.
“Common” is measured: kept by at least 6 in 10 of the 7 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Add Agent
Create a new agent so the assistant grows with the user's work. This is the main way to customize the kit.
Steps
- Ask four things (one short round of questions, not an interrogation):
- Name: kebab-case, e.g.
recruitingorproduct-research. - 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. - Tools: the minimum it needs (4 to 6). Advice-only agents get read tools only:
Read, Glob, Grep, WebFetch, WebSearch. - Model:
inheritis the default (the agent follows the session's model); pinsonnetfor a cheap, high-volume agent oropusfor one that always needs hard reasoning.
- Name: kebab-case, e.g.
- 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. - Scaffold. Copy
.claude/agents/_agent-template.md.templateto.claude/agents/<name>.mdand fill it in: frontmatter, Purpose, When to use / when not to, Output format, Safety. - Register it. Add a one-line routing rule for the new agent to the Agent Architecture & Routing section of
CONSTITUTION.md. (_orchestrator-reference.mddescribes coordination patterns; it is not a list of agents.) - 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).
Principles
- The
descriptionis the routing signal. Write it as "Use for X, Y, Z", and name what it is not for. - Keep the tool list minimal. An agent with every tool routes badly.
- One agent, one job. If it needs a paragraph to describe, it is two agents.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.