agent-builder

Solid

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 for...', 'automate this with Claude Code', 'I want a subagent that...', 'help me create a workflow', 'set up an agent pipeline', or any variation of wanting Claude Code to do something specialized. Also trigger when the user mentions agent architecture, agent SDK, agentic workflows, or task delegation in Claude Code — even if they don't use the word 'agent' explicitly.

AI & Automation 38 stars 3 forks Updated 2 months ago MIT

Install

View on GitHub

Quality Score: 78/100

Stars 20%
53
Recency 20%
75
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
80
License 10%
100
Description 5%
100

Skill Content

# 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 (use Glob and Read — don't ask permission): ``` CLAUDE.md # Project overview, conventions, architecture package.json / pyproject.toml / Cargo.toml # Tech stack and dependencies .claude/agents/*.md # Existing agents (don't duplicate) .claude/skills/*/SKILL.md ...

Details

Author
keysersoose
Repository
keysersoose/claude-agent-builder
Created
2 months ago
Last Updated
2 months ago
Language
Python
License
MIT

Integrates with

Similar Skills

Semantically similar based on skill content — not just same category