Awesome-omni-skill agent-builder
Create custom Claude Code sub-agents with specialized expertise and tool access. Use when you need to build reusable agents for specific tasks like code review, debugging, data analysis, or domain-specific workflows.
git clone https://github.com/diegosouzapw/awesome-omni-skill
T=$(mktemp -d) && git clone --depth=1 https://github.com/diegosouzapw/awesome-omni-skill "$T" && mkdir -p ~/.claude/skills && cp -r "$T/skills/ai-agents/agent-builder" ~/.claude/skills/diegosouzapw-awesome-omni-skill-agent-builder && rm -rf "$T"
skills/ai-agents/agent-builder/SKILL.mdBuild Custom Claude Code Sub-Agents
When to Use
- Creating a specialized agent for recurring tasks (code review, debugging, testing)
- Need an agent with specific tool permissions or limited scope
- Want to share reusable agents across projects or with your team
- Building domain-specific agents (data science, DevOps, security)
- Need to preserve main conversation context while delegating complex tasks
What This Skill Does
Guides you through creating custom sub-agents that:
- Specialize: Focused expertise for specific domains or tasks
- Isolate: Separate context windows prevent main conversation pollution
- Reuse: Deploy across projects and share with teams
- Control: Granular tool access and model selection per agent
Quick Start
1. Use the Built-In Agent Creator
# Run the agents command /agents
Then:
- Select "Create New Agent"
- Choose project-level (
) or user-level (.claude/agents/
)~/.claude/agents/ - Generate with Claude or manually define configuration
- Save and test
2. Manual Agent Creation
Create a markdown file in
.claude/agents/ (project) or ~/.claude/agents/ (user):
--- name: my-agent-name description: Use this agent when [specific trigger condition] tools: Read, Edit, Bash model: sonnet --- # Agent System Prompt Your detailed instructions for the agent go here. Be specific about: - What tasks this agent handles - How to approach problems - What outputs to produce - Any constraints or guardrails
3. Invoke Your Agent
Automatic: Claude detects matching tasks based on description Explicit: "Use the my-agent-name agent to [task]"
Agent Configuration
Required Fields
| Field | Description | Example |
|---|---|---|
| Lowercase with hyphens | |
| When to use this agent (triggers routing) | |
Optional Fields
| Field | Description | Default |
|---|---|---|
| Comma-separated tool list | All tools inherited |
| Model alias (sonnet/opus/haiku) or 'inherit' | Inherits from main |
Agent Structure
.claude/agents/ # Project-level agents ├── code-reviewer.md ├── debugger.md └── custom-agent.md ~/.claude/agents/ # User-level agents (global) ├── my-helper.md └── data-analyzer.md
Priority: Project agents override user agents with same name
Common Agent Types
Code Reviewer
Reviews code for quality, security, and best practices
Triggers: After code changes, before commits
Debugger
Analyzes errors, identifies root causes, proposes fixes
Triggers: Test failures, runtime errors
Data Scientist
Writes SQL queries, performs analysis, generates reports
Triggers: Data questions, BigQuery tasks
See: Agent Examples
Best Practices
- Single Responsibility: One focused task per agent
- Descriptive Triggers: Use "PROACTIVELY" or "MUST BE USED" for automatic delegation
- Detailed Prompts: Specific instructions yield better results
- Limit Tools: Only grant necessary permissions
- Version Control: Commit project agents for team collaboration
Full Guide: Best Practices
Available Tools
Sub-agents can access:
- File Operations: Read, Write, Edit, Glob, Grep
- Execution: Bash
- MCP Tools: Any installed MCP server tools
Use
/agents interface to visually select tools.
Outputs
This skill helps you create:
- Agent configuration files (
with YAML frontmatter).md - Specialized system prompts
- Tool permission configurations
- Reusable agent templates
Guardrails
- Agents must have focused, well-defined purposes
- Use lowercase-with-hyphens naming convention
- Always specify clear trigger conditions in description
- Grant minimal tool access (principle of least privilege)
- Test agents thoroughly before sharing with team
Advanced Topics
- Configuration Guide - Complete field reference
- Agent Examples - Real-world templates
- Best Practices - Design patterns
- Troubleshooting - Common issues
Triggers
This skill activates when you mention:
- "create an agent" or "build an agent"
- "sub-agent" or "subagent"
- "agent configuration"
- "Task tool" or "custom agent"
- "agent best practices"
Testing
To test your agent:
# Ask Claude to use it explicitly "Use the [agent-name] agent to [task]" # Or test automatic triggering "[Describe a task matching agent's description]"
Verify:
- Agent triggers correctly
- Has necessary tool access
- Produces expected outputs
- Maintains scope/focus
Reference Documentation
- PRISM Agent Strategy - Artifact-centric agent design patterns for PRISM workflows
Last Updated: 2025-10-27 Version: 1.0.0