Claude Skills: What They Are and How to Add One

Claude skills are instruction files you load into Claude to turn a general-purpose assistant into a specialist for one specific job. You load a skill once, and from then on Claude follows a real method instead of improvising an answer. That's the short version. Here is the longer one: what a skill actually contains, how to add one in about two minutes, and how to spot a good one before you waste an afternoon on a bad one.

What Claude skills actually are

Out of the box, Claude is a brilliant generalist. It does everything reasonably well and nothing quite the way a specialist would. Ask it for a sales page and you get a sales page. It just won't be the sales page a copywriter would have written, because Claude has no idea which method you want it to follow.

A skill fixes exactly that. It is a set of written instructions from someone who does the job for a living, packaged into a file Claude reads and applies. Inside a good one you find three things: the working method (how a pro actually approaches the task, in order), the assets (the templates and structures ready to fill in), and the guardrails (the mistakes to avoid, the tone to hold, the things that quietly ruin the result).

You don't have to call the skill by name either. Once it is loaded, Claude pulls it up on its own when your request matches what it covers. You keep writing in plain English, and the method shows up underneath.

Made concrete, a skill is always built around a task somebody normally gets paid to do. A month of social posts planned in your own voice. A cold outreach sequence that segments your list before it writes a word. A sales page laid out in the order that actually converts, objections included. Same request, same Claude, except now the shape of the answer comes from someone who has done it a hundred times.

Claude without a skill is a console without a cartridge

This is the comparison that makes it click for everyone I train. A game console is a powerful machine and, on its own, completely empty. Slide in a cartridge and it knows the game: the rules, the levels, what happens when you press the button. Same hardware, brand new abilities.

That is exactly what happens when you load a skill into Claude. Nothing about the model changes. What changes is that it now has somebody's method in hand instead of a blank page. It is also where our house vocabulary comes from: we call our packs Cartridges, you load one into Claude, and Claude levels up.

Worth being precise here, because the promise gets oversold everywhere: a skill does not make Claude smarter. It makes Claude more specific. In practice, specific beats smart almost every single time.

A skill is not just a long prompt

This is the question I get in every session, so let's settle it. Yes, a good prompt already improves what you get back. No, a skill is not the same object, and the difference is not length.

• A prompt is disposable. You paste it, you use it, and in the next conversation you have to find it again. A skill is loaded once and stays available.
• A prompt asks for an output. A skill carries a process. It knows what comes first, what to check before moving on, and what to do when your answer to step two changes step four.
• A skill says no to things. That is the part people underestimate. Half the value of a specialist is knowing what not to do, and those guardrails travel with the file.

There is a quieter benefit too: you stop being the one who has to remember. The method lives in the file instead of in your head or in a notes doc you last opened four months ago.

How to add a skill to Claude

Two things before you start, and only two:

• A paid Claude subscription. Pro is enough. Uploading plugins is not available on the free plan, and that is the real prerequisite.
• The plugin file itself. If it arrived as a zip, unzip it first so you can select what is inside.

Then the actual path, which takes about two minutes:

1. Open Claude on a computer. Easiest for the first time.
2. Go to Settings.
3. Open the Plugins section. Depending on your version it may be labeled Skills or Capabilities. Same place.
4. Click Upload plugin.
5. Select the file on your computer.
6. Confirm. The plugin appears in the list, switched on.

That's the whole thing. No code, no developer account, nothing to configure afterwards. If you want the screenshots and the fixes for the errors that trip people up, we broke every step down in how to install a Claude plugin.

How to check it actually loaded

Open a brand new conversation and ask, in normal English, for something the skill is supposed to handle. If Claude walks you through a structured method, asks you the questions a specialist would ask, or hands back a real framework, the skill is live.

If you get the same vague answer as before, check two things: the plugin is toggled on in your settings, and you are in a new conversation rather than an old one started before the upload. Nine times out of ten it is one of those two.

One habit worth taking on day one: give Claude your real context in that first message. Who you are, who you sell to, what you are working on this week. The skill supplies the method, you supply the situation. A skill running on no context still produces something generic, and people blame the skill when the missing half was theirs.

How to tell a good skill from a bad one

The ecosystem is filling up fast, and the quality range is wide. Open the file before you trust it, and look for four signals:

• It has one job."Write LinkedIn posts that sound like you" is a skill. "Marketing assistant" is a category, and it will behave like one: broad and forgettable.
• It has steps. A real method is numbered, ordered and has decision points. If there is no sequence, there is no method.
• It has guardrails. Explicit rules about what to avoid and what a bad result looks like. That is the fingerprint of somebody who has actually shipped the work.
• It brings assets. Templates, structures, worked examples. Something you would have had to build yourself.

The red flag is the opposite: pages of general advice. Know your audience, be authentic, provide value. That is a blog post saved as a file, and Claude already knew all of it. Here is the fastest test I know: read the skill and ask yourself whether you could have written it in five minutes. If the answer is yes, it will not change anything about your results.

Where to start

Pick one job you do every week and quietly dread. Load one skill for that job. Use it three times before you add a second one. Stacking a dozen skills on day one is exactly how people end up using none of them, and it is the most common mistake I see.

That is the whole idea behind the Cartridges: packs of Claude skills built around one job each, with a plain-English quick start guide, ready-to-use mega-prompts and templates. You load one, you ask, Claude works.

If you are still deciding whether to buy skills or write your own, read our honest take on skill packs. And if you want to know which jobs to hand over first, start with Claude for freelancers.