skill-creation-walkthrough
Step-by-step guide for creating your own Claude Skills, from deciding whether a skill is the right tool to writing the SKILL.md file, structuring reference material, and making it trigger reliably. Use when you want to package a workflow, framework, or repeated task into a reusable Skill, when an existing skill is not triggering or not loading the right context, when you are auditing a skill that is underperforming, or when you want to publish a skill for others. Also triggers when someone asks "how do I make a skill" or "what makes a good skill". Useful for individuals, teams, and anyone publ
Profile →npx skills add rampstackco/claude-skills --skill skill-creation-walkthrough --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
A walkthrough for designing, writing, and maintaining your own Claude Skills. Covers when a skill is the right shape for your problem, how to write a description that actually triggers, how to structure SKILL.md and references, and how to test and iterate. ## When to use - You catch yourself writing the same prompt or instructions repeatedly. - You want to package a workflow or framework for reuse. - An existing skill of yours is not triggering when it should. - You are publishing skills for others to use. - You want to teach Claude a domain-specific way of working. - You are reviewing a skill someone wrote and need a quality bar. ## When NOT to use - For one-off prompts (just write the prompt). - For information that should live in system context, not progressive disclosure. - For changing Claude's general behavior across all conversations (use Claude.ai settings or system prompts, not skills). - For replacing tool calls (skills are instructions, not tools). ## Required inputs - The task or workflow you want to encode. - The audience: who will trigger this skill, in what kind of conversation. - Existing artifacts: prompts you have used, docs you have written, examples of good outp
- When to use
- When NOT to use
- Required inputs
- The framework: how skills work
- Workflow
- Phase 1: Decide if a skill is the right shape
- Phase 2: Define the trigger
- Phase 3: Write the description
- Phase 4: Structure the SKILL.md body
- Phase 5: Add references for what does not belong in SKILL.md
- Phase 6: Test and iterate
- Deep dive: description anatomy
- Sentence 1: What it does
- Sentence 2: When to use it
What does the skill-creation-walkthrough skill do?
Step-by-step guide for creating your own Claude Skills, from deciding whether a skill is the right tool to writing the SKILL.md file, structuring reference material, and making it trigger reliably. Use when you want to package a workflow, framework, or repeated task into a reusable Skill, when an existing skill is not triggering or not loading the right context, when you are auditing a skill that is underperforming, or when you want to publish a skill for others. Also triggers when someone asks "how do I make a skill" or "what makes a good skill". Useful for individuals, teams, and anyone publ
How do I install it?
Run `npx skills add rampstackco/claude-skills --skill skill-creation-walkthrough --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From rampstackco/claude-skills, a repository with 515 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.