agent-builder
Design and build AI agents for any domain. Use when users: (1) ask to "create an agent", "build an assistant", or "design an AI system" (2) want to understand agent architecture, agentic patterns, or autonomous AI (3) need help with capabilities, subagents, planning, or skill mechanisms (4) ask about Claude Code, Cursor, or similar agent internals (5) want to build agents for business, research, creative, or operational tasks Keywords: agent, assistant, autonomous, workflow, tool use, multi-step, orchestration
Best use case
agent-builder is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Design and build AI agents for any domain. Use when users: (1) ask to "create an agent", "build an assistant", or "design an AI system" (2) want to understand agent architecture, agentic patterns, or autonomous AI (3) need help with capabilities, subagents, planning, or skill mechanisms (4) ask about Claude Code, Cursor, or similar agent internals (5) want to build agents for business, research, creative, or operational tasks Keywords: agent, assistant, autonomous, workflow, tool use, multi-step, orchestration
Teams using agent-builder should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/agent-builder/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How agent-builder Compares
| Feature / Agent | agent-builder | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Design and build AI agents for any domain. Use when users: (1) ask to "create an agent", "build an assistant", or "design an AI system" (2) want to understand agent architecture, agentic patterns, or autonomous AI (3) need help with capabilities, subagents, planning, or skill mechanisms (4) ask about Claude Code, Cursor, or similar agent internals (5) want to build agents for business, research, creative, or operational tasks Keywords: agent, assistant, autonomous, workflow, tool use, multi-step, orchestration
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
Related Guides
Best AI Skills for Claude
Explore the best AI skills for Claude and Claude Code across coding, research, workflow automation, documentation, and agent operations.
ChatGPT vs Claude for Agent Skills
Compare ChatGPT and Claude for AI agent skills across coding, writing, research, and reusable workflow execution.
Best AI Skills for ChatGPT
Find the best AI skills to adapt into ChatGPT workflows for research, writing, summarization, planning, and repeatable assistant tasks.
SKILL.md Source
# Agent Builder Build AI agents for any domain - customer service, research, operations, creative work, or specialized business processes. ## The Core Philosophy > **The model already knows how to be an agent. Your job is to get out of the way.** An agent is not complex engineering. It's a simple loop that invites the model to act: ``` LOOP: Model sees: context + available capabilities Model decides: act or respond If act: execute capability, add result, continue If respond: return to user ``` **That's it.** The magic isn't in the code - it's in the model. Your code just provides the opportunity. ## The Three Elements ### 1. Capabilities (What can it DO?) Atomic actions the agent can perform: search, read, create, send, query, modify. **Design principle**: Start with 3-5 capabilities. Add more only when the agent consistently fails because a capability is missing. ### 2. Knowledge (What does it KNOW?) Domain expertise injected on-demand: policies, workflows, best practices, schemas. **Design principle**: Make knowledge available, not mandatory. Load it when relevant, not upfront. ### 3. Context (What has happened?) The conversation history - the thread connecting actions into coherent behavior. **Design principle**: Context is precious. Isolate noisy subtasks. Truncate verbose outputs. Protect clarity. ## Agent Design Thinking Before building, understand: - **Purpose**: What should this agent accomplish? - **Domain**: What world does it operate in? (customer service, research, operations, creative...) - **Capabilities**: What 3-5 actions are essential? - **Knowledge**: What expertise does it need access to? - **Trust**: What decisions can you delegate to the model? **CRITICAL**: Trust the model. Don't over-engineer. Don't pre-specify workflows. Give it capabilities and let it reason. ## Progressive Complexity Start simple. Add complexity only when real usage reveals the need: | Level | What to add | When to add it | |-------|-------------|----------------| | Basic | 3-5 capabilities | Always start here | | Planning | Progress tracking | Multi-step tasks lose coherence | | Subagents | Isolated child agents | Exploration pollutes context | | Skills | On-demand knowledge | Domain expertise needed | **Most agents never need to go beyond Level 2.** ## Domain Examples **Business**: CRM queries, email, calendar, approvals **Research**: Database search, document analysis, citations **Operations**: Monitoring, tickets, notifications, escalation **Creative**: Asset generation, editing, collaboration, review The pattern is universal. Only the capabilities change. ## Key Principles 1. **The model IS the agent** - Code just runs the loop 2. **Capabilities enable** - What it CAN do 3. **Knowledge informs** - What it KNOWS how to do 4. **Constraints focus** - Limits create clarity 5. **Trust liberates** - Let the model reason 6. **Iteration reveals** - Start minimal, evolve from usage ## Anti-Patterns | Pattern | Problem | Solution | |---------|---------|----------| | Over-engineering | Complexity before need | Start simple | | Too many capabilities | Model confusion | 3-5 to start | | Rigid workflows | Can't adapt | Let model decide | | Front-loaded knowledge | Context bloat | Load on-demand | | Micromanagement | Undercuts intelligence | Trust the model | ## Resources **Philosophy & Theory**: - `references/agent-philosophy.md` - Deep dive into why agents work **Implementation**: - `references/minimal-agent.py` - Complete working agent (~80 lines) - `references/tool-templates.py` - Capability definitions - `references/subagent-pattern.py` - Context isolation **Scaffolding**: - `scripts/init_agent.py` - Generate new agent projects ## The Agent Mindset **From**: "How do I make the system do X?" **To**: "How do I enable the model to do X?" **From**: "What's the workflow for this task?" **To**: "What capabilities would help accomplish this?" The best agent code is almost boring. Simple loops. Clear capabilities. Clean context. The magic isn't in the code. **Give the model capabilities and knowledge. Trust it to figure out the rest.**
Related Skills
mcp-builder
Build MCP (Model Context Protocol) servers that give Claude new capabilities. Use when user wants to create an MCP server, add tools to Claude, or integrate external services.
Process PDF files - extract text, create PDFs, merge documents. Use when user asks to read PDF, create PDF, or work with PDF files.
code-review
Perform thorough code reviews with security, performance, and maintainability analysis. Use when user asks to review code, check for bugs, or audit a codebase.
mcp-builder
Create MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. The quality of an MCP server is measured by how well it enables LLMs to accomplish real-world tasks.
browser-extension-builder
Expert in building browser extensions that solve real problems - Chrome, Firefox, and cross-browser extensions. Covers extension architecture, manifest v3, content scripts, popup UIs, monetization strategies, and Chrome Web Store publishing.
Go-to-Market Strategy Builder
Build a complete GTM plan for product launches, market entries, or expansion plays. Covers positioning, channel strategy, pricing, launch timeline, and success metrics.
Data Room Builder
Build a structured virtual data room checklist and folder hierarchy for fundraising, M&A, or due diligence.
AI Governance Policy Builder
Build internal AI governance policies from scratch. Covers acceptable use, model selection, data handling, vendor contracts, compliance mapping, and board reporting.
doppel-block-builder
Place MML blocks in Doppel worlds. Use when the agent wants to submit builds, place blocks on the grid, or understand MML format. Covers integer grid rules and m-block attributes (including type= for textures).
douyin-cover-builder
这是一个面向中文创作者的 OpenClaw Skill,输入主题与人物气质后,会输出可直接用于生图模型的高质量提示词与创意说明。
agentic-mcp-server-builder
Scaffold MCP server projects and baseline tool contract checks. Use for defining tool schemas, generating starter server layouts, and validating MCP-ready structure.
process-builder
Scaffold new babysitter process definitions following SDK patterns, proper structure, and best practices. Guides the 3-phase workflow from research to implementation.