agent-creator_skill

This skill helps you create structured agent definitions for Claude Code, including plugin and user agents, with frontmatter, capabilities, and usage examples.
  • Python

4

GitHub Stars

1

Bundled Files

2 months ago

Catalog Refreshed

4 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill basher83/agent-auditor --skill agent-creator

  • SKILL.md5.7 KB

Overview

This skill creates well-formed subagent definitions for Claude Code, producing either plugin-distributed agents or personal .claude agents with correct frontmatter and structure. It guides naming, capability selection, invocation criteria, and provides ready-to-drop markdown templates and examples. Use it to add specialized subagents to plugins or to your local agent collection.

How this skill works

It asks whether the agent is for a plugin or personal use, collects the agent purpose and capabilities, and generates a kebab-case name and YAML frontmatter matching the required format. For plugin agents it includes description and capabilities array; for user agents it includes name, description, optional tools and model, and a system prompt guideline. It also outputs sections: capabilities, when-to-use criteria, and context/examples demonstrating invocation.

When to use it

  • When you ask to create, write, or generate an agent or subagent for Claude Code
  • When adding a specialized agent to a Claude Code plugin and you need correct frontmatter and capabilities
  • When you want a personal .claude agent with name, tools, and model hints
  • When you need invocation criteria and concrete examples so Claude knows when to call the agent
  • When you want a ready markdown template with title, sections, and examples

Best practices

  • Decide plugin vs personal agent up front — plugin agents require a capabilities array, user agents require a name and can list tools
  • Keep agents narrowly focused: 3–5 concrete capabilities describing specific actions or outputs
  • Provide clear invocation criteria so Claude can decide when to invoke rather than handle tasks itself
  • Use kebab-case for agent filenames and identifiers (e.g., security-reviewer)
  • Include real context/examples showing typical user requests and expected agent responses

Example use cases

  • Create a plugin agent 'security-reviewer' that inspects code diffs for vulnerabilities and recommends fixes
  • Generate a personal agent 'performance-tester' in .claude for designing and analyzing load tests with specified tools
  • Add an 'api-documenter' agent to a plugin that extracts OpenAPI fragments and drafts endpoint docs
  • Produce frontmatter and full markdown for an agent that Claude can invoke when a user asks for specialized legal or compliance checks
  • Provide invocation criteria examples so Claude calls the agent only for security, performance, or documentation requests, not general questions

FAQ

Use a plugin agent when you intend to distribute the agent with a plugin for team/community use. Use a user agent (.claude/agents) for personal or project-specific workflows.

What fields are mandatory for plugin agents?

Plugin agents must include frontmatter with description and a capabilities array, an H1 title, a Capabilities section, When to Use criteria, and Context and Examples.

Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational
agent-creator skill by basher83/agent-auditor | VeilStrat