It does not create the skills an agent references -- for that, use skill-creator; agent-creator only wires the agent frontmatter and workflow around skills that already exist or are created alongside it.
Agent Creator
Agent Workflow (MANDATORY)
Before ANY agent creation, delegate via Agent — spawn 2 agents in parallel (single message, 2 Agent calls). Generated agents carry Agent and SendMessage in their tools, so this same pattern is what they must use internally too:
- fuse-ai-pilot:explore-codebase - Check existing agents, analyze patterns
- fuse-ai-pilot:research-expert - Fetch latest agent conventions
mcp__context7__query-docs is a direct MCP call, not a spawned agent — invoke it directly (alongside the 2 Task calls) to get examples from existing agents.
After creation, run fuse-ai-pilot:sniper for validation.
Overview
| Action |
When to Use |
| New Agent |
New domain/framework expert needed |
| Adapt |
Copy from similar agent (Next.js → React) |
| Update |
Add skills, modify hooks |
Critical Rules
- ALL content in English - Never French or other languages
- Frontmatter complete - name, description, model, tools, skills, hooks
- Agent Workflow section - Always first content section
- SOLID rules reference - Link to solid-[stack] skill
- Register in marketplace.json - Or agent won't load
- Hook scripts executable -
chmod +x
- Output Format section mandatory - Every generated agent must define a standard
## Output Format section (status, files_changed, errors, sources) — an agent invoked by a lead must return structured data, not prose
Architecture
plugins/<plugin-name>/
├── agents/
│ └── <agent-name>.md # Agent definition
├── skills/
│ ├── skill-a/
│ └── solid-[stack]/
├── scripts/
│ └── validate-*.sh # Hook scripts
└── .claude-plugin/
└── plugin.json
→ See architecture.md for details
Reference Guide
Concepts
| Topic |
Reference |
When to Consult |
| Architecture |
architecture.md |
Understanding agent structure |
| Frontmatter |
frontmatter.md |
YAML configuration |
| Required Sections |
required-sections.md |
Mandatory content |
| Hooks |
hooks.md |
Pre/Post tool validation |
| Registration |
registration.md |
marketplace.json |
Templates
| Template |
When to Use |
| agent-template.md |
Creating new agent |
| hook-scripts.md |
Validation scripts |
Quick Reference
Create New Agent
# 1. Research existing agents
→ explore-codebase + research-expert
# 2. Create files
touch plugins/<plugin>/agents/<agent-name>.md
touch plugins/<plugin>/scripts/validate-<stack>-solid.sh
chmod +x plugins/<plugin>/scripts/*.sh
# 3. Register in marketplace.json
# 4. Validate
→ sniper
Adapt Existing Agent
# 1. Copy similar agent
cp plugins/nextjs-expert/agents/nextjs-expert.md plugins/new-plugin/agents/new-expert.md
# 2. Adapt with sed
sed -i '' "s/nextjs/newstack/g; s/Next\.js/NewStack/g" agents/new-expert.md
# 3. Update skills, tools, register
Validation Checklist
Related: Skill Creator
When creating an agent, you often need to create skills too.
Use /fuse-ai-pilot:skill-creator to create skills for the agent:
| Scenario |
Action |
| New agent needs skills |
Create skills with skill-creator first |
| Agent references skills |
Ensure skills exist in skills/ |
| Adapting agent |
Adapt related skills too |
Best Practices
DO
- Use skill-creator for associated skills
- Reference solid-[stack] skill for SOLID rules
- Include Gemini Design section for UI agents
- Make hook scripts executable
DON'T
- Write in French (English only)
- Skip Agent Workflow section
- Forget marketplace registration
- Create agent without its skills
- Hard-code paths in hooks (use
$CLAUDE_PLUGIN_ROOT)
1---2name: agent-creator3description: Use when creating expert agents. Generates agent.md with frontmatter, hooks, required sections, and skill references.4---56<objective>7Agent Creator scaffolds a complete Claude Code expert agent: frontmatter (name, description, model, tools, skills, hooks), the mandatory Agent Workflow section, hook scripts, and marketplace registration. It covers three flows -- creating a brand-new domain/framework expert, adapting an existing agent to a new stack, and updating an agent's skills or hooks -- each ending with a `fuse-ai-pilot:sniper` validation pass.89It does not create the skills an agent references -- for that, use `skill-creator`; agent-creator only wires the agent frontmatter and workflow around skills that already exist or are created alongside it.10</objective>1112# Agent Creator1314## Agent Workflow (MANDATORY)1516Before ANY agent creation, delegate via `Agent` — spawn 2 agents in parallel (single message, 2 `Agent` calls). Generated agents carry `Agent` and `SendMessage` in their tools, so this same pattern is what they must use internally too:17181. **fuse-ai-pilot:explore-codebase** - Check existing agents, analyze patterns192. **fuse-ai-pilot:research-expert** - Fetch latest agent conventions2021`mcp__context7__query-docs` is a direct MCP call, not a spawned agent — invoke it directly (alongside the 2 Task calls) to get examples from existing agents.2223After creation, run **fuse-ai-pilot:sniper** for validation.2425---2627## Overview2829| Action | When to Use |30|--------|-------------|31| **New Agent** | New domain/framework expert needed |32| **Adapt** | Copy from similar agent (Next.js → React) |33| **Update** | Add skills, modify hooks |3435---3637## Critical Rules38391. **ALL content in English** - Never French or other languages402. **Frontmatter complete** - name, description, model, tools, skills, hooks413. **Agent Workflow section** - Always first content section424. **SOLID rules reference** - Link to solid-[stack] skill435. **Register in marketplace.json** - Or agent won't load446. **Hook scripts executable** - `chmod +x`457. **Output Format section mandatory** - Every generated agent must define a standard `## Output Format` section (status, files_changed, errors, sources) — an agent invoked by a lead must return structured data, not prose4647---4849## Architecture5051```52plugins/<plugin-name>/53├── agents/54│ └── <agent-name>.md # Agent definition55├── skills/56│ ├── skill-a/57│ └── solid-[stack]/58├── scripts/59│ └── validate-*.sh # Hook scripts60└── .claude-plugin/61 └── plugin.json62```6364→ See [architecture.md](references/architecture.md) for details6566---6768## Reference Guide6970### Concepts7172| Topic | Reference | When to Consult |73|-------|-----------|-----------------|74| **Architecture** | [architecture.md](references/architecture.md) | Understanding agent structure |75| **Frontmatter** | [frontmatter.md](references/frontmatter.md) | YAML configuration |76| **Required Sections** | [required-sections.md](references/required-sections.md) | Mandatory content |77| **Hooks** | [hooks.md](references/hooks.md) | Pre/Post tool validation |78| **Registration** | [registration.md](references/registration.md) | marketplace.json |7980### Templates8182| Template | When to Use |83|----------|-------------|84| [agent-template.md](references/templates/agent-template.md) | Creating new agent |85| [hook-scripts.md](references/templates/hook-scripts.md) | Validation scripts |8687---8889## Quick Reference9091### Create New Agent9293```bash94# 1. Research existing agents95→ explore-codebase + research-expert9697# 2. Create files98touch plugins/<plugin>/agents/<agent-name>.md99touch plugins/<plugin>/scripts/validate-<stack>-solid.sh100chmod +x plugins/<plugin>/scripts/*.sh101102# 3. Register in marketplace.json103104# 4. Validate105→ sniper106```107108### Adapt Existing Agent109110```bash111# 1. Copy similar agent112cp plugins/nextjs-expert/agents/nextjs-expert.md plugins/new-plugin/agents/new-expert.md113114# 2. Adapt with sed115sed -i '' "s/nextjs/newstack/g; s/Next\.js/NewStack/g" agents/new-expert.md116117# 3. Update skills, tools, register118```119120---121122## Validation Checklist123124- [ ] ALL content in English125- [ ] Frontmatter complete (name, description, model, tools, skills)126- [ ] Agent Workflow section present127- [ ] Mandatory Skills Usage table128- [ ] SOLID Rules reference to solid-[stack]129- [ ] Local Documentation paths valid130- [ ] Output Format section present (status, files_changed, errors, sources)131- [ ] Hook scripts executable132- [ ] Registered in marketplace.json133134---135136## Related: Skill Creator137138**When creating an agent, you often need to create skills too.**139140Use **`/fuse-ai-pilot:skill-creator`** to create skills for the agent:141142| Scenario | Action |143|----------|--------|144| New agent needs skills | Create skills with skill-creator first |145| Agent references skills | Ensure skills exist in skills/ |146| Adapting agent | Adapt related skills too |147148---149150## Best Practices151152### DO153- Use skill-creator for associated skills154- Reference solid-[stack] skill for SOLID rules155- Include Gemini Design section for UI agents156- Make hook scripts executable157158### DON'T159- Write in French (English only)160- Skip Agent Workflow section161- Forget marketplace registration162- Create agent without its skills163- Hard-code paths in hooks (use `$CLAUDE_PLUGIN_ROOT`)