command-skill-creatorlisted

# Command Skill Creator Create command-type skills - imperative prompts that guide Claude through phased execution of multi-step workflows. These are `/slash-commands` users invoke explicitly, not passive reference material. Command skills live in project-level `.claude/skills/<name>/SKILL.md` and are invoked as `/name [arguments]`. ## When to use this vs skill-creator - **This skill**: Commands that DO things - deploy, commit, migrate, sync, release, scaffold. Side effects, approval gates, phased execution. - **skill-creator**: Knowledge that INFORMS Claude - coding standards, API references, framework guides. No side effects, auto-triggered by context. ## Creation Workflow ### Step 1: Understand Intent Establish what the command automates. Ask (or extract from conversation context): - What does this command do? What are the major phases? - Which actions have side effects? (commits, deploys, file mutations, external APIs) - Does it take arguments? What kind? - Does it operate across multiple repos/projects? - Are there approval gates needed before irreversible actions? - What model complexity is needed? (most commands work with default; complex multi-phase reasoning may need `opus`) If the user says "turn this into a command," extract the workflow from conversation history - tools used, sequence, corrections made. ### Step 2: Design Frontmatter Choose fields based on the command's nature. See the frontmatter reference table below. Minimum viable frontmatter: ```y