agent-creator

Create subagent definitions for Claude Code plugins with required frontmatter fields.

5|Updated Nov 21, 2025
One-click install
npx skills add https://github.com/basher83/agent-auditor --skill agent-creator-basher83
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: agent-creator
Source: https://github.com/basher83/agent-auditor/tree/main/skills/agent-creator
Command: npx skills add https://github.com/basher83/agent-auditor --skill agent-creator-basher83

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you define two distinct types of Claude Code agents: Plugin Agents (for plugin distributions) and User/Project Agents (personal workflows). It provides required frontmatter fields, templates, and guidance for when to invoke each agent type.

Core Features & Use Cases

  • Plugin Agents: require frontmatter fields description and capabilities; located under plugins/<category>/<plugin>/agents/agent-name.md
  • User/Project Agents: require name and description; optional tools and model
  • Templates & Guidance: Provides structured templates and examples for quick-start.

Quick Start

Example: Create a plugin agent at plugins/blog/agents/code-reviewer.md with description and capabilities: ["code review","security","quality"].

Frequently Asked Questions about agent-creator

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

FAQPage Schema
How do I create a subagent definition for Claude Code?

Define a subagent by writing a markdown file with required frontmatter fields: description and capabilities for plugin agents, or name and description for user agents. Place plugin agents at plugins/<category>/<plugin>/agents/agent-name.md and include a capabilities list matching your agent's specialized functions.

What's the difference between plugin agents and user agents in Claude Code?

Plugin agents require description and capabilities fields in frontmatter and live under plugins/<category>/<plugin>/agents/. User/project agents require only name and description, with optional tools and model settings. Plugin agents standardize agents for distribution; user agents support personal workflows.

What frontmatter fields are required when defining a Claude Code agent?

Plugin agents require description and capabilities. User agents require name and description. Both support optional fields. Include agent title, capabilities list describing specialized functions, 'When to Use' guidance, and 'Context and Examples' sections to clarify invocation criteria.

Can I define custom capabilities for my Claude Code subagent?

Yes. Specify capabilities as a list in frontmatter reflecting your agent's specialized functions. Capabilities describe what the agent can perform—code review, security analysis, documentation generation—and guide when Claude Code should invoke that specific agent.

How do I structure example workflows when creating a subagent?

Include a 'Context and Examples' section showing realistic invocation scenarios. Provide example inputs and outputs demonstrating when and how the agent activates, matching your capabilities list and 'When to Use' guidance for clarity.

Do subagent definitions work with YAML frontmatter in Claude Code?

Yes. Agent definitions use YAML frontmatter to declare metadata: name, description, title, capabilities, and optional tools and model. This frontmatter standardizes how Claude Code recognizes and routes to specialized agents.