How to Create a Claude Skill ZIP: Step-by-Step Guide
July 2026 · 8 min read
Quick answer
A Claude Skill ZIP should contain a clear SKILL.md file, concise trigger description, step-by-step instructions, optional reference files, and any scripts or templates the skill needs. Keep it focused on one repeatable workflow so Claude knows when to use it.
Start With One Repeatable Job
Do not start by packaging everything you know. Start with one job you perform often: creating a report, reviewing a pull request, cleaning a CSV, writing a launch email, or turning notes into a brief.
A good skill is narrow enough that Claude can recognize when it applies and detailed enough that the output is consistent.
Basic Skill Structure
- SKILL.md: name, description, and instructions.
- references/: docs, rubrics, templates, examples, or style guides.
- scripts/: optional helper scripts for repeatable mechanical work.
- examples/: sample inputs and outputs when useful.
Keep the top-level instructions short. Put long background material in references so Claude can load it only when the workflow needs it.
What To Put in SKILL.md
Write the description as a trigger: "Use this when..." Then give Claude the workflow, decision rules, required checks, output format, and any constraints that matter.
Avoid vague personality instructions. A skill should tell Claude what to do, what to inspect, what to produce, and how to verify the result.
Test Before Sharing
Test the skill with a normal example, a messy example, and an edge case. If Claude asks for the same clarification every time, add that decision rule to the skill.
If your workflow starts inside Claude.ai, pair the skill with a saved prompt library so you can launch it quickly and consistently.
Sources and further reading
FAQ
What file does every Claude Skill need?
Every skill needs a SKILL.md file that explains when the skill should be used and how Claude should perform the workflow.
Should a Claude Skill include scripts?
Only when scripts make the workflow more reliable. Use scripts for mechanical transformations, validation, exports, or repeatable checks.
How big should a Claude Skill be?
As small as possible while still being useful. Split unrelated workflows into separate skills.
Claude power users
Use Claude harder without losing your place.
ClaudeKit adds usage tracking, reset timers, saved prompts, exports, and conversation forking to Claude.ai.
Add to Chrome - Free