Claude won't remember your best prompt. A Skill will.

By Daniel S. · June 22, 2026

You've got a prompt that works. It lives somewhere — a note, a doc, a pinned message — and a few times a week you dig it out, drop it into Claude, fix a word, and run it again. That manual dig-and-paste, repeated forever, is exactly what a Skill removes. Not a fancier model, not a trick — just the end of doing it by hand.

Here's the honest version of what Skills are, when they're worth the five minutes, and when they're not.

So, what is a Skill?

A Skill is a small folder containing a single file, SKILL.md. Inside, you write two things: a one-line description of the situations it should kick in for, and the steps Claude should follow once it does. It's all plain English — no code involved.

The real shift is who keeps track. With a prompt, that's you: each time, you decide to go find it and paste it in. With a Skill, Claude does the tracking — it recognizes the kind of task and loads the instructions itself, without you reaching for anything.

What it isn't: a Skill doesn't make Claude smarter, and it isn't an agent. It makes Claude consistent at a job you'd otherwise re-explain. That's the entire value — and it's a real one if you do the same things repeatedly.

When it's worth it — and when it isn't

The threshold is repetition, nothing else. If you've pasted the same prompt three or more times, or you keep re-explaining the same preference ("write it short, no corporate language, lead with the point"), that's a Skill.

If you've done it once, just type the prompt. And if the task changes every time, a Skill won't help — a Skill encodes a stable way of doing something. Don't build one for a job you'll do twice and never again. Most people don't need many Skills. They need two or three for the things they actually repeat.

Making one (about five minutes)

Make a folder and give it a short, lowercase name with no spaces — say tighten-draft.
Put a SKILL.md inside it with a name, a "use when…" description, and the instructions.
Add it in claude.ai under Customize → Skills (upload your folder).

One setting to flip first: Skills need "Code execution and file creation" turned on — on individual plans that's in Settings → Capabilities. And the good news, contrary to a lot of older posts: this isn't paid-only. Skills work on Free, Pro, Max, Team, and Enterprise. (On Team and Enterprise, an admin switches it on at the org level.)

The line that makes or breaks it

That one-line description is what decides whether the Skill ever fires. Write it as "Use when I…" and fill it with the actual words you type when the task comes up. This is where most Skills die — they're written in tidy, abstract language that never matches how you really talk to Claude, so nothing ever triggers them.

Compare:

Weak: Use for strategic evaluation.
Works: Use when I ask: should I build this? is this a waste of time? do I actually need this?

The second one fires because it's built from phrases you'd really type. The first is too abstract to match anything, so it just sits there.

What this looks like in practice

Say you turn one idea into several posts every week, and you've been pasting the same instructions each time. Save it once:

---
name: repurpose
description: Use when I want one piece turned into several posts.
---
From the input, make one longer post, five short posts pulled from its
strongest lines, and three opening-hook options for each. Stay in my
voice; no repeated angles.

Now you write the piece once, say "repurpose this," and the week's posts come out of that single input. You didn't get a smarter model — you stopped redoing the same setup by hand. That's the whole thing, and it's enough.

When it misbehaves

Skills break in predictable ways, and each has a one-line fix:

Never fires → the description doesn't match your words. Rewrite it as "Use when I…" with real phrases.
Fires too often → the description is too broad. Narrow the job.
Ignores its own rules → the instructions are too long, contradictory, or trying to do several jobs. One Skill, one job.
Goes stale → open the file, change it, re-upload. Treat them as things you revise, not set-and-forget.

Where to get ones that already work

Anthropic ships official Skills at github.com/anthropics/skills — that's the safe place to start. You'll also see viral threads pushing community skill libraries with enormous star counts. Some are genuinely good. But ignore the numbers in those posts; treat them as leads to check, not facts. A skill someone else wrote only helps if it matches how you work.

Start with one

Don't build a system. Pick the single prompt that annoys you most — the one you retype the most often — and turn that one into a Skill tonight. Tomorrow it loads itself.