skill-generator-agent — Claude Code subagent: what it does
skill-generator-agent turns a skill spec into files on disk: SKILL.md, helper scripts, reference docs. Then it checks frontmatter and layout.
no license ★ 1,357 updated 2026-03-01
.claude/agents/skill-generator-agent.mdWhat skill-generator-agent does
Give it a specification and it writes the skill out: a SKILL.md with proper frontmatter, supporting material in its own folders, plus scripts with execute permission set where the spec asks for them. The run is ordered — read the spec, plan the layout, generate, then verify.
Folders follow your answer about placement: personal skills go under ~/.claude/skills/skill-name/, project ones under .claude/skills/skill-name/. Inside, scripts/ holds runnable code, references/ holds longer docs, assets/ holds templates. Before finishing it checks the YAML, the trigger wording in description, and that every planned file is there.
The spec has to exist first. This agent works from the document produced by skill-elicitation-agent and has nothing to build without it. Its toolset includes Write and Bash, so files really land on disk.
What it helps with
- turn a written spec into a valid
SKILL.md - lay out a multi-file skill across
scripts/,references/andassets/ - generate a helper script with error handling and usage notes
- audit a skill before publishing: YAML, triggers, file permissions
- decide between a personal and a project path for a new skill
Example prompts for the agent
- Build the skill from
spec.mdand put it under.claude/skills/ - Generate
SKILL.mdandreference.mdfor a log-parsing skill, with triggers in the frontmatter - Check the layout of
~/.claude/skills/pdf-helper/and tighten its description
How to install skill-generator-agent
Manually: put the files in place
.claude/agents/skill-generator-agent.mdFor all projects use ~/.claude/agents/. Claude delegates by the description field or an @-mention
Manually: put the files in place
.codex/agents/skill-generator-agent.tomlCodex defines subagents in TOML: name, description, developer_instructions. Move the Markdown text into developer_instructions by hand. For all projects use ~/.codex/agents/
Manually: put the files in place
.cursor/agents/skill-generator-agent.mdCursor also reads .claude/agents/
Step by step, with commands for each platform: Claude Code subagents: how to create one, call it and keep context clean
Questions about skill-generator-agent
How do I install skill-generator-agent in Claude Code?
Copy the agent file to .claude/agents/skill-generator-agent.md.
What does skill-generator-agent do?
It builds a skill from a spec: the main SKILL.md, reference docs, examples and scripts arranged in folders. Then it runs checks on frontmatter and structure.
What do I need before running it?
A finished spec from skill-elicitation-agent, which supplies the name, triggers and file list. Access to Write and Bash matters too, since nothing reaches disk without them.