A skill is a folder Claude reads before it does the job your way
Mechanically, a Claude Skill is a directory. Inside it sits a file called SKILL.md, plain text with a short header (its name and a description of when to use it) followed by instructions in ordinary language.
The folder can also hold extra files: a template, a reference document, a small script, sample output. A folder and a text file, nothing more, is the entire mechanism. No new software, no dashboard to learn.
Claude does not load every skill into every conversation. At the start of a chat it only reads each installed skill's name and description, a few lines each.
When you ask for something that matches one, Claude reads that skill's full SKILL.md. If the skill points to extra files, Claude opens those only if the task actually needs them.
Anthropic calls this progressive disclosure, and the plain version is: a table of contents first, the chapter if it is relevant, the appendix only if you need that much detail. It is why you can have 20 skills installed without every chat getting slower.
An example. An invoice skill's SKILL.md might read: "Use this when asked to create a client invoice. Net-30 terms unless told otherwise. List each line as quantity x rate.
Round tax to 2 decimals. Sign off with our standard line." Once that exists, you type "invoice Riverside Plumbing for 3 hrs at $85/hr plus $40 in parts" and Claude applies every rule in that format without being told again.
The difference between a skill and typing the same instructions every time
You can already tell Claude your invoice rules in any chat. The problem is you have to tell it again in the next one. Say that takes 2 minutes and you send 20 invoices a month: `2 min x 20 = 40 min/mo` spent re-explaining a rule you already explained, every month, forever.
A skill removes that cost once, permanently, because Claude checks for it automatically instead of waiting to be reminded.
Skills also travel further than a single chat's instructions. Because Anthropic published the skill format as an open standard in December 2025, the same SKILL.md works in Claude.ai, in Claude Code, and through the API, and in principle on any agent that adopts the standard.
A rule typed into one conversation dies with that conversation. A rule saved as a skill does not.
What a useful skill looks like for a small business
None of this needs to be complicated. The skills that earn their keep for an owner-operator are the small, boring, repeated jobs already eating your week.
Anthropic ships its own pre-built skills for common document work, creating and editing PowerPoint, Excel, Word, and PDF files, so you are not starting from zero even before you write anything custom.
Its Claude for Small Business plugin goes further: 15 skills and 15 ready-made workflows across finance, operations, and marketing, wired to its launch connectors including QuickBooks and Google Workspace, at no added product fee.
Three ways a non-technical owner actually gets a skill built
- Turn on a pre-built one. Anthropic and partners including Canva, Notion, Zapier, Atlassian, Figma, and Stripe publish ready-made skills. You switch one on in Settings, or install a plugin that bundles several at once, no writing required.
- Have Claude build it with you. Anthropic's built-in skill-creator tool asks you plain questions about the task you keep repeating, then writes the SKILL.md itself from your answers. You describe the workflow once in your own words; you do not touch a line of code.
- Get a custom one built around your real process. A pre-built skill does not know your numbering scheme or your supplier's exact form. Someone who already has your rules and documents, whoever set up the rest of your business knowledge base, can turn your actual process into a working skill in an afternoon rather than you learning the format yourself. That is the kind of setup we do in month one.
One practical note: turning on a pre-built skill needs almost nothing. Building your own with skill-creator needs the Claude desktop app, code execution turned on, and a paid plan, not the free tier.
Skills are not the same thing as a Project, and not the same thing as a Plugin
Three words get used loosely, and they mean different things. A Project is where your facts live: your price list, your refund policy, your supplier terms, the documents Claude reads before it answers.
A skill is where your procedure lives: not what is true, but how to do one specific recurring task once the facts are in front of it.
A plugin is the delivery box, a single install that can bundle several skills together with workflows and connectors, the way the Claude for Small Business plugin bundles 15 skills with 15 workflows in one install.
You can have a Project with no skills attached, just documents Claude reads on request. You can have a skill with no Project behind it, a generic formatting rule that does not depend on your specific numbers.
The useful combination is a skill that leans on your Project's files, so an invoice skill pulls the client's actual name and price from documents already sitting in your knowledge base instead of asking you to retype them.
Skills ship at no added fee on Pro, Max, Team, and Enterprise, the same way connectors and Cowork do (our Claude pricing breakdown covers the plans in full). You are not billed per skill and not billed per plugin.
Running a skill still counts against the normal usage limits of whatever plan you are on, so a heavy day of report-building can still hit a cap the way any other heavy day would.
The free plan has much lower usage limits and does not reliably support the code execution skills rely on, so treat skills as a paid-plan feature in practice: if you already pay $17-20/mo for Pro, skills add $0 on top.
Where a skill runs out
- A skill changes how, not what. If the SKILL.md says "always apply net-30 terms" but your actual terms vary by client, the skill will apply the wrong term with total confidence. It still needs your real facts behind it, not just a tidy procedure.
- Badly written skills fail quietly. A vague description means Claude never notices the skill applies, so it silently never fires. An overly broad one fires on tasks it should not touch. Either way, you find out from the output, not from an error message.
- Skill sprawl is a new kind of clutter. 15 skills nobody has opened since install day are 15 places stale instructions can rot without you noticing, the same way an unused app or a forgotten spreadsheet does.
- A skill does not fact-check. It formats and follows procedure. It does not independently verify a number against reality unless you built that check into the instructions yourself.
- Anything a customer reads still needs a human pass. A skill can draft the reply in your voice. It should not be the last step before send. See how to handle AI customer comms safely.
Bottom line: a skill is a cheap, low-drama way to stop re-explaining yourself to Claude. It will not fix a business whose rules were never written down in the first place, and it will happily produce a beautifully formatted wrong answer if the instructions behind it are wrong or the facts feeding it are stale.
