So, what is a Claude skill? Let me explain it in the easiest way possible.

Hi, I'm Francis. My goal is to teach a million people how to use AI to get better at their jobs or run their businesses. And one of the questions I get asked the most — by founders, by employees, by people who just opened Claude for the first time last week — is some version of: what's a skill? Is it a feature? Is it something I have to set up? Do I have to be technical?

Here's the good news. You only need to know two things, and then you've got it.

Thing one: a prompt is just text. A skill is a really big prompt with code attached.

When you talk to Claude, what you're typing is called a prompt. It's just text. You tell Claude what you want, Claude reads it, Claude responds. That's the whole loop. A short prompt might be "summarize this email." A long prompt might be five paragraphs explaining how you like your weekly report formatted, what tone to use, what to leave out, what to include.

A skill is what happens when you take that long, detailed prompt and package it up so you never have to type it again. Imagine writing out every instruction you'd give a new assistant on day one — your preferences, your templates, your no-go list, the things you always forget to mention until it's too late. Now imagine bundling all of that into a single file and handing it over.

That's a skill. It's a really big prompt with a lot of detail. And here's the part that makes it more than just a saved prompt: a skill can also include code. When Claude uses the skill, it runs that code automatically. So if the task involves something fiddly — formatting a spreadsheet, filling out a PDF, generating an image, building a slide deck — the skill brings the tools along with the instructions. You don't have to know what the code does. You don't have to know it exists. Claude handles it.

This is the part most people miss when they first hear about skills. They think it's just a saved prompt template. It's not. It's a saved prompt template plus a small toolkit, and Claude knows how to use both.

Thing two: with a prompt, you have to tell Claude to use it. With a skill, you don't.

This is the magic part.

If you save a long prompt as a note somewhere, you still have to remember to paste it in. You have to find it, copy it, drop it into your conversation with Claude, and then ask for what you want. Every single time. Most people stop doing this within a week, because life is busy and that's a lot of steps.

Skills skip all of that. You install the skill once, and from then on, Claude just knows it has it.

Here's what it looks like in practice. Open Claude, go to Customizations, then Skills. You'll see a list of every skill you've added. That list is what Claude looks at when you make a request. You ask for a slide deck, Claude scans the list, sees there's a slide deck skill, pulls it up, and uses it. You ask for a spreadsheet, same thing — Claude finds the spreadsheet skill on its own. You don't say "use the skill." You don't even have to remember which skills you have. Claude picks the right one based on what you're asking for.

This is why I keep telling people: a skill is not a saved prompt. A saved prompt is a piece of paper you keep in a drawer. A skill is a tool sitting on Claude's workbench, ready to use the moment it's needed.

Think of it like a mini software you install inside Claude

This is the analogy that clicks for most of the people I teach. A skill is basically a tiny piece of software that lives inside Claude. You install it, and from then on, Claude has a new capability it didn't have before.

The point isn't just convenience. The point is consistency. Same task, same result, every time. If you build slide decks every week, you don't want a different layout every week. If your team sends reports every Monday, you don't want five different formats showing up in five different inboxes. A skill locks the result in. You stop getting surprises. You stop having to proofread for the same mistakes. The output is the same shape it was last time, because Claude is reading from the same playbook.

That alone is worth installing skills for. The bigger upside, though, is that you stop being the bottleneck. When the instructions live inside Claude instead of inside your head, anyone on your team can run the same task and get the same result. The skill is the standard.

And anyone can build one. No coding required.

This is the part that surprises people the most.

You might assume building a skill requires programming. It doesn't. Claude has a skill literally called Skill Creator. You open it, you chat with Claude about what you want the skill to do, and it builds the skill for you. You describe the task in plain English. You tell it what good output looks like. You give it a few examples. It writes the skill, you test it, you tweak it. That's the whole process.

If you're feeling fancy and want more control multiple files, custom scripts, more complex logic there's a full guide that walks you through it. But you don't have to start there. Start by chatting with Skill Creator. Most people are amazed at how fast they have something working.

That's a Claude skill

To recap, in case you're skimming: a prompt is text. A skill is a really big prompt with code attached. Prompts you have to invoke. Skills run automatically when Claude needs them. They're like mini software you install inside Claude, they give you the same result every time, and anyone can build one without writing code.