Claude Skills: What Anthropic's Reusable Instruction Packs Mean for Your Team

TL;DR

Claude Skills are reusable instruction packs that teach Claude how your business does a specific task — how you format a proposal, structure meeting notes, apply your brand, or build your monthly report. You write the instructions once (in plain language, no coding), and from then on Claude automatically pulls in the right skill whenever a task calls for it. You don't have to remember it's there or paste it in. If a Project is a workspace that holds your knowledge, a Skill is a recipe that holds your method — and unlike a Project, a Skill follows you everywhere Claude works. Anthropic has made it an open standard, anyone on any plan can use them, and companies like Rakuten are reporting tasks that took a full day now finishing in an hour. Here's what Skills are, why they matter, and how to build your first one this week.

What a Claude Skill Actually Is

A Skill is a saved set of instructions that teaches Claude how to do one specific task the way your company does it.

Think about the tasks your team does over and over that always follow the same shape. Writing a client proposal in your standard structure. Turning messy meeting notes into a clean summary with action items. Producing the monthly sales report in the exact format your leadership expects. Applying your brand voice and formatting rules to a document. Each of these has a “right way” to be done — a method that lives in someone's head or in a half-remembered template.

A Skill captures that method and hands it to Claude. You write down the steps, the rules, the format, and any examples — in plain English, in a simple document — and save it as a Skill. From that point on, Claude knows how to do that task your way.

The clever part is what happens next. You don't have to tell Claude “use the proposal skill now.” When you ask Claude to draft a proposal, it recognizes that the task matches your proposal skill, quietly loads those instructions, and follows them. When the task is something else, it leaves that skill alone. Anthropic calls this “progressive disclosure” — Claude only reaches for the instructions it actually needs, when it needs them.

The simplest way to picture it: a Skill is like a laminated recipe card you've written for one dish. Claude keeps a whole box of these cards. When you order that dish, it grabs the right card and cooks it exactly the way you specified — without you having to find the card and read it out loud every time.

