In one minute

  • A skill is a small set of written steps that teaches Claude how you do one job, like writing a product description or answering a shipping question.
  • You write it once. Claude notices when a request matches and uses it on its own.
  • Skills are available on the Free, Pro, Max, Team and Enterprise plans.
  • Start with three: the writing that sells, the questions you answer every week, and the checks you run before anything goes out.

Here's a small confession. For months I typed the same instructions into Claude over and over. Every product description started with me explaining how I write product descriptions. Every customer reply started with me explaining how I answer customers.

I was training the same employee every single morning.

Claude skills is the feature that ends that. If you watched the video, this is the written version you can come back to. If you didn't, you can read this on its own.

What a skill is, in plain English

A skill is a small set of written steps that teaches Claude exactly how you do one thing. How you write a product description. How you answer a shipping question. How you check a newsletter before it goes out.

Anthropic describes skills as folders of instructions, scripts and resources that Claude loads when they are relevant to a task. You don't need the scripts part. For most of us a skill is just clear instructions, written in plain words.

And here's the part I love. You don't have to call for it. When what you're asking for matches a skill you've made, Claude picks it up on its own. Claude reviews the skills you have, works out which ones fit your request, and loads only what it needs. You just ask the way you always ask.

Skills and projects are not the same thing

If you've set up a Claude project, you already have a folder with a memory. It holds your files and your standing instructions, and it's always there in every chat inside that project.

A skill is different, and the difference matters.

The project knows who you are. A skill knows how you do one job.

A project is background. A skill is a procedure that only wakes up when the job comes up, and it works across Claude, not just inside one project.

Before you start: turn it on

Skills need code execution to be switched on. On an individual Free, Pro or Max plan, go to Settings, then Capabilities, and turn on code execution and file creation. In the newer layout it's called "Create and edit files." Then go to Customize, then Skills, to switch individual skills on or off.

On a Team or Enterprise plan, your admin controls this in the organization settings.

What goes inside a good skill

You don't need a special editor. You can simply tell Claude, "I want to make a skill for how I write product descriptions. Help me build it." It will ask you questions. Answer them the way you'd train a careful new assistant, and it writes the skill for you.

But you'll get a better skill if you know what belongs inside. Three things.

  1. When it should wake up. One sentence is enough. "Use this whenever I ask for a product description." Anthropic's own guidance says a clear description of when to use the skill is what helps Claude find it.
  2. The steps, in order. Ask me for the details first. Keep it under 80 words. Lead with the feeling. End with the picture in their head.
  3. The rules. What never happens? Never invent a measurement. Never promise a shipping date. Never use the word luxury.

If you can explain the job to a person over coffee, you can write the skill. It's the same words.

Your first skill, step by step

  1. Pick the job you repeat most.
  2. Do that job with Claude once, the ordinary way, until you get a result you like.
  3. Say, "Turn what we just did into a skill."
  4. Read what it gives you, and fix the two lines that don't sound like you.

That's your first skill. Mine took about ten minutes.

The three skills I'd build first

If you run something small, I'd start here.

One for the writing that sells. Product descriptions, service pages, listings. Your steps, your brand words, your length.

One for the questions you answer over and over. Where is my order? Do you take returns? Your policies, your warmth, your exact way of saying no, kindly.

One for the checking you do before anything goes out. A small checklist skill. "Before I send a newsletter, check these five things." Claude runs the list so you don't have to hold it in your head.

The mistake to skip

I made this one, so you don't have to. Don't try to build a skill for everything.

A skill for a job you do once a month is a drawer you'll never open again. My rule is simple. If you'll ask for the same thing more than twice, make it a skill. If not, just ask.

Where it gets quietly powerful

Skills and projects work together. The project knows your business. The skill knows the job.

A chat inside your project, with your skills on the shelf, is the closest thing to a trained assistant you can have without hiring one.

Your ten minutes this week

Pick the one job you repeat most. Do it once with Claude the ordinary way. Then say, "Turn this into a skill." Read it, fix two lines, and you never type those steps again.

If any of the words in this post felt new, my free Plain-English AI Dictionary explains them one calm sentence at a time. You'll find it, and everything else I make, at mawahibkhearalla.com.

You're not behind. You're right on time.

Sources

Mawahib Khearalla

Mawahib Khearalla works a 9-to-5, runs two small businesses, and shares the calm, practical way she uses AI to make room for what matters.

Letters from Mawahib

One calm letter, once a week.

What's working, and the small AI shortcuts that give me my evenings back — pick the topics you want.