← ClaudeAtlas

create-agentlisted

Runs a structured interview to design a new Claude Code subagent role from scratch. MUST be used when the user says 'create an agent', 'build an agent', 'I need an agent that...', 'set up a new agent role', or describes autonomous behaviour they want to delegate. Produces the complete agent package (persona, skills, evals) and installs the agent into .claude/agents/.
talentedgeai/infinite-leverage · ★ 0 · AI & Automation · score 62
Install: claude install-skill talentedgeai/infinite-leverage
# Create Agent Skill Guide the user through designing a new Claude Code subagent role from requirements through to installation, using a five-phase process: **interview → diagram → iterate → build → install**. Do not skip phases. Do not generate any files before the workflow diagram is approved. --- ## Phase 1 — Interview Present all questions in a single message, grouped by section. Do not proceed until the user has answered each section. If an answer is vague, ask one targeted follow-up before moving on. --- **Let's design your new agent. Answer what you know — leave blanks for anything uncertain.** **1. Role basics** - What is this agent's name or role title? - In one sentence: what problem does it solve or what does it own? **2. Team & context** - Who does it work with? (names, human or AI, any contact info) - What project or repo does it operate in? **3. Workflow** - What triggers it? (a time/schedule, a human phrase, an event, or all three) - Walk me through the key phases from trigger to done — rough steps are fine - Any retry loops, escalation paths, or deadlines it must enforce? **4. Tool stack** - What tools or services should it have access to? (e.g. git CLI, GitHub MCP, Slack, Supabase, file tools, scheduled tasks) - Are any not yet connected? If so, what should it do as a fallback? **5. Data & files** - What files does it read? What files does it write or update? - Any naming conventions or formats it must follow? **6. Skills** - List the discrete th