Why This Is Different From Projects (and Why You'll Want Both)

A Project holds what Claude should know. A Skill holds how Claude should work. They solve different problems.

If you've read our piece on Claude Projects, this is the natural next question: isn't this the same thing? It isn't, and the difference is worth getting straight because it changes how you use each one.

A Project is a workspace tied to one area of your business — a client, a department, a product. It holds background knowledge (your documents, your pricing, your policies) that is always available inside that workspace. The knowledge sits there permanently, loaded into every conversation in the Project.

A Skill is a method for doing a task, and it isn't tied to any one workspace. It activates dynamically, wherever you are, the moment a task matches it. The same “format our monthly report” skill works inside your Finance Project, inside a one-off chat, and even inside an automated agent — without being copied into each one.

Here's the practical way to think about it. If you keep re-uploading the same documents, you want a Project. If you keep re-explaining the same steps — “remember, our reports always start with the headline number, then three bullets, then the risks” — you want a Skill. Most mature setups use both: a Project that holds the knowledge, with Skills layered on top that handle the recurring tasks within it.

The Four Kinds of Skills You'll Run Into

Some skills come built in, some you write, some your admin pushes to everyone, and some come from the software you already use.

It helps to know the four categories, because you'll benefit from all of them without having to build everything yourself:

• Anthropic Skills — built and maintained by Anthropic, switched on automatically. The clearest example is document creation: when you ask Claude to produce a proper Excel spreadsheet, a formatted Word document, a PowerPoint deck, or a PDF, a built-in skill handles the formatting. You don't set these up; they just work.
• Custom Skills — the ones you or your team write for your own recurring work. Applying brand guidelines, generating a templated client email, structuring meeting notes, drafting a standard work order. This is where most of your value will come from.
• Organization Skills — on Team and Enterprise plans, an administrator can build a skill once and push it to everyone in the company. It shows up automatically in every team member's skill list. This is how a 50-person company makes sure everyone produces the proposal, the report, or the customer reply the same correct way.
• Partner Skills — professionally built skills from companies like Notion, Figma, and Atlassian, designed to work alongside their connectors. If your team lives in those tools, you get well-made skills for free.

The point is that Skills aren't only something you have to author from scratch. A lot of capability arrives ready-made — and the custom skills you write sit comfortably alongside them.

What a Skill Looks Like in Practice

Five concrete examples that map onto work your team is already doing.

1. The on-brand document skill

A marketing team writes a skill that captures their brand voice, their formatting rules, the words they never use, and how headings and bullets should look. Now anyone — not just the senior editor — can ask Claude to draft a blog post or a one-pager and get something that comes out on-brand by default. The consistency that used to require a human reviewer is baked into the skill.

2. The monthly report skill

A finance or operations team writes down exactly how their monthly summary should be built: headline number first, then the three metrics leadership cares about, then a short risk section, with figures rounded a specific way and never invented. Each month, someone drops the raw numbers into Claude and asks for the report. Claude applies the skill and produces the document in the expected format every time — no reformatting afterward.

3. The meeting-notes skill

A team that drowns in calls writes a skill that turns a raw transcript or rough notes into a clean output: a two-line summary, decisions made, action items with owners, and open questions. Anyone on the team can paste their notes and get the same tidy structure back — so notes from different people finally look the same.

4. The proposal skill for a services firm

A consultancy encodes its proposal structure into a skill: the sections in order, the tone, the standard scoping language, the way deliverables and timelines are presented. A junior team member can now produce a first draft that follows the firm's house style closely — turning a blank-page task into a review-and-refine task.

5. The customer-reply skill for support

A support team writes a skill that captures their tone, their escalation rules, and the way they like to acknowledge, explain, and resolve. Replies come out consistent in voice and structure regardless of who is at the keyboard, and new hires sound like the team from day one.

Why Skills Matter More Than They First Appear

Skills turn “the way we do things” from tribal knowledge into something every person and every AI tool can use.

The quiet problem in most companies is that the “right way” to do a task lives in the heads of a few experienced people. The best proposal-writer knows the structure cold. The senior analyst knows how the report should read. When those people are busy, on holiday, or gone, the quality drops and everyone reinvents the method.

A Skill is that method written down once and applied automatically — by anyone, every time. That has three compounding effects:

• Consistency. Ten people using the same skill produce ten outputs that follow the same standard. The drift that comes from everyone prompting Claude slightly differently disappears.
• Speed. Nobody re-explains the method. The instructions are already there, so the task starts further along. This is where reports of work compressing from a day to an hour come from — the setup time per task collapses to zero.
• Onboarding. A new hire inherits the company's methods on day one, because the methods are encoded in the skills they have access to. They don't need to absorb years of “how we do it here” before they're useful.

And because a Skill follows Claude everywhere — chats, Projects, and automated agents — the same method you write for a person also powers any automation you build later. The work you put into describing how a task should be done pays off in more than one place.

How Skills Fit With the Rest of Claude

Skills, Projects, and connectors each cover a different part of the picture — and they're strongest together.

It's worth seeing where Skills sit relative to the other pieces, because the confusion usually comes from treating them as competing features when they're complementary:

• Projects give Claude your knowledge — the documents and context for an area of work.
• Connectors (MCP) give Claude access — the ability to reach into the tools where your data lives, like your CRM, your files, or your project tracker.
• Skills give Claude method — the steps and standards for doing a specific task your way.

A fully equipped Claude setup uses all three: a Project holds the background, connectors pull in live data, and a Skill ensures the output is produced the right way. You don't need all three to start — a single custom skill on its own is already useful — but knowing the roles keeps you from trying to force one feature to do another's job.

One more detail that matters for the long term: Anthropic has published the Skills format as an open standard. In plain terms, the skills you write aren't locked inside Claude — they're described in a portable format that other AI tools adopting the standard can use too. The effort you invest in writing down your methods isn't a bet on a single vendor.

The Mistakes Teams Make With Skills

A few avoidable errors that keep Skills from delivering.

• Writing one giant skill for everything. A skill should do one task well. “Handle all our writing” is too broad for Claude to apply cleanly. “Format our monthly board report” is the right size.
• Being vague. “Make it professional” teaches Claude nothing. “Open with the headline number, use three bullets, never invent figures, keep it under one page” teaches it exactly what you want. The more specific the steps, the more reliable the result.
• Not including an example. A skill that shows Claude one good finished output — an example proposal, an example report — works far better than instructions alone. Show, don't just tell.
• Letting skills go stale. If your report format changes, the skill has to change with it, or Claude will faithfully produce last quarter's format. Someone needs to own each important skill.
• Building in isolation. On Team and Enterprise plans, the highest-value move is to build a skill once and share it organization-wide — not to have forty people each write their own slightly different version of the same thing.

What Your Team Should Do This Week

Three steps to get your first Skill working.

1. Pick one repeatable task with a clear “right way”

Find a task your team does regularly that always follows the same structure — the monthly report, the standard proposal, the meeting-notes format, the customer reply. The more often it's done and the more it matters that it's done consistently, the better the candidate.

2. Write down the method — including one example

In plain language, write the steps, the rules, and the format. Then add one example of a finished output done well. You don't need any coding for this; you're describing how you'd brief a sharp new colleague. Save it as a Skill from the “Customize” area in your Claude settings.

3. Use it for a week, then tighten it

Have the people who do that task ask Claude to do it and let the skill run. Where the output still needs editing, that's your cue to sharpen the instructions or improve the example. Skills get better the more you tune them — the first version is a starting point. Once one skill is solid, build the next, and consider pushing the best ones to your whole team.

FAQ

Do I need a paid plan to use Skills?

No. Skills are available across Free, Pro, Max, Team, and Enterprise plans. The ability for an administrator to build a skill once and distribute it to your whole organization is part of the Team and Enterprise plans. Skills do require code execution to be enabled, which is a setting in your account.

Do I need to know how to code to create a Skill?

No. A basic skill is just instructions written in plain language — the steps, rules, format, and an example for a task. That's enough for the large majority of business use cases. More advanced skills can include executable scripts for technical workflows, but you don't need that to get real value. If you can write a clear brief for a new colleague, you can write a skill.

How is a Skill different from a Project?

A Project holds knowledge — documents and context that are always loaded inside that workspace. A Skill holds method — the steps for doing a specific task — and it activates automatically wherever you are, not just inside one workspace. Many teams use both: a Project for the background, Skills for the recurring tasks done within it.

How is a Skill different from Custom Instructions?

Custom instructions apply broadly to all your conversations — a general standing preference. A Skill is task-specific and loads only when the task at hand matches it. So custom instructions might set your overall tone, while a skill kicks in only when you're building, say, the monthly report.

Does Claude decide on its own which Skill to use?

Yes. When you give Claude a task, it reviews the skills available to it, recognizes which ones are relevant, and loads only those. You don't have to name the skill or switch it on for each task. This is what makes Skills feel effortless once they're set up — the right method shows up automatically.

Can my whole team use the same Skill?

Yes, on Team and Enterprise plans. An administrator can build or approve a skill and push it to everyone, so it appears automatically in each team member's skill list. This is the most powerful use for a company: it guarantees that everyone produces the proposal, the report, or the customer reply to the same standard, without each person setting it up themselves.

Are Skills locked into Claude?

No. Anthropic has published the Skills format as an open standard, which means the skills you write are described in a portable way that other AI tools adopting the standard can also use. The time you invest in writing down your methods isn't tied to a single product.

Want help turning your team's best methods into Skills that actually work? The Deployed Kickstart gets your team hands-on with Claude in a single day — including building your first Skills around your real tasks. The Partner program gives you ongoing support to expand your skill library and roll the best ones out across the business.