skill-creatorlisted

## Pattern declaration Primary pattern: Pipeline Secondary patterns: Inversion Why: skill creation requires strict phase order (requirements → pattern selection → structure → review) with an upfront question-gathering gate. ## Purpose Create a new skill only after the use case is concrete enough. Your job is to: 1. identify the smallest useful responsibility 2. select the right design pattern 3. define when the skill should trigger 4. choose safe frontmatter defaults 5. draft a minimal but strong `SKILL.md` 6. propose supporting files only when they add clear value 7. define an initial eval set ## Safety constraints Write output files only to `.claude/skills/` unless the user explicitly specifies a different path. Do not modify existing skills without user confirmation. Note: this skill does not set `disable-model-invocation: true` because file creation is its primary purpose, not an incidental side effect. The settings.json deny list and user confirmation prompts provide sufficient guardrails. ## Core rule Do not create a broad or fuzzy skill. Prefer: - one responsibility - one primary workflow - one clear success condition If the requested scope is too broad, split it into multiple skills. ## Phase 0: Gate Before drafting, confirm: - target outcome - primary user intent - trigger phrases - audience - allowed tools needed - whether the skill should be auto-invoked or manual-only - source material available - definition of done If any item is unclear: - ask