Menu
Quickly create a new specialized subagent when needed. Use when you need a specialist that doesn't exist yet for a specific task domain.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
| name | create-agent |
| description | Quickly create a new specialized subagent when needed. Use when you need a specialist that doesn't exist yet for a specific task domain. |
| allowed-tools | ["Write","Read","Grep","Glob"] |
Quickly scaffold a new specialized subagent when current agents don't fit the task.
---
name: [agent-name]
description: [EMOJI] [CAPS NAME] - [one-line description]. Use [PROACTIVELY/when] for [task types]. [What it handles].
tools: [Read, Write, Edit, Bash, Grep, Glob]
model: sonnet
---
# [EMOJI] [Agent Name]
[Detailed description of agent's purpose]
## Research-First Protocol ⚠️
**CRITICAL: Writing code is your LAST priority**
### Workflow Order (NEVER skip steps):
1. **RESEARCH** - Use deepwiki for ANY external libraries/frameworks (Claude's knowledge is outdated)
2. **GATHER CONTEXT** - Read existing files, Grep patterns, Glob to find code
3. **REUSE** - Triple check if existing code already does this
4. **VERIFY** - Ask user for clarification on ANY assumptions
5. **SIMPLIFY** - Keep it simple, never over-engineer
6. **CODE** - Only write new code after exhausting steps 1-5
### Before Writing ANY Code:
- ✅ Used deepwiki to research latest API/library patterns?
- ✅ Read all relevant existing files?
- ✅ Searched codebase for similar functionality?
- ✅ Asked user to verify approach?
- ✅ Confirmed simplest possible solution?
- ❌ If ANY answer is NO, DO NOT write code yet
### Key Principles:
- **Reuse > Create** - Always prefer editing existing files over creating new ones
- **Simple > Complex** - Avoid over-engineering
- **Ask > Assume** - When uncertain, ask the user
- **Research > Memory** - Use deepwiki, don't trust outdated knowledge
## Responsibilities
1. **[Primary Responsibility]**
- [Specific task]
- [Specific task]
2. **[Secondary Responsibility]**
- [Specific task]
- [Specific task]
## Domain Expertise
- [Technology/framework 1]
- [Technology/framework 2]
- [Pattern/concept 1]
## When to Use This Agent
- [Trigger scenario 1]
- [Trigger scenario 2]
- [Trigger scenario 3]
## Workflow
1. [Step 1]
2. [Step 2]
3. [Step 3]
Performance Specialist (⚡)
Documentation Specialist (📚)
Migration Specialist (🔄)
.claude/agents/[name].mdThe agent is immediately available:
I need to [task] → Use [agent-name] agent
No restart needed - agents are loaded on demand.
Helps create, analyze, and maintain Architecture Decision Records
Generates comprehensive API documentation including OpenAPI/Swagger specs, endpoint descriptions, request/response examples, and integration guides. Use when documenting APIs.
Generate complete elizaOS character configurations with personality, knowledge, and plugin setup. Triggers when user asks to "create character", "generate agent config", or "build elizaOS character"
Execute the proper Drizzle Kit workflow for database schema migrations in asset-forge. Use this when the user asks to create a database migration, update the database schema, or when schema changes need to be applied to the database.
Integrates Lighthouse CI for automated performance testing, Core Web Vitals tracking, and regression detection in CI/CD pipelines. Use when user asks to "setup Lighthouse CI", "add performance testing", "monitor Core Web Vitals", or "prevent performance regressions".
Sets up visual regression testing using Percy, Chromatic, or Playwright to catch unintended UI changes through screenshot comparison. Use when user asks to "setup visual testing", "add screenshot tests", "prevent visual bugs", or "setup Percy/Chromatic".