← ClaudeAtlas

skill-creatorlisted

Authors Claude Code skills (`.claude/skills/<name>/SKILL.md`, project/user/plugin/managed scope). Use whenever a new skill is being written, an existing skill is being edited, a recurring workflow is being captured as a playbook, scope and invocation are being decided (inline vs forked, model-invocable vs user-only), `allowed-tools` patterns are being chosen, bundled `references/` or `scripts/` are being added, `paths:` is being scoped, or a skill that fails to trigger is being debugged. Triggers on "create a skill", "write a SKILL.md", "turn this into a skill", "make a slash command", "package this workflow", "playbook", "fix this skill", "skill not triggering", "skillify". Use even when the user does not say the word "skill" but is asking to capture a procedure they keep retyping. Pair with `ac:prompt-writer` for the body content, with `command-creator` for command-shaped skills (`/name [args]`), with `agent-creator` for context-isolated workers, with `ac:claude-md-rules-creator` for facts that belong in CL
anilcancakir/claude-code · ★ 1 · AI & Automation · score 77
Install: claude install-skill anilcancakir/claude-code
# Skill Creator You are about to write or edit a skill another Claude will load. A skill is a directory with a `SKILL.md`. Frontmatter is metadata for the trigger decision; the body is a prompt that enters the conversation when the skill fires and stays for the rest of the session. This skill is the playbook for picking the right shape, writing the frontmatter, structuring the body, and shipping bundled references and scripts that survive plugin install. Target is Opus 4.8. Same rules work for Sonnet 4.6 and Haiku 4.5 with lower effort levels. The body of every skill you produce here is a prompt, route that body work through the sibling `ac:prompt-writer` skill instead of restating prompt principles here. ## Two jobs, not one Writing a skill splits cleanly into two tasks, and conflating them is the most common authoring mistake. 1. **Skill shape.** Frontmatter, file layout, scope, invocation control, bundling. This file teaches that. 2. **Body content.** The markdown the model reads when the skill triggers. This is a prompt. Route through `ac:prompt-writer` (architecture, snippets, anti-patterns, Opus 4.8 tuning). The shape decisions front-load most of the leverage. A great body inside the wrong shape (wrong scope, wrong invocation control, bloated description) never gets used. A modest body inside the right shape gets used every day. ## Decision flow Route by the user's request. Each branch lands on the right reference for the depth. ``` Is a skill the right tool at