Short answer: A Claude Skill is a saved set of instructions that teaches Claude to do one repeat task your way, so you stop re-explaining it every time. Switch on the built-in skills in Settings, then use the skill-creator to build your first custom skill in about 30 minutes — no coding needed. Custom skills need a paid Claude plan (Pro starts at $20 a month). Start with the task you repeat most, not the cleverest one.
What is a Claude Skill, in plain words?
A Claude Skill is a folder of instructions that tells Claude how to handle one specific job. Inside sits a file called SKILL.md, written in plain Markdown, with a short header naming the skill and describing when it should be used. The folder can also hold templates, checklists, examples, and small scripts Claude can run. Anthropic launched Skills on 16 October 2025, published the format as an open standard in December 2025, and on 22 October 2026 donated it to the Agentic AI Foundation. Anthropic says more than 70 agent platforms, including ChatGPT, Cursor, GitHub Copilot, and VS Code, have adopted it since then, with 1 million skills published and nearly 280 million installed — Anthropic’s own figures, not independently verified.
The trick is what Anthropic calls progressive disclosure. Claude does not read your whole skill library on every message — it scans only the name and description of each skill, loads the one that matches, and ignores the rest. A prompt is a temp you brief from scratch every time; a skill is training done once, properly, with your examples and your rules.
Skills, Projects, and Custom GPTs: which one does what?
Claude already has Projects, and ChatGPT had custom GPTs, so it is fair to ask what skills add. The short version: Projects store context, skills store procedure. A Project holds the files and background for a client or a job; a skill holds the steps Claude should follow every time that kind of job comes up.
The custom GPT comparison matters most. OpenAI has been winding custom GPTs down — new creation is already gone from personal accounts, and full retirement has been targeted for December 2026. A skill is a folder of text files, not a feature locked inside one company’s product, and since the format is now an open standard, the same skill can load in Claude, ChatGPT, Cursor, and other tools that support it. Our guide to building a custom GPT for business still works for the migration decision, but if you are starting from scratch today, build a skill, not a GPT.
What does it cost to use Claude Skills?
Skills themselves carry no extra charge. The cost is the Claude plan, because custom skills need a paid plan with code execution enabled. Claude’s pricing page, read 6 November 2026, lists Pro at $20 a month ($17 a month if billed annually), Max at $100 a month, and Ultra at $200 a month, with Enterprise at $20 per seat a month plus usage billed at API rates. Our Claude vs ChatGPT subscription comparison puts those prices against OpenAI’s matching tiers.
| Plan | Price | Skills? | Who it suits |
|---|---|---|---|
| Free | $0 | No custom skills, per Anthropic | Trying Claude, not running a workflow on it |
| Pro | $20/mo ($17 annual) | Yes | Solo freelancer or owner — the sensible entry point |
| Max | $100/mo | Yes, 5x Pro usage | All-day Claude use across many tasks |
| Ultra | $200/mo | Yes, 10x weekly usage | Heavy, long-running work; overkill for most small firms |
| Team / Enterprise | From $20/seat/mo + usage | Yes, org-wide deployment | Teams that share skills; admins must enable them first |
Two things to note. On Team and Enterprise plans an admin has to enable Skills for the organisation first — if the toggle is missing, ask your admin. And the built-in document skills need code execution switched on in Settings; if a skill refuses to run, check that first. There is also a ready-made route: Claude for Small Business launched in May 2026 with 15 pre-built workflows, grown to more than 40 by September 2026, covering finance, sales, marketing, operations, and hiring. It runs as a plugin inside Claude, connects to QuickBooks, Google Sheets, HubSpot, Slack, Google Ads, and Outlook, and every action waits for your approval.
Step 1: switch on the built-in skills
Before building anything, turn on what Anthropic already ships: Word, Excel, PowerPoint, and PDF skills, plus a skill-creator skill and a brand-guidelines skill. They load automatically when the task calls for them.
- Open Claude and go to Settings, then Capabilities, and switch Skills on. Make sure code execution is enabled in the same place; without it, the document skills can’t run.
- Open Customize, then Skills. This is where you see what’s installed and add your own. (Anthropic has moved this menu before — if the labels differ, look under Settings or the “+” button beside the chat box.)
- Try one built-in skill on real work. Ask Claude to build a budget spreadsheet from your numbers. Watch the reply: Claude names the skill it loads as it works.
- Switch on the skill-creator. This is the skill that builds your other skills — it interviews you in plain conversation, then writes the SKILL.md file for you. Expect 15 to 30 minutes for your first working skill.
Step 2: build your first custom skill in 30 minutes
Anthropic’s own guide breaks skill creation into five steps, and they map neatly onto briefing a new hire. The example below is a client-proposal skill — the most useful first skill for a freelancer, because proposals are repeatable and high-stakes.
1. Pick the task with the five-times rule. Have you done this task at least five times, and will you do it at least ten more times? If yes, a skill pays. If no, a prompt is enough. Our guide to writing client proposals with AI shows the shape of the job: eight inputs, a fixed structure, pricing decided by you.
2. Write the name. Short, lowercase, hyphens instead of spaces — client-proposal, not “Client Proposal Generator v2”. The name and the description are the only parts of the file that decide whether Claude loads the skill, so they do the heavy lifting.
3. Write the description as a trigger, not a slogan. “Helps with proposals” tells Claude nothing. Write it from Claude’s point of view — what it does, what inputs it expects, and what it is not for. Name verbs (draft, structure, price), concrete situations (after a sales call, from call notes), and boundaries (never sets the price).
4. Write the instructions like a checklist. Plain Markdown, in order: what to ask first, what sections the output must have, what format, what to check before finishing. Put long reference material — your rate card, your terms, a past proposal — in separate files in the folder, so Claude only opens them when the job needs them.
5. Upload it and test it three ways. In Claude, go to Settings, then Skills, then Add, and either write the instructions directly or upload the skill folder as a .zip (the folder must be the root of the zip). Test with a normal request, an edge case (missing price, vague scope), and an out-of-scope request (ask for an employment contract — your proposal skill should stay asleep). If it fires when it shouldn’t, narrow the description. If it doesn’t fire when it should, widen it.
Here is the core of a proposal skill — a template, not a finished file:
--- name: client-proposal description: Drafts a client proposal from sales-call notes. Use when a call has ended and a proposal is due. Asks for price, timeline, and exclusions first. Never sets prices. --- # Client proposal ## Before drafting, ask for - Client name and business - My price for this job (never invent it) ## Output structure 1. Project summary, plain language 2. Scope of work, including what is NOT covered 3. Investment, stated directly, no hedging 4. Timeline, and the next step: confirm and pay ## Rules - Three options, not one price: core, recommended, premium - Proposal valid 14 days; 50% to start, 50% on delivery
One line in that file does most of the work: “My price for this job (never invent it)”. A skill is where you put the judgements you never want delegated — prices, terms, anything a client could hold you to — as fixed rules in the file, not suggestions in the chat.
Five skills worth building first
Don’t build a library. Build one skill, use it for two weeks, then build the next. These five cover the repeat work most small businesses actually have.
| Skill | What it holds | Trigger |
|---|---|---|
| Client proposal | Your structure, your terms, your rate card, three-option pricing | “Draft a proposal from these call notes” |
| Invoice chasing | Your reminder schedule, tone rules, escalation point, late-fee terms | “Who is overdue this week?” |
| Expense categorisation | Your chart of accounts, vendor rules, receipt format | Monthly, from a bank CSV export |
| Client onboarding | Welcome email, intake questions, contract checklist, first-week steps | “New client signed — start onboarding” |
| Meeting notes | Your format: decisions, owners, deadlines, open questions | After any call, from raw notes or a transcript |
The accounting three are the best documented: Xero’s guide walks through expense categorisation, bank reconciliation, invoice processing, cash flow checks, and month-end close, with the same pattern each time — export the data as a CSV, write the skill with your categories and matching rules, run it on the batch. Our invoice-chasing guide has the pricing ladder for the tools in this space, and our AI CRM guide covers the per-seat maths if your skill needs to touch a CRM. The pattern is always the same: the skill holds your rules, the export holds your data, and you approve the output before anything is sent or filed. If you already keep your process in a standard operating procedure, you are most of the way there. Our capture-first SOP guide shows how to record a process properly, and our guide to using Claude on long documents covers feeding a skill a 40-page contract.
Where Claude Skills break (and how to spot it)
Skills fail in predictable ways. The first is a vague description: Claude matches skills by meaning, not keywords, so “helps with documents” can fire on anything or nothing. If your skill never loads, the description is the first suspect; if it loads on the wrong job, it is too broad. The second is a stale skill: your prices and terms change, and the skill file doesn’t unless you update it. Put a review date in the file and re-check it whenever a price moves.
The third is security, and Anthropic says it plainly: skills can execute code, so only install skills from sources you trust. A malicious or careless skill can tell Claude to do things you didn’t intend. Treat installing a skill like installing software — check who wrote it, read the SKILL.md file before you enable it, and don’t install random skill packs because a video told you to. The open standard makes skills portable; it doesn’t make them safe. Finally, skills won’t fix a workflow that is broken in real life — if you can’t explain the task to a new hire in ten minutes, you can’t write a skill for it yet.
Is a skill worth the setup time?
This is the only question that matters, and it has an arithmetic answer. A skill costs a one-off setup — say 30 minutes with the skill-creator — and then saves a few minutes on every run. Break-even is setup time divided by saving per run. A proposal that takes 40 minutes today and 15 with a skill pays for itself on the second one. A 10-minute task that saves 2 minutes needs 15 runs — worth it weekly, not twice a year.
Skill payback calculator
Enter your own numbers. All fields are your estimates — the calculator only does the arithmetic.
How the calculator works: monthly saving equals runs per month times minutes saved per run, divided by 60 for hours; yearly saving is the monthly figure times 12; break-even runs equal setup minutes divided by minutes saved per run. This is our calculation from your inputs, not Anthropic data — the setup time and the saving per run are your estimates, so use honest numbers. One caution: don't count the first run, when you will check every line of output. The saving shows up from the second or third run, once you trust the format and only check the numbers.
What we can't confirm yet
Four things are genuinely unsettled. Plan availability: Anthropic's own pages say custom skills need a paid plan, but some secondary guides claim the feature has reached the Free plan — we go with Anthropic's pages. Menu labels: Anthropic has moved the Skills settings at least once, and guides disagree on the path. The Claude for Small Business workflow count (15 at launch, 40+ by September 2026) comes from vendor and partner pages, not Anthropic. And the custom GPT retirement date (December 2026) has already moved once. None of that changes the decision: the format is a vendor-neutral open standard, the skills you build are plain text files you own, and the cheapest test is one skill, one task, thirty minutes. The specification lives at agentskills.io.
Frequently asked questions
Do I need to know how to code to make a Claude Skill?
No. The skill-creator skill interviews you in plain conversation and writes the SKILL.md file for you — no coding, no file editing. Coding only enters the picture if you want the skill to run scripts, which is optional.
Are Claude Skills free?
The skills themselves cost nothing extra, but custom skills need a paid Claude plan — Pro at $20 a month ($17 on annual billing), Max at $100, or Ultra at $200, per Claude's pricing page read 6 November 2026.
What's the difference between a Claude Skill and a Custom GPT?
A Custom GPT is a tuned assistant locked inside ChatGPT, and OpenAI is retiring custom GPTs. A Claude Skill is a folder of text files in an open format — the same skill can load in Claude, ChatGPT, Cursor, GitHub Copilot, and VS Code.
Can I use a skill I built in Claude with ChatGPT or another tool?
Yes, in principle — that is the point of the open standard. Anthropic published the Agent Skills format at agentskills.io in December 2025 and donated it to the Agentic AI Foundation in October 2026, and more than 70 platforms have adopted it. In practice, test the skill in the other tool first.
How many skills should I build?
As few as possible. Anthropic's rule is to build a skill only for a task you've done at least five times and will do at least ten more. Most small businesses need three to five good skills, not fifty — a library nobody maintains goes stale.
Shurah is the founder of AI Tools Daily, tracking pricing, licensing and policy changes across AI tools so readers can make decisions without wading through marketing claims themselves.
