Home / Knowledge hub / Claude skills explained

Guide · Claude skills

Claude skills explained: what they are and how to use them in your business

What Claude skills are, where they work, how they differ from prompts, projects and CLAUDE.md, ten ideas for a service business and how to share them safely.

The short version

  • A Claude skill is a folder with a SKILL.md file of instructions, plus any templates, reference files or scripts Claude needs for one kind of job.
  • Claude only reads the full skill when a task calls for it, so you can have dozens installed without clogging up every conversation.
  • Skills work in the Claude apps, in Claude Code and through the API, and they now live on one Plugins page alongside connectors.
  • The best first skills are the jobs your team repeats every week: proposals, quotes, client reports, onboarding emails.
  • Skills can contain scripts, so only install ones you've written yourself or that come from a source you trust.

If you've used Claude for more than a few weeks, you've probably got a document somewhere full of prompts you keep pasting in. The proposal one. The one that makes reports sound like you. And you've probably noticed it still forgets half of what you told it last time. Skills fix that. A Claude skill is a folder of instructions, templates and optional scripts that Claude picks up automatically whenever a task matches, so it does the job your way every time without you pasting anything.

This guide explains what skills are in plain English, where they work, how they compare with prompts, projects and CLAUDE.md, and how to write one that's actually useful. There are ten ideas at the end for a typical service business, plus the safety points you need to know before installing anything.

What is a Claude skill?

A skill is a folder with a file called SKILL.md inside it. That file holds a short name, a description of when to use it, and then the instructions themselves, written in ordinary language.

The folder can also hold anything else Claude needs for that job. A price list. Your proposal template. Three examples of reports clients loved. A small script that turns a spreadsheet into a chart. Anthropic describes skills as folders of instructions, scripts and resources that Claude loads when a task calls for them.

The clever part is how they load. Claude doesn't read every skill at the start of every chat. It only sees the name and description of each installed skill, which takes up very little space. When you ask for something that matches, say "draft a proposal for Hargreaves Joinery", Claude spots that your proposal skill fits and reads the full instructions then. Long reference material inside a skill costs almost nothing until it's needed, which means you can install lots of them without slowing anything down or confusing Claude.

In practice a skill is a written procedure. The kind you'd give a sharp new starter on day one, except Claude actually reads it every single time.

In short. A prompt is something you say once. A skill is something Claude knows how to do from now on.

Where do Claude skills work?

Skills work in three places: the Claude apps (web, desktop and mobile), Claude Code, and the Claude API. The format is the same everywhere, but how you install them differs.

In the Claude apps

Skills are available on Free, Pro, Max, Team and Enterprise plans. They need code execution and file creation switched on in your settings, because many skills create files or run small scripts. Anthropic ships a set of ready made skills (for working with Word, Excel, PowerPoint and PDF files, for example), and you can add your own by packaging the skill folder as a ZIP file and uploading it.

In Claude Code

In Claude Code, skills are simply folders on your computer. Personal skills live in a skills folder inside your Claude settings and follow you across every project. Project skills live inside the project itself, in .claude/skills/, so anyone who works on that project gets them too. You can let Claude use a skill whenever it judges it relevant, or run it yourself by typing a slash and its name, for example /proposals.

Through the API

If you're building your own software on Claude, custom skills can be uploaded through the API and shared across your workspace. That's developer territory, but it matters because a skill you write once for the apps can, in principle, be reused in a tool your developers build later.

Anthropic has also published the format as an open standard called Agent Skills, so the same folder structure is starting to be supported by other AI tools as well.

How are skills different from prompts, projects and CLAUDE.md?

They all give Claude instructions, but they're loaded at different times and suit different jobs. The short version: a prompt is for one conversation, a project holds background for a body of work, CLAUDE.md sets standing rules for a folder, and a skill is a reusable procedure for one type of task.

OptionWhat it isWhen Claude reads itBest for
PromptWhat you type in the chatOnce, in that conversationOne off requests
Project (Claude apps)A workspace with uploaded files and custom instructionsEvery chat inside that projectOngoing work for one client or topic
CLAUDE.md (Claude Code)A file of standing rules in a folderAt the start of every session in that folderHouse rules that always apply, like tone or where files go
SkillA folder with SKILL.md and supporting filesOnly when a task matches its descriptionRepeatable jobs with a clear method

