The Client SOP Skills Playbook

Anthropic's own engineers put it plainly: stop building a new agent for every job and package the know-how as skills instead. A skill is a folder with a SKILL.md file, plus any scripts and templates, that Claude opens only when a task needs it. These are the five client SOPs I would turn into skills first, the template to write each one in, and the rules that keep them reliable.

01Skill 01

Brand Voice: every draft sounds like the client on the first pass

Start here, because every other skill leans on it. Make a folder named client-voice with a SKILL.md inside. Paste the client's tone rules, the words they never use, and three real posts or emails they loved as examples. Then write the description as what it does and when to use it: 'Writes in Acme's brand voice. Use for any post, email or reply written for Acme.' Claude matches every request against that description, so a vague one means the skill never opens.

02Skill 02

Weekly Client Report: the same format every Monday, whoever runs it

Turn the report you already send into a skill. Put the one-page structure in SKILL.md, save your best past report as templates/report.md, and list where each number comes from. Bundled files cost nothing until Claude reads them, so the whole template library can live in the folder. If a step is pure math, like week-over-week change, put it in a small script: a script runs and only its output enters the conversation, so the math is done the same way every time.

03Skill 03

Lead Qualifier: every inbound lead scored against the same rules

Write the client's ideal customer as a checklist, a 1 to 5 scoring rubric and the next step for each score. Keep it to one job. Anthropic's own advice is that several focused skills compose better than one large one, so qualifying lives here and the reply lives in the Brand Voice skill. Run it on ten real past leads and compare its scores with yours before it touches a new one.

04Skill 04

Client Onboarding: the checklist you run for every new client, packaged

Every new client needs the same things: access to their tools, brand files, goals and a kickoff call. Write that SOP as numbered steps with the exact questions to ask. In Claude Code, a skill saved in the project's .claude/skills/ folder travels with the repo, so commit it and everyone on the project runs the same checklist. My editing agents work exactly like this: the reel that sent you here was made with my DOSSIER skill, one folder holding the stages, the checks and the house rules.

05Skill 05

Delivery QA: nothing reaches the client until it passes their rules

The last skill checks the work of the other four. List what must be true before anything ships: brand names spelled right, no claim the client cannot back up, every link opening, the approved format. Ask Claude to run the checklist and answer pass or fail, line by line. Keep API keys and passwords out of every skill file, and only install skills you wrote yourself or got from a source you trust.

SKILL.md template · one client SOP per folder

---
name: client-weekly-report
description: Writes Acme's weekly client report from last week's
numbers. Use when asked for the Acme report or a weekly update.
---
# Acme weekly report
## Steps
1. Pull last week's numbers from the sources listed in sources.md.
2. Fill templates/report.md. Keep every heading.
3. Run scripts/change.py for week-over-week change. Never estimate it.
## Rules
- One page, plain language, the client's words from voice.md.
- Flag anything you could not find. Never fill a gap.
## Done when
- Every section is filled and every number has a source.

Want this running for you?

Build it step by step inside AI Creative OS, with me in the thread.

Implement this today →

Not ready for that?

Drop your email and 3 more guides open in the Library, free.

Unlock all 78 guides

Implement this today →