skill-creatorlisted

# Skill Creator Official docs: <https://code.claude.com/docs/en/skills.md>. Fetch when unsure about frontmatter semantics, subagent forking, hook integration, or recent features. ## Process ### 1. Gather requirements Ask the user: - What task/domain does the skill cover? - What specific use cases should it handle? - Does it need executable scripts or just instructions? - Any reference materials to include? If the user's description is already clear, skip straight to drafting. ### 2. Determine placement Infer from context, ask only if ambiguous: - **Global** (`~/.claude/skills/`) - across all projects - **Project** (`<project>/.claude/skills/`) - repo-specific - **Plugin** (`<plugin>/plugins/<name>/skills/`) - distributed via marketplace ### 3. Assess complexity **Simple** (just write the SKILL.md): - Purely instructional (workflow, guidelines, domain knowledge) - No supporting files needed **Full** (skill with bundled resources): - Needs scripts for deterministic/repeated operations - Needs reference docs (schemas, API docs, large knowledge bases) - Needs assets (templates, images, fonts) ### 4. Draft the skill **Simple path:** Create the directory and write SKILL.md directly. **Full path:** 1. Plan supporting files (what scripts/references/assets are needed) 2. Create the skill directory and subdirs 3. Write supporting files first (may need user input for assets/docs) 4. Write SKILL.md last, referencing the supporting files ### 5. Review with user Present