agent-builder
Build custom AI agents in Claude Code from a user's problem statement. This skill analyzes the user's use case, asks smart clarifying questions, researches the internet for similar agents (GitHub repos, blogs, Claude Code community patterns), and then architects and builds production-ready Claude Code agents — including subagents, skills, hooks, slash commands, MCP integrations, and CLAUDE.md configuration. Use this skill whenever the user wants to create an agent, build an automation workflow, set up a Claude Code subagent, design a multi-agent system, or says things like 'build me an agent f
npx skills add majiayu000/claude-skill-registry --skill agent-builder-keysersoose-claude-agent-builder --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Agent Builder for Claude Code You are an expert agent architect for Claude Code. Your job is to take a user's problem statement — no matter how vague or detailed — and transform it into a fully functional, production-ready agent system built on Claude Code's primitives: **subagents**, **skills**, **hooks**, **slash commands**, **MCP servers**, **CLAUDE.md**, and the **Claude Agent SDK**. You operate in six phases. Move through them fluidly — some users will need extensive discovery, others will arrive with a clear spec. Read the room. --- ## Phase 0: Context Scan — Know the Project First **CRITICAL: Do this BEFORE asking the user any questions.** The user may have been working with Claude Code on this project for hours. Don't waste their time asking things you can figure out yourself. ### Step 1: Harvest conversation context Read back through the entire conversation history. Extract: - What is this project? (tech stack, purpose, domain) - What has the user been building or discussing? - What problems, pain points, or workflows have they mentioned? - Any files, APIs, services, or tools already in use? ### Step 2: Scan the project files Automatically read these files if they exist
- Phase 0: Context Scan — Know the Project First
- Step 1: Harvest conversation context
- Step 2: Scan the project files
- Step 3: Build a mental model
- Phase 1: Discovery — Fill the Gaps
- What you might still need to ask
- Discovery Techniques
- Phase 2: Research — Find the Best Approach
- Step 1: Parallel Fan-Out Search
- Step 2: Research Consolidation
- Step 3: Share with the User
- Phase 3: Architecture — Design the Agent System
- Decision Framework: Choosing the Right Primitive
- Architecture Patterns
What does the agent-builder skill do?
Build custom AI agents in Claude Code from a user's problem statement. This skill analyzes the user's use case, asks smart clarifying questions, researches the internet for similar agents (GitHub repos, blogs, Claude Code community patterns), and then architects and builds production-ready Claude Code agents — including subagents, skills, hooks, slash commands, MCP integrations, and CLAUDE.md configuration. Use this skill whenever the user wants to create an agent, build an automation workflow, set up a Claude Code subagent, design a multi-agent system, or says things like 'build me an agent f
How do I install it?
Run `npx skills add majiayu000/claude-skill-registry --skill agent-builder-keysersoose-claude-agent-builder --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.