agent-development

Create and validate autonomous agent configurations for Claude Code plugins.

1|Updated Jul 6, 2015
One-click install
npx skills add https://github.com/ksolomon/dotfiles --skill agent-development-ksolomon
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: agent-development
Source: https://github.com/ksolomon/dotfiles/tree/main/AI/.claude/plugins/marketplaces/claude-plugins-official/plugins/plugin-dev/skills/agent-development
Command: npx skills add https://github.com/ksolomon/dotfiles --skill agent-development-ksolomon

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve? Building agents for Claude Code plugins requires precise frontmatter fields, triggering descriptions, and system prompt structure, and mistakes in any of these cause agents to trigger unreliably or behave unpredictably. ## Core Features & Use Cases - Agent File Authoring: Provides the complete agent markdown format with required frontmatter fields (name, description, model, color, tools) and naming/length validation rules. - Triggering Design: Guides writing prose trigger descriptions and "When to invoke" scenario sections so agents dispatch reliably for both explicit and proactive requests. - System Prompt Patterns: Supplies templates for analysis, generation, validation, and orchestration agents, plus an AI-assisted generation prompt that outputs JSON ready to convert into agent files. - Use Case: You want an agent that reviews code after each feature is written. Use this Skill to generate the agent file, define its trigger scenarios, and validate it with the included script before adding it to your plugin's agents directory. ## Quick Start Create a code review agent for my Claude Code plugin that triggers after new code is written and validate the resulting agent file.

Frequently Asked Questions about agent-development

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

FAQPage Schema
How do I create an agent for a Claude Code plugin?▼

Create a markdown file in your plugin's agents directory with YAML frontmatter containing name, description, model, and color fields, followed by a system prompt body. You can generate it with the AI-assisted prompt template or write it manually, then validate with the included script.

How do I write an agent description that triggers reliably?▼

Write the description as flat prose starting with "Use this agent when" followed by 2-4 named trigger scenarios, ending with a pointer to a "When to invoke" body section. Cover both explicit user requests and proactive triggering situations.

What frontmatter fields are required for Claude Code agents?▼

Agents require name (3-50 lowercase hyphenated characters), description (triggering conditions), model (inherit, sonnet, opus, or haiku), and color (blue, cyan, green, yellow, magenta, or red). The tools field is optional and restricts tool access.

Why is my Claude Code agent not triggering?▼

Triggering fails when the description lacks specific trigger scenarios, the body scenarios do not match actual user phrasings, or a more specific competing agent wins routing. Expand the scenarios in the "When to invoke" section and tighten the description prose.

How long should an agent system prompt be?▼

System prompts should be between 20 and 10,000 characters, with 500-3,000 characters recommended. Include clear responsibilities, a step-by-step process, output format definition, and edge case handling written in second person.