add-agent
Skill1 starsChanged 7 months agoMITView on GitHub
Create a new IronClaw agent with its own persona, config, and model
- Reads credentials
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
- chacosoldier/compabobtheir own version, first seen Oct 23, 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
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
- chacosoldier/compabob★ 34same name
- FISHers6/clawBro★ 28same name
- venkateshv1266/pi-harness★ 2same name
- axrmxv/claude-config★ 1same name
- theopengroup/rune-harness★ 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 repository9 other files it gives its agents.
- add-remote-accessSkill
- add-telegramSkill
- configureSkill
- resetSkill
- security-auditSkill
- setupSkill
- startSkill
- stopSkill
- switch-agentSkill
The file
We split this skill into the rules it gives an agent
11 rules. 0 are common, 8 are distinctive, and 3 are very specific to this project.
0
Common
Most of the 7 edited versions we read keep these.
8
Distinctive
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 8
Create an additional agent alongside the default one.
- Very specific: line 10
IMPORTANT: Use the AskUserQuestion tool for all selections.
- Distinctive: line 14
Ask the user for a name using AskUserQuestion with a few suggestions plus "Other":
- Distinctive: line 23
Use AskUserQuestion (single select):
- Distinctive: line 29
If they select "Other", show the remaining options:
- Distinctive: line 47
Use AskUserQuestion (multi-select) with question "Which capabilities should be ENABLED?":
- Very specific: line 53
All should be selected by default.
- Distinctive: line 57
Use AskUserQuestion (multi-select) with question "Which integrations do you want?":
- Distinctive: line 68
Run from the shared package directory:
- Distinctive: line 97
Conversationally: Ask the current agent to "list all agents" to see it
- Very specific: line 98
Configure: Run /configure to modify the agent's settings
“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
Create an additional agent alongside the default one. Each agent has its own persona, boundaries, memory, and optionally a different model.
IMPORTANT: Use the AskUserQuestion tool for all selections.
Step 1: Name
Ask the user for a name using AskUserQuestion with a few suggestions plus "Other":
- research-assistant — "For research and analysis tasks"
- code-reviewer — "For code review and debugging"
- content-writer — "For writing and editing"
The user can type a custom name via "Other".
Step 2: Persona
Use AskUserQuestion (single select):
- General assistant — "Good at everything"
- Developer assistant — "Code, debugging, architecture"
- Research assistant — "Thorough research, citations, analysis"
- Personal organizer — "Tasks, scheduling, reminders"
If they select "Other", show the remaining options:
- Writing assistant — "Content creation, editing"
- Data analyst — "Data exploration, SQL, visualizations"
- DevOps / SRE — "Infrastructure, deployment, monitoring"
- Product manager — "Requirements, specs, user stories"
They can also type a custom persona via "Other" on either question.
Step 3: Model
Use AskUserQuestion (single select):
- Default (same as main agent) — "Uses the model from ANTHROPIC_MODEL env var"
- Claude Haiku — "Fast and cheap, good for simple tasks (claude-haiku-4-5-20251001)"
- Claude Sonnet — "Balanced performance (claude-sonnet-4-20250514)"
- Claude Opus — "Most capable (claude-opus-4-20250514)"
Step 4: Boundaries
Use AskUserQuestion (multi-select) with question "Which capabilities should be ENABLED?":
- Run bash commands — "Execute shell commands"
- Write/edit files — "Create and modify files"
- Web search — "Search the internet for information"
- Read system files — "Access files outside the project directory"
All should be selected by default. Items the user deselects become false in boundaries.
Step 5: MCP Connections
Use AskUserQuestion (multi-select) with question "Which integrations do you want?":
- Memory (built-in) — "Persistent long-term memory (recommended)"
- GitHub — "Read/write GitHub issues, PRs, code. Requires GITHUB_TOKEN in .env."
- Sentry — "Read Sentry issues/events. Requires SENTRY_AUTH_TOKEN in .env."
- Slack — "Coming soon"
- Google Calendar — "Coming soon"
If the user selects GitHub or Sentry, check .env for the matching token (GITHUB_TOKEN / SENTRY_AUTH_TOKEN). If missing, tell the user the token needs to be added before the agent will actually use that MCP — IronClaw will log a warning and skip the server at runtime. Do NOT block agent creation; the connection stays in config and starts working the moment the token is set.
Step 6: Create
Run from the shared package directory:
cd packages/shared && node --env-file=../../.env --import tsx/esm -e "
import { agentRepo } from './src/index.js';
const tenant = await agentRepo.findOrCreateDefaultTenant();
await agentRepo.createAgent(tenant.id, 'AGENT_NAME', {
persona: 'CHOSEN_PERSONA',
customPersona: 'CUSTOM_OR_UNDEFINED',
boundaries: {
allowBash: BOOL,
allowFileWrites: BOOL,
allowWebSearch: BOOL,
allowSystemFiles: BOOL
},
mcpConnections: MCP_CONNECTIONS_ARRAY,
model: 'MODEL_OR_UNDEFINED'
});
console.log('Agent created!');
process.exit(0);
"Replace placeholder values with the user's actual choices. Omit customPersona and model if not applicable.
Step 7: Confirm
Show the created agent's config. Explain how to use it:
- CLI:
pnpm start -- --agent AGENT_NAME - Conversationally: Ask the current agent to "list all agents" to see it
- Configure: Run
/configureto modify the agent's settings
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.

