Anthropic Claude Skills: 10 SMB-grade skills to build first
Claude Projects are the right unit of organisation. Claude Skills are the recipes inside those Projects. Most SMBs roll out Projects and then leave them as generic chat surfaces - which leaves most of the value on the table. The teams that get compounding returns are the ones who build a small set of named, reusable Skills early. Here are the ten we install first across XLev clients.
What a Claude Skill actually is
A Claude Skill is a named instruction pack inside a Claude Project. Each Skill has a clear name, a description of when to use it, the steps and output format Claude should follow, and example input-output pairs. Anyone with access to the Project can invoke the Skill by name and get consistent output every time.
A Skill takes 30-60 minutes to build once you know the format. The payback per Skill is usually 10-20 hours per month of saved time across the team that uses it.
The ten Skills to build first
1. Meeting-note summary
Input: a meeting transcript or rough notes. Output: a structured summary with key points, decisions, action items with owners, and open questions. Project: Operations. Owner: ops lead or EA.
2. Proposal draft from a brief
Input: a sales brief (client, scope, key constraints). Output: first-draft proposal in your firm’s template and voice. Project: Sales. Owner: sales lead.
3. Customer email triage and draft
Input: an inbound customer email. Output: a one-line summary, a category (sales, support, complaint, other), an urgency rating, and a suggested response in your tone. Project: Sales or Support. Owner: customer service lead.
4. Hire-shortlist evaluator
Input: a CV plus the job spec. Output: a structured evaluation against the role’s requirements, a recommendation (yes/maybe/no) with reasoning, and three follow-up interview questions. Project: People. Owner: hiring manager or HR lead.
5. Weekly board update writer
Input: weekly KPI numbers, key wins, key issues. Output: a structured weekly update in your board’s preferred format. Project: Leadership. Owner: COO or chief of staff.
6. Content-brief expander
Input: a one-line content brief. Output: a full content outline with key points, target audience, tone notes and suggested structure. Project: Marketing. Owner: marketing lead.
7. Supplier-comparison matrix
Input: supplier websites or quotes. Output: a comparison matrix across price, terms, lead time and other named criteria, with a recommendation. Project: Operations or Finance. Owner: ops or purchasing lead.
8. Customer-feedback synthesiser
Input: a batch of customer feedback (survey responses, reviews, NPS comments). Output: themes, frequency counts, sentiment, and notable individual comments worth surfacing. Project: Product or Customer Success. Owner: product or CS lead.
9. Onboarding-task generator
Input: a new hire’s role and start date. Output: a checklist of the onboarding tasks for that role, with owners and timing, grounded in your onboarding playbook. Project: People. Owner: HR lead or hiring manager.
10. Incident-report writer
Input: incident details (what happened, when, who was affected, what was done). Output: a structured incident report in your format, with root cause analysis prompts and follow-up recommendations. Project: Operations or Engineering. Owner: ops lead or engineering lead.
How to build each one
The pattern is mechanical once you have done it twice:
- Pick the workflow. It should be something that runs at least once a week and currently takes 20-60 minutes manually.
- Write the steps Claude should follow. Three to seven steps is the sweet spot.
- Specify the output format. Be concrete: headings, bullet lists, table columns, length.
- Provide two or three example inputs and the matching outputs you would actually accept.
- Test by invoking the Skill three times on real inputs. Tighten the steps and examples based on what comes back.
- Ship it to the team. Tell them how to invoke it.
Total time per Skill: 30-60 minutes once you have done two or three. The first ones take longer.
Ownership and maintenance
Every Skill needs a named owner - usually the function lead whose Project the Skill lives in. The owner is responsible for keeping the Skill working as the business changes (new templates, new tone guides, new SOPs). A monthly 15-minute review per Project is enough to keep the Skills sharp.
Skills with no owner go stale fast. Skills with an owner compound for years.
When to build an eleventh
The right time to add a new Skill is when a manual workflow has recurred more than three times and would take less than an hour to convert. The wrong time is when you are brainstorming theoretical Skills nobody has yet asked for. Skills built from live workflow pain compound; Skills built from theoretical possibility usually die.
Frequently asked questions
- What are Claude Skills?
- Claude Skills are named instruction packs that live inside a Claude Project and teach Claude how to do a specific recurring task. Each Skill includes a clear name, a description of when to use it, the steps and format Claude should follow, and example inputs and outputs. Once built, anyone with access to the Project can invoke the Skill by name and get consistent output without having to explain the context each time.
- How are Skills different from a system prompt?
- A system prompt is the persistent instruction that frames everything Claude does inside a Project - tone, format defaults, refusal rules. A Skill is a named recipe inside that Project that you invoke for a specific task. Think of the system prompt as the rules of the workspace and Skills as the named procedures the workspace knows how to run.
- How long does it take to build a useful Skill?
- 30-60 minutes once you know the format. The first time you build one it takes longer because you are also designing the format. By the third or fourth Skill, you have a template and the build becomes mechanical: name it, describe when to use it, write the steps, paste two or three examples of inputs and outputs, save.
- Who should build Skills in our business?
- The function lead who owns the Project. If the operations function lead owns the operations Project, they own the Skills inside it. They know the workflow well enough to specify it correctly. The CEO or AI lead can review and quality-check, but should not be the one building. Skills built by people who do not own the workflow tend to be theoretical.
- How many Skills should we have?
- Per Project, 8-15 is the sweet spot. More than that and the team forgets which Skill does what; less than that and you are leaving leverage on the table. The maintenance habit is the same as for Projects: a named owner, a monthly review, and the discipline to retire Skills that are not being used.
Where this fits
Claude Implementation
Install Claude properly across your team - Claude Code, Claude.ai projects and skills, custom Anthropic SDK builds.