SuperAPI AI Directory
Partner中文AI newsFavorites
Skillscreate-sub-agent

create-sub-agent

Agents & models

View repository

Updated 10-16 08:00

About this skill

Follow the create-sub-agent skill workflow to design and generate a Claude Code agent file.

Inputs

  • $ARGUMENTS — optional agent name or brief use-case description passed as initial context to the design interview. Omit to start with open discovery.

Steps

  1. If $ARGUMENTS is provided, use it as the starting context for agent name / purpose
  2. Follow the create-sub-agent phased workflow: extract core intent via design interview (purpose, input/output contract, escalation posture, tools, permissions.deny, model, maxTokens, color, lifecycle hooks, placement), present design summary, confirm, then generate the agent .md file
  3. Validate the generated agent with validate_agent.py
  4. Publication Check: Ask if the agent should be visible to GitHub Copilot or Claude Code for this repository. If yes, materialize it into .github/agents/ or .claude/agents/ and ensure the path is tracked in .gitignore.
  5. Report the created agent path, triggering conditions, and next steps

Output

Agent .md file with complete YAML frontmatter (name, description with <example> blocks, model, maxTokens, color, permissions.allowedTools, permissions.deny) and a second-person system prompt targeting 500-3,000 characters.

Placement Rules

Plugin agents: flat .md file — plugins/<plugin-name>/agents/<agent-name>.md

  • No subdirectory. Skills use skills/<name>/SKILL.md subdirectory format, but agents do NOT.
  • Confirmed against Anthropic official plugins (feature-dev, code-simplifier, hookify).

Local/project agents: .claude/agents/<agent-name>.md (also flat, no subdirectory).

Discovery & Publication

To make an agent visible to GitHub Copilot or Claude Code for this repository, follow the Discovery-First Publication pattern:

  1. Materialize the agent into .github/agents/ (Copilot) or .claude/agents/ (Claude).
  2. Ensure .gitignore allows the specific agent file or subdirectory.
  3. Commit the materialized file to the repository.

See Agent Discovery and Publication Pattern for details.

Edge Cases

  • If $ARGUMENTS is empty: conduct the full Phase 1 design interview — do not pre-fill
  • If an agent with that name already exists: confirm before overwriting
  • If requirements suggest multiple responsibilities: propose splitting into specialized agents
  • If high-risk operations are required: configure escalation posture and add Stop hook