How to Turn Your Company SOPs into Claude Skills: A Small Business Playbook

Introduction

Your business already runs on instructions — refund procedures, quote templates, onboarding checklists, the monthly close ritual only one employee fully understands. These are your standard operating procedures (SOPs): usually a Google Doc, a Notion page, or worse, one person’s head. Our beginner’s tutorial showed how a Claude Skill works: a folder with a SKILL.md file that teaches Claude to do one task your way. This playbook goes the other way — it turns an SOP you already have into a working Skill, so Claude follows your company procedures instead of improvising. Two hours for the first; under an hour each after that.

What You’ll Need

• One written SOP — a Google Doc, a Notion page, even a photo of a whiteboard — that someone actually follows today.
• A claude.ai Pro, Max, Team, or Enterprise plan with code execution enabled (Settings > Features) — where you upload custom Skills.
• A plain-text editor (Notepad, TextEdit, VS Code).

Step 1: Pick the Right SOP to Convert

Convert the procedures that hurt most when done inconsistently — score candidates on:

• Frequency: weekly or daily tasks (lead follow-ups, support triage) pay back fastest.
• Pain: tasks that break when a step is skipped — wrong quotes, missed disclaimers, inconsistent refunds.
• Documented: a written SOP converts in an afternoon. A procedure “only Linh knows” needs a walkthrough first.

Good first candidates: your refund workflow, client quote process, new-hire onboarding, blog publishing checklist. Skip procedures that change weekly, and anything holding secrets like passwords or API keys — credentials never belong in a Skill file.

Step 2: Read Your SOP Like an Editor

SOPs written for humans carry baggage: tribal knowledge (“ask the manager” — which one?), vague steps (“check quality”), steps nobody can explain. Read yours and fix three things:

• Ambiguity: “send a polite follow-up” is ambiguous. Decide what polite means in your company — and put the actual template in the Skill.
• Missing context: if the SOP says “use the standard discount,” write down what that discount actually is.
• Dead steps: steps that exist because “we’ve always done it this way.” Converting to a Skill is your excuse to delete them.

After this pass you’ll have a clean procedure of one to three pages — the raw material for Step 5.

Step 3: Set Up the Skill Folder

Create a folder named for the procedure — lowercase, hyphens, no spaces, e.g. refund-request-workflow — containing:

• SKILL.md — the brain: YAML frontmatter (name + description) plus the instructions.
• REFERENCE.md (optional) — the full original SOP, linked from SKILL.md. Claude opens it only when the fine print is needed, so it costs nothing until used.
• EXAMPLES.md (optional) — one or two anonymized input/output examples. Examples teach tone and format faster than adjectives.

This is Anthropic’s progressive disclosure: at startup Claude reads only each Skill’s name and description (~100 tokens). The SKILL.md body loads when the Skill triggers; reference files load only when needed. Several focused Skills compose better than one giant “do everything” Skill.

Step 4: Write the Description That Triggers

The description is what Claude matches your request against, so it must say both what the Skill does and when to use it (max 1,024 characters):

---
name: refund-request-workflow
description: Follows our company refund procedure — eligibility check, approval thresholds, and the customer reply template. Use when the user mentions refunds, refund requests, or returns.
---

Name rules: max 64 characters, lowercase letters/numbers/hyphens, no “anthropic” or “claude”, no XML tags — gerund form (processing-refunds) works well. If the Skill never fires, the description is too narrow or missing trigger phrases; if it fires wrongly, it’s too broad. As our SKILL.md anatomy guide notes, most misfires are fixed at the description level.

Step 5: Rewrite the SOP as Instructions

Rewrite your cleaned SOP as the SKILL.md body, for an extremely capable new hire. Four rules from Anthropic’s authoring guidance:

• Concise is key. Don’t explain what a refund is. Add only what Claude doesn’t know — your rules, thresholds, tone, templates. Keep SKILL.md under 500 lines; split detail into reference files.
• Match specificity to fragility. Flexible tasks (drafting emails) get plain-text guidance; fragile sequences (“approvals over $200 need the owner’s sign-off”) get rigid checklists.
• Structure like an onboarding doc: context, numbered steps, hard rules (“never offer cash refunds over $50 without approval”), one worked example.
• Build in validation. Add a checklist Claude can check its own output against. Avoid time-sensitive info — move expiring details to the reference file with a “last updated” date.

Step 6: Zip, Upload, and Install

Zip the folder — with the folder inside the zip, not the files loose at the zip root. Then install where your team works:

• claude.ai: Settings > Features > Skills > Upload Skill. Note: custom Skills here are per-user — each teammate uploads the same zip. They don’t sync across accounts.
• Claude API: upload via the Skills API; API skills are workspace-wide. They run in a sandboxed container with no network access.
• Claude Code: drop the folder into ~/.claude/skills/ (personal) or .claude/skills/ (project).

Custom Skills don’t sync across surfaces — upload separately everywhere you want them.

Step 7: Test, Roll Out, Maintain

• Test with realistic prompts — the exact words your team would use (“customer wants a refund on order #4821”). Three to five variations.
• Review Claude’s thinking after upload to confirm the Skill loads; fix the description first when it misfires.
• Baseline it: run the same task without the Skill and note what goes wrong — that tells you what instruction to add.
• Pilot with one person for a week before rolling out, with a one-page “when to use it” note.
• Review quarterly. Procedures change. A Skill with stale rules enforces the wrong procedure confidently — worse than no automation. Put a review date on REFERENCE.md.

Tips From Teams That Did This

• Start with the Skill you’ll use tomorrow — the refund workflow you handle five times a week, not the contingency plan you handle never.
• Keep Skills narrow. “Refund requests” and “support triage” should be two Skills. Focused Skills compose; bloated ones misfire.
• Record tacit knowledge. If a procedure lives only in someone’s head, Claude’s record-a-skill builds a Skill from a ~10-minute screen recording. The video isn’t retained — only reviewable screenshots.
• Audit like software. Review bundled Skill files the way you’d review an install — especially third-party Skills. Watch for unexpected network calls or operations that don’t match the stated purpose.

Frequently Asked Questions

Do I need a written SOP first?

It helps but isn’t required. Record the task with record-a-skill, then clean up the generated Skill — most teams end up with a better SOP as a side effect.

How many SOPs should I convert?

Start with one — the most frequent painful procedure. Three to five well-maintained Skills beat twenty stale ones.

Can my team share one Skill on claude.ai?

Not automatically — custom Skills on claude.ai are per-user, so each teammate uploads the same zip. For org-wide distribution, the API’s workspace-wide Skills are the cleaner option.

Conclusion

Converting SOPs into Skills is how a small business gets more out of Claude: your procedures are your playbook, and a Skill makes Claude follow them every time. Pick one painful, frequent procedure, clean it up, write a triggering description, keep the body concise, test with realistic prompts, review it quarterly. The second Skill takes half the time.