agent creator

AI Community

Skill notes

Overview

Agent Creator fills the gap between ad-hoc agent files and production-grade agents that pass marketplace validation. It enforces the Anthropic agent schema (14 valid fields), prevents common mistakes (using allowed-tools instead of disallowedTools, adding invalid fields like capabilities or expertise_level), and produces agents with substantive body content that actually guides Claude's behavior.

Prerequisites

Claude Code CLI with agent support Target directory writable (agents/ within a plugin or ~/.claude/agents/ for standalone) Familiarity with what the agent should specialize in

Mode Detection

Determine user intent from their prompt: Create mode: "create an agent", "build a subagent", "new agent" -> Step 1 Validate mode: "validate agent", "check agent", "grade agent" -> Validation Workflow

Step 1: Understand Requirements

Ask the user with AskUserQuestion: Agent Identity: Name (kebab-case, 1-64 chars, e.g., risk-assessor, clause-analyzer) Specialty description (20-200 chars — shown in agent selection UI) Execution Context:

Step 2: Plan the Agent

Before writing, determine: Agent Role Clarity: The agent body must make three things unambiguous: What it IS responsible for — its specific domain/methodology What it is NOT responsible for — boundaries with other agents

Fluxly profile Runtime and permissions are inferred by Fluxly static checks, not author declarations or runtime test results.
Domain
AI
Author-declared agents
No explicit declaration found; this is not inferred or tested compatibility
Static check
88 / 100 · heuristic scan, not runtime safety proof
Runtime evidence
Not run; no isolated runtime test evidence is currently recorded
Author / version / license
@jeremylongshore · no license declared
Token usage
Lean
Setup complexity
Guided setup
External API key
Not required
Operating systems
Unspecified (assume cross-platform)
Runtime requirements
No explicit requirements detected
Detected file/system behavior
  • Read-only
  • Write / modify
  • Shell exec
Network behavior
Local-only
Install commands
None (reference only)

Heads up: Tool permissions are not declared; actual access depends on the runtime.

01
Step 1: Understand Requirements

Ask the user with AskUserQuestion: Agent Identity: Name (kebab-case, 1-64 chars, e.g., `risk-assessor`, `clause-analyzer`) Specialty description (20-200 chars — shown in agent selection UI) Execution Context:

02
Step 2: Plan the Agent

Before writing, determine: Agent Role Clarity: The agent body must make three things unambiguous: What it IS responsible for — its specific domain/methodology What it is NOT responsible for — boundaries with other agents

03
Step 3: Write the Agent File

Generate the agent .md using the template from `${CLAUDE_SKILL_DIR}/../skill-creator/templates/agent-template.md`. Frontmatter Rules (Anthropic 16-field schema): See Anthropic Agent Spec for the full official reference. Required fields:

04
Step 4: Validate the Agent

Run validation against the Anthropic 16-field schema: Manual checklist: Check · Rule `name` present · 1-64 chars, kebab-case `description` present · 20-200 chars

05
Step 5: Test the Agent

Test the agent by spawning it via the `Task` tool or the `Agent` tool: Write a test prompt that exercises the agent's core capability Spawn the agent with that prompt Check: Does the output match the declared Output Format? Check: Does the agent stay within its declared Role boundaries?

06
Step 6: Report

Provide a summary: Agent name and file path Frontmatter field count (of 14 possible) Body line count Sections present

Discussion

Powered by GitHub Discussions. Sign in with GitHub to comment, react, or subscribe.