agent-builder

Create standardized Claude Code agent definitions with YAML frontmatter and workflows.

37|4|Updated Dec 6, 2025
One-click install
npx skills add https://github.com/mike-coulbourn/claude-vibes --skill agent-builder-mike-coulbourn
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: agent-builder
Source: https://github.com/mike-coulbourn/claude-vibes/tree/main/plugins/vibes/skills/agent-builder
Command: npx skills add https://github.com/mike-coulbourn/claude-vibes --skill agent-builder-mike-coulbourn

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill guides users through the process of creating effective Claude Agents (subagents) that activate reliably and perform complex tasks. It provides a structured approach to agent design, ensuring they are discoverable, well-behaved, and follow best practices, eliminating guesswork and debugging frustration.

Core Features & Use Cases

  • Guided Agent Creation: Follow a step-by-step workflow from requirements gathering to testing for robust agent development.
  • Description Optimization: Learn to craft discoverable descriptions that ensure your agents activate for the right tasks and user prompts.
  • Tool & Model Management: Understand how to assign specific tools and select appropriate models (e.g., Sonnet, Haiku) for optimal agent performance.
  • Use Case: You need an agent to review code for security vulnerabilities. This skill helps you define the agent's role, specify the tools it needs (like Read, Grep, Bash(git diff:*)), choose the best model for security analysis, and craft a description that triggers it when you ask for a "security review."

Quick Start

Ask the agent-builder to help you create a new agent for reviewing code quality.

Frequently Asked Questions about agent-builder

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create a Claude Agent that activates for the right tasks?

Claude Agents activate based on their descriptions and assigned tools. Craft a clear, task-focused description that matches user queries, define the specific tools the agent needs (like Read, Grep, or Bash), and select an appropriate model. The agent-builder Skill guides you through defining these discovery-optimized components so it triggers reliably when users ask for that task.

What's the best way to design an agent for a specific problem like security review?

Agent design follows a structured workflow: gather requirements, define the agent's role and scope, specify the tools it needs, choose an appropriate model (Sonnet for complex reasoning, Haiku for speed), and craft a discoverable description. The agent-builder Skill walks you through each phase, from initial design to testing, ensuring your agent handles the task effectively.

How do I assign tools and choose the right model for my Claude Agent?

Tool assignment depends on what your agent needs to accomplish. Specify exact tools in your agent configuration (e.g., `Read`, `Grep`, `Bash(git diff:*)` for security analysis). Select the model based on task complexity and latency requirements—Sonnet for sophisticated analysis, Haiku for faster, simpler tasks. The agent-builder Skill helps you match both to your use case.

What YAML fields do I need to define when building a Claude Agent?

Claude Agents require YAML frontmatter with name, description, tools, model, permissionMode, and skills fields. The agent-builder Skill provides templates and guidance for each field, showing you how to structure them so your agent integrates properly, activates for the right prompts, and delegates tasks correctly.

Can I use Claude Agents to create subagents that handle specific workflows?

Yes. Claude Agents support multi-phase workflows and Task tool delegation to subagents. Configure each subagent with its own tools, model, and description, then orchestrate them through your parent agent. The agent-builder Skill covers the full design process, including how to set up subagent coordination and ensure reliable task handoff.

What are common mistakes when writing agent descriptions?

Descriptions that are too vague or generic fail to activate reliably. Avoid ambiguous language; be specific about the agent's scope, the problems it solves, and the tasks it handles. Use domain vocabulary that matches user queries. The agent-builder Skill teaches description optimization techniques so your agent activates for the right user prompts and behaves predictably.