What is a Claude skill, and how is it different from a project?

Arjita Sethi · Updated November 9, 2026 · 4 min read

AI for Growth

A Claude skill is a written procedure for one job, saved to your account, that Claude follows whenever you describe that situation in any chat. A project is a workspace that holds the context and conversations for one body of work, like one business, one client or one course. Put simply, a project tells Claude who and what it is working on, and a skill tells Claude how you do a specific job. Build with AI Club teaches non-technical people to use both, because they solve different problems.

Why people mix them up

Both save you from retyping things, so they feel like the same tool. I see the confusion every time I teach this. Someone builds a beautiful project for their weekly client updates, then starts a second client and has to rebuild the whole thing, because the method lived inside the first project.

The distinction that clears it up is this: context belongs to a body of work, and a method travels. If you write weekly updates the same way for three clients, that is one skill. The details about each client are three sets of context, and each one belongs in its own project.

The four things people keep confusing

When I teach this, I put four cards on the screen.

  • Context file: knowledge that should always be true inside one body of work, like your brand rules, your customer and the things you never say. It lives in one project.
  • Skill: a procedure with a trigger. It works across your whole account, inside any project and in a chat with no project at all.
  • Project: the workspace. It holds the context and the conversations for one brand, one client or one course.
  • Agent: a sequence that runs on a schedule or with one command, built out of the other three.

A plain prompt sits underneath all of these. It is the right choice for a one-off question you will never ask again.

How to tell which one you need

Think of one specific thing you did more than once last month, then answer three questions about it.

  1. Does it change how Claude thinks, or what Claude does? If it changes how Claude thinks, like your tone or your audience, it is context. If it changes what Claude does, like the steps for a weekly update, it is a skill.
  2. Should it fire on a trigger, or should it always be true? Always true points to context in a project. A trigger points to a skill.
  3. Does it need to run without you in the room? If yes, you are looking at an agent, and an agent is made from a skill plus context, with a checkpoint where you approve the result.

How to build your first skill

  1. Pick the job you explained to AI most often last week, like the weekly update, meeting prep or turning one long piece into short posts.
  2. Write the steps the way you would brief a new assistant, including what a good result looks like and one line it must never cross.
  3. Write the description with care, because the description is how Claude decides when to use the skill. Describe the situation in the words you would actually type.
  4. Test it in a fresh chat. Describe the situation without naming the skill. If it does not kick in, fix the description, because that is nearly always where the problem is.
  5. When the result is close but not right, change the skill rather than the chat, so the fix is there next week.

What not to turn into a skill

Some jobs are better left alone. A task you do twice a year is cheaper as a note. A task that changes every time is judgment, and writing it as a procedure makes it worse. A job you have never done by hand can't be written down yet, because you don't know the steps.

FAQ

Do I need to know how to code to write a Claude skill? No. A skill is written in plain language, the same way you would write instructions for a new hire.

Can I use a skill inside a project? Yes. A skill works across your whole account, so it can use the project's context while it follows your steps.

Does ChatGPT have something similar? Other tools have their own versions of saved instructions and reusable workflows, and the thinking is the same: write the method once and keep your context separate. Check your tool's current features, because they change often.

Learn it with me

This week's Build with AI Club YouTube lesson, 4 Claude skills I would set up before anything else, shows the first four skills I recommend and how each one is set up. Watch it on the Build with AI Club YouTube channel

You can also watch me teach live for free. My AI 101 class at SHACK15 in San Francisco on Wednesday, Nov 11, 6 to 7 PM PT, is Your AI Research Desk, and free online audit seats are open at luma.com/build-4bhm. On Thursday, Nov 12, 10 to 11 AM PT, I'm co-hosting Aligning AI With Your Family's Values with Sarah Dooley, free on Zoom, at luma.com/build-nt03.