<- all tokdocs

How to Actually Build a Claude Skill

Watch on TikTok

View on TikTok ->

Most people are building Claude Skills wrong. They try to one-shot it -- write one big prompt, tell Claude to turn it into a skill, and then try to use it. This approach rarely works because a skill is fundamentally different from a prompt. Building a great skill is closer to building a product than it is to writing a prompt.

The Mindset Shift: Products, Not Prompts

A prompt lives in one turn. It gets re-typed each time. It has no tests, no structure, no reusable files. A skill, by contrast, survives conversations. It auto-loads on intent. It has an eval. It has a spec (SKILL.md). It bundles code and references.

Infographic showing "How to actually build a Claude Skill" with SKILL.md as entry point

The pipeline for building a skill is: design, then spec, then scripts, then evals, then ship.

What a Skill Actually Contains

A skill is much more than just a prompt. It has instructions, scripts, reference files, and teaches Claude exactly how to do something. The SKILL.md file is the entry point -- it is always loaded as metadata when the skill is invoked.

Side-by-side comparison of prompts vs skills showing the mindset shift

Building Intentionally

If you want a skill you will use every day, be intentional about its design. Ask yourself four questions:

  1. What should the skill handle the same way every single time?
  2. Where should it be flexible and allow for changes?
  3. What files or tools does it need to accomplish the task?
  4. What can happen step-by-step versus what can happen in parallel?

Once you have answered these, you can create the basis for your skill.

Evaluating Before Deploying

Before you deploy a skill, run an eval. Try completing the same task both with and without the skill. The skill should produce measurably better results. If it does not, go back to the drawing board.

Key Takeaways

  • A Claude Skill is a product, not a prompt -- treat it like a product development process
  • Skills contain instructions, scripts, reference files, and a SKILL.md spec file
  • Design intentionally: define what is fixed, what is flexible, what tools are needed, and what can run in parallel
  • Always run evals before deploying -- compare results with and without the skill

Resources

Published May 12, 2026. Writeup generated from a favorited TikTok.