Custom Claude Skills: Making the Small Business Pack Actually Fit Your Business

The most underrated feature in Claude for Small Business isn't any of the 15 workflows. It's the thing sitting quietly underneath them: skills — and specifically, the fact that you can write your own.

I use skills daily in my own Claude setup, and they're the mechanism that turns Claude from "impressively capable generalist" into "colleague who already knows how we do things here." This post explains what a skill actually is, why the stock ones are generic on purpose, what to encode first, and what a real skill file looks like.

What a skill actually is

Strip away the branding and a skill is refreshingly simple: a folder of markdown instructions, plus optional templates and scripts, that teaches Claude a repeatable task in your house style.

That's it. No fine-tuning, no training runs, no vector databases. You write down how a task should be done — the steps, the rules, the format of the output, the edge cases — the way you'd write an onboarding doc for a new hire. Claude reads it whenever the task comes up, in any chat or Cowork session, and does the task your way instead of a plausible generic way.

The small business plugin ships 15 prebuilt skills alongside its 15 workflows, covering finance, ops, sales, marketing, HR, and customer service. And anyone — including you, including someone you hire — can add custom ones.

Why the stock skills are generic (and why that's fine)

The prebuilt skills have to work for a plumber in Ohio, a design studio in Lisbon, and a three-person SaaS company on day one. So they encode the shape of each task — what a month-end close covers, what an invoice reminder should contain, how lead qualification generally works — without any opinion about your business.

That's the right call for a free plugin, and it's also why reviewers consistently land on the same verdict: useful immediately, generic until you add your own context. A stock invoice-chaser skill writes a competent, polite reminder. It doesn't know that you give long-standing clients a soft first nudge, that net-15 is non-negotiable for new clients, or that one particular account always pays after exactly one phone call and reminders are a waste of everyone's time.

Every one of those things is one sentence in a skill file. That's the entire trick.

What to encode first

If I were building a skill library for a small business from scratch, I'd write these four before anything else — in this order:

1. A business profile doc. One page: what you sell, to whom, your pricing structure, your team and who handles what, your busy seasons, the three things that make you different. Nearly every other skill and workflow gets sharper when this exists, because Claude stops guessing at context and starts using yours.
2. Brand voice. How you sound in writing — formal or warm, short or thorough, words you use, words you never use. Include two or three real examples of emails or posts that sound like you. This single skill upgrades every draft the content strategist and campaign workflows produce.
3. Your document formats. The invoice layout, the proposal structure, the weekly report your team actually reads. Attach a template file and describe what goes in each section. Output that matches your format needs no reformatting, which is the difference between a draft you use and a draft you rewrite.
4. Escalation rules. The judgment calls: which client emails the owner must see personally, what discount threshold requires sign-off, what a refund request over a certain amount triggers. Encoding these is what makes it safe to let Claude draft more, because the "stop and ask a human" lines are explicit. (These pair directly with the approval-gate habits I cover in Is Claude Safe for Your Business Data?)

A worked example: what a skill file looks like

Here's the skeleton of a custom invoice follow-up skill — generic on purpose, but structurally real:

invoice-follow-up/
├── SKILL.md
└── templates/
    └── reminder-email.md

And the SKILL.md itself:

# Skill: Invoice follow-up

Use this skill whenever drafting overdue-invoice reminders.

## Tone
Friendly and direct. Assume good faith — invoices get missed,
not dodged. Never apologize for asking to be paid.

## Sequence
- 7 days overdue: soft nudge. Reference the project by name,
  restate the amount and due date, attach the invoice.
- 21 days overdue: firmer. Note it's the second reminder and
  ask for a payment date.
- 35+ days overdue: do NOT draft an email. Flag for a phone
  call and surface the full history of this client's invoices.

## Rules
- Clients marked "legacy" in the CRM get an extra 7 days of
  grace before the first reminder.
- Never mention late fees — we don't charge them.
- Use the template in templates/reminder-email.md for structure.
- Anything over the flag threshold in our escalation rules goes
  to the owner before sending, no exceptions.

Twenty minutes of writing, and every invoice reminder from now on follows your collections philosophy instead of a generic one. That's the return profile of skills in general: small upfront writing cost, compounding payoff on every future run.

How skills compound with the workflows

This is the part that clicked the whole system into place for me. The 15 workflows are processes — the invoice chaser, the month-end prepper, the lead triager. Skills are the knowledge those processes draw on. They multiply:

• The invoice chaser workflow + your invoice follow-up skill + your brand voice skill = reminders that follow your sequence, in your voice, respecting your grace periods.
• The lead triager + a qualification-criteria skill = prioritization by your definition of a good lead, not a general one — the exact calibration problem I described in the HubSpot lead triage post.
• The business-pulse summary + your business profile doc = a summary that knows what "normal" looks like for your company and flags what's actually unusual.

Each skill you add upgrades every workflow that touches its territory. Four good skills don't make the system four increments better; they make most of the 15 workflows meaningfully yours at once.

When it's worth paying someone to build the library

Writing one skill is easy. Building a library — figuring out which twenty pieces of tribal knowledge are worth encoding, extracting them from the owner's head, writing them so they trigger reliably, testing them against real tasks, and revising the ones Claude misreads — is a genuine project. It's also where the fiddliness lives: the gap between a skill that exists and a skill that fires correctly every time comes down to how it's written and tested, and that's a craft you only develop by doing it a lot.

Two honest options, depending on depth:

• My Claude Small Business Setup Sprint — $1,250, fixed price — includes two custom skills alongside the full setup: plan selection, connectors, five configured workflows, team training, and 30 days of support. Right if you want the system running properly and a starter pair of skills built the correct way, which you can then imitate.
• The bigger sibling on the same page: a custom skills and automation build at $3,000–$6,000, where I build out the full skill library plus the event-driven automation layer for the things Claude won't do on its own — the scheduled and triggered runs I covered in What Claude for Small Business Can't Do. Right if you want the whole operating layer done, not started.

And the free option is real too: read this post again, write your business profile doc tonight, and build from there. The format is markdown and plain English. The barrier was never technical.

Frequently asked questions

Do I need to know how to code to write a custom Claude skill?

No. A skill is markdown — structured plain text — plus optional templates. Scripts can be included for advanced cases, but the four foundational skills I recommend (business profile, brand voice, formats, escalation rules) are pure writing. If you can write an onboarding doc for an employee, you can write a skill.

How is a skill different from just typing instructions into the chat?

Persistence and reuse. Chat instructions evaporate when the conversation ends; a skill is on file and applies every time the task comes up, for every run of every relevant workflow, without anyone remembering to paste it. It's the difference between telling a new hire something once in a hallway and putting it in the handbook.

How many custom skills does a small business actually need?

Fewer than you'd think. The four foundations cover most of the value, and I'd rather see a business with five well-written, well-tested skills than twenty vague ones. Add new ones when you catch yourself correcting Claude's output the same way twice — that repeated correction is the skill, waiting to be written down.

Can skills be wrong or go stale?

Yes, in exactly the way an employee handbook goes stale. If you change your pricing, your grace periods, or your escalation thresholds, the skill file needs the same edit. My habit: when a Claude draft surprises you, check whether the skill it drew on still says what you currently believe. Skills are documents, and documents need owners.

What's in the 15 prebuilt skills, and should I replace them?

They ship across finance, ops, sales, marketing, HR, and customer service, matching the workflow pack. Don't replace them — layer on them. The stock skills handle the general shape of each task competently; your custom skills add the opinions, formats, and rules that make the output yours. The combination beats either alone.

Want a skill library built by someone who writes these daily? The Claude Small Business Setup Sprint includes two custom skills, and the full library build is on the same page — or book a 15-minute call and tell me what your business does that no template knows.