The difference that matters most is loading. Everything in a project's instructions or a CLAUDE.md file is read every time, whether it's relevant or not. Put your whole proposal method, your report method and your onboarding method in there and Claude has to wade through all of it to answer a simple email. Skills keep each method in its own box until it's needed.

They also travel. A project belongs to one place. A skill works in any chat or any project where it's switched on.

Most businesses end up using all four together. A short CLAUDE.md or project instruction for the rules that always apply, and a handful of skills for the jobs you do over and over.

What is the new Plugins page in Claude?

Anthropic has merged skills, connectors and plugins into a single Plugins page in the Claude apps. The sidebar item that used to say Customize now says Plugins, and one page replaces the separate Skills, Connectors and Plugins tabs.

The rollout started on 29 October 2026 for Free, Pro, Max and Team plans, with general availability on 9 November. Enterprise plans get it from 30 November 2026. Anything you'd already installed stays where it was. You can filter the page to show just skills or just connectors, and each card tells you what type it is. To use a skill directly in a chat, click the plus button or type a slash.

A quick bit of vocabulary helps here. A connector links Claude to another app, like your email or CRM, and is built on MCP. A plugin is a bundle that can contain skills, connectors and other extras in one installable package. A skill on its own is the instructions. The new page simply puts them all in one list.

If you're an admin on a Team or Enterprise plan, check your organisation settings. Plugins need code execution and file creation turned on at organisation level, and Anthropic's help article warns that if Skills is left off, plugins stop working in Claude Desktop, Cowork and the Code tab from 30 November.

How do you write a good Claude skill?

Start with a job you've already done well at least ten times, write down exactly how you do it, and give it a description that tells Claude precisely when to use it. The description is the bit most people get wrong.

Here's a short outline for a proposal writing skill. The folder would be called proposals and this is the SKILL.md inside it:

---
name: proposals
description: Writes client proposals and quotes in our house style.
  Use when asked to draft, rewrite or price a proposal for a new
  or existing client.
---

# Proposal writer

## Before you start
1. Ask for the client name, their problem in their own words,
   and the budget if they gave one.
2. Read pricing.md for current prices. Never invent a price.

## Structure
1. Their situation, in two short paragraphs
2. What we recommend and why
3. What's included and what isn't
4. Price, timings and next step

## Tone
UK English. Plain and warm. No jargon. Short paragraphs.

## Before handing back
Check every price against pricing.md and flag anything
you weren't sure about.

Supporting files in this folder:
pricing.md, examples.md, template.docx

A few things make the difference between a skill that gets used and one that gets ignored.

  • Write the description like a trigger. Say what the skill does and the words people will actually use when they need it. "Use when asked to draft, rewrite or price a proposal" works far better than "Proposal helper".
  • Keep one job per skill. A skill that writes proposals, chases invoices and plans social posts will be picked at the wrong moments. Split it up.
  • Move the long stuff into separate files. Keep SKILL.md short and readable. Price lists, examples and style guides go in their own files that SKILL.md points to. Anthropic suggests keeping SKILL.md under 500 lines.
  • Include real examples. Two good past proposals teach Claude more about your style than a page of adjectives.
  • Tell it what not to do. "Never invent a price" and "never promise a delivery date" save a lot of embarrassment.
  • Test it on a real job, then fix it. Your first version will be wrong in small ways. Each time you correct Claude, add the correction to the skill.

You don't need to write it all by hand either. You can ask Claude to interview you about how you do a task and draft the skill for you, then edit what it produces.

Tip. The fastest way to build a good skill is to do the job once with Claude, correcting it as you go, then say "turn what we just did into a skill". You'll get something close to right on the first go.

Ten skill ideas for a service business

The best skills cover jobs that happen every week, follow a method you can describe, and currently depend on one person remembering how it's done. Here are ten that work well for most service businesses.

  1. Proposal writer. Turns discovery call notes into a proposal in your structure, using your current prices.
  2. Quote builder. Works out a quote from a rate card and a job description, showing its sums so you can check them.
  3. Monthly client report. Takes the numbers and a few notes and writes the report in the same format every month, leading with what matters to the client.
  4. Brand voice checker. Reads any draft and rewrites it to match your tone, with your banned words and phrases listed.
  5. Client onboarding pack. Produces the welcome email, the access checklist and the kickoff agenda for a new client from a single form.
  6. Meeting notes to actions. Turns a call transcript into a summary, a list of actions with owners and a follow up email.
  7. Case study writer. Interviews you about a project and writes it up as a case study with the problem, the work and the result.
  8. Job ad and interview pack. Writes a job ad, a scoring sheet and interview questions in your style for any role.
  9. Complaint reply. Drafts a calm, fair reply to an unhappy customer following your policy, ready for a human to check and send.
  10. Policy and process writer. Turns a messy explanation of how something's done into a clean, numbered procedure for the team handbook.

Pick two to start. Proposals and client reports tend to save the most time because they're long, repetitive and need to be consistent.

How do you share skills across a team?

On Team and Enterprise plans you can share a skill with specific colleagues or publish it to your whole organisation. In Claude Code, you share skills by keeping them in the project folder.

In the Claude apps, a skill you upload is private until you share it. An owner first has to allow sharing in the organisation settings. After that you can share a skill with named people (or groups, on Enterprise), and they can switch it on and use it but not edit it. When you update the skill, they get the new version automatically next time they use it. Admins can also provision skills centrally, and those are switched on for everyone by default.

In Claude Code, project skills sit inside the project folder, so if that folder is shared through version control, everyone working on it picks up the same skills. Personal skills stay on your own machine.

Whichever route you use, give every shared skill an owner. Someone needs to update the price list when prices change and fix the skill when it starts producing something odd. A skill nobody maintains slowly goes stale, and stale instructions are worse than none because people trust them.

This is a big part of what we do when we set up a Claude workspace for a business: working out which jobs deserve a skill, writing them with the people who actually do the work, and agreeing who looks after each one. If you'd rather start on your own, our guide to setting up Claude Code for a business covers the basics.

Are Claude skills safe?

Skills you write yourself are as safe as the instructions inside them. Skills from anywhere else need checking first, because they can contain scripts that run on a computer and can tell Claude to install other software.

Anthropic's own guidance is to install skills only from trusted sources. The main risks it names are prompt injection, where hidden instructions steer Claude into doing something you didn't ask for, and data being sent somewhere it shouldn't go. A skill shared on a forum or in a public code repository could look helpful and still do either.

A sensible routine before switching on any skill you didn't write:

  • Read the SKILL.md in full. It's plain text and usually short.
  • Open every script in the folder, or ask someone technical to. If a skill for writing proposals contains code that sends data to a web address, that's a red flag.
  • Prefer skills from Anthropic, from the official Plugins directory or from software companies you already use.
  • On Team and Enterprise plans, decide who's allowed to share and publish skills, rather than leaving it open to everyone.
  • Keep sensitive personal data out of skills themselves. Anthropic notes, for instance, that its healthcare agreement doesn't cover skills, plugins or connectors.

Rule of thumb. Treat a skill from the internet like a macro in an email attachment. Probably fine, but you'd want to know where it came from before you open it.

Used carefully, skills are one of the most practical things in Claude for a small business. They capture how your best people do a job and make that the default for everyone, which is where the real time saving comes from.

Questions people ask

What is a Claude skill?

A Claude skill is a folder containing a SKILL.md file with instructions for a specific task, plus optional extras like templates, reference documents and scripts. Claude sees a short description of every installed skill and loads the full instructions only when a task matches. Think of it as a written procedure Claude follows whenever that job comes up.

Are Claude skills free?

Skills are available on the Free, Pro, Max, Team and Enterprise plans, though they need code execution and file creation switched on. There's no separate charge for using a skill, but the work Claude does counts towards your normal plan usage. Check claude.com/pricing for current plan prices.

What's the difference between Claude skills and Claude Code skills?

They're the same idea and use the same SKILL.md format. In the Claude apps you upload a skill as a ZIP file or install one from the Plugins page. In Claude Code, skills are folders on your computer or in a project, and you can also run them by typing a slash and the skill name.

Can I share a skill with my team?

Yes. On Team and Enterprise plans you can share a skill with named colleagues or publish it to the whole organisation, once an owner has switched sharing on. In Claude Code, the usual route is to keep skills in the project folder so everyone who works on that project gets them.

Are Claude skills safe to install?

Skills you write yourself are as safe as the instructions you put in them. Skills from elsewhere can include scripts and can tell Claude to install software, so Anthropic advises only installing them from trusted sources. Read the SKILL.md and any scripts before you switch one on.

Start with a 20 minute call

Which part of your week would you hand to a machine first?

Tell us on a short call. You'll leave with a straight answer on what's possible, what it costs and whether it's worth doing.