Agent Creator

Creates spec-compliant agent .md files following Anthropic's current documented subagent frontmatter contract. Supports both creation of new agents and validation of existing ones.

Overview

Agent Creator fills the gap between ad-hoc agent files and production-grade agents that pass marketplace validation. It distinguishes the 16 fields in Anthropic's public frontmatter table from runtime-recognized experimental options, then layers the stricter Intent Solutions required set on top. It 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.

Key difference from skill-creator: agents support both tools (allowlist) AND disallowedTools (denylist). Skills use allowed-tools (allowlist) and, since schema 3.7.0, an optional kebab-case disallowed-tools denylist — a parallel field, not a unification. Agents also support effort, maxTurns, skills, memory, isolation, permissionMode, background, color, and initialPrompt. These controls have context-specific support; effort also exists on skills. Do not assume agent field spellings or constraints apply to skills. Claude Code also recognizes a separately labeled runtime experimental object; do not present it as part of the public 16-field table. The agent body becomes the system prompt that drives the subagent — it does NOT receive the full Claude Code system prompt.

Field-naming warning: Agents use camelCase disallowedTools: (canonical sub-agents spec); skills use kebab-case disallowed-tools: (schema 3.7.0+). The validator rejects either mismatch — never copy-paste between agent and skill frontmatter without renaming.

Authentication

Authoring and static validation do not require provider credentials. Generated workflows have their own authentication requirements. Use only the requested scope and existing authorization for any model/provider execution.

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

Instructions

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", "g…

Skill Creator

Creates complete, spec-compliant skill packages following AgentSkills.io and Anthropic standards. Supports both creation and validation workflows with 100-point marketplace grading.

Overview

Skill Creator solves the gap between writing ad-hoc agent skills and producing marketplace-ready packages that score well on the Intent Solutions 100-point rubric. It enforces the 2026 spec (top-level identity fields, ${CLAUDE_SKILL_DIR} paths, scored sections) and catches contradictions that would cost marketplace points. Supports create, validate, forge and reforge modes, loading their details only when selected.

Prerequisites

• A known target location, workflow and authoring authority.
• The target's canonical validator and required local tools available for any claimed static result; report unavailable tools rather than claiming a pass.
• Known provenance and licensing for reused content.

Instructions

For test-quality or infrastructure work, use audit-tests for diagnosis and implement-tests for the authorized repair handoff. Skill grading, package checks and behavioral evaluation are separate; ordinary authoring does not implicitly authorize installing a test stack or making paid provider calls.

Mode Detection

Determine user intent from their prompt:

• Optimize mode: improve an existing description through the requested advanced workflow, using its existing model/provider authorization.
• Create mode (default): "create a skill", "build a skill", "new skill" -> proceed to Step 1
• Validate mode: "validate", "check", "grade", "score", "audit" -> read Validation Workflow
• Forge mode (--forge): "/skill-creator --forge <api>", "forge a skill from <api>", "generate plugin from API" -> read Forge Mode Workflow. The --forge flag invokes a stricter pipeline with NOI gate, ecosystem absorb, mandatory validation, and .forge/ audit trail. Right when generating a plugin from an API surface; not needed for hand-authored skills.
• Reforge mode (--reforge): "/skill-creator …