Back to Library
SOP Writer
Client Delivery and Service Operations
Client Delivery
Beginner
v1•Updated 6/6/2026SKILL.md Preview
--- name: sop-writer description: Use this skill when the user asks Claude to write an SOP, document a process, build a repeatable workflow, or turn a Loom or transcript into steps a team can follow. Trigger when the user mentions handing off a process, documenting how they do something, or phrases like 'document this so I can delegate it.' This skill helps produce a standardized SOP document with quality checks. compatibility: Claude.ai, Claude Desktop --- # SOP Writer ## Purpose Turn a process into a standard operating procedure on one fixed structure, so every SOP has the same shape and a new hire can follow any of them. ## When to Use This Skill Use it to capture and standardize any repeatable process for delegation or training. ## When Not to Use This Skill Do not use it for one-time tasks with no repeat value or for strategy documents. Do not use it without enough detail to describe the steps. ## Required Inputs - The process being documented. - Who performs it and how often. - The tools involved. - The trigger that starts it and the result that ends it. ## Workflow 1. If the source is a transcript or recording, extract the steps first, then fill gaps with the user. 2. State the purpose and why it matters. 3. Define scope, owner, and prerequisites. 4. Write numbered imperative steps, one action each, noting decision points and branches. 5. Add quality checks per phase, common errors and fixes, and a clear definition of done. ## Output Format Return the SOP: Purpose, Scope and Owner, Prerequisites, Steps, Quality Checks, Common Errors and Fixes, Definition of Done. Produce a Word doc on request; otherwise inline. ## Quality Standards - Steps are imperative and single-action. - Decision points and branches are explicit. - Quality checks and error recovery are included, not just raw steps. - Uses contractions, no em dashes, no hype. ## Edge Cases If the process has hidden branches, ask about them; a process with undocumented decisions breaks on handoff. If the source is a messy transcript, reconstruct the logical order rather than transcribing literally. ## Safety and Limitations Do not document processes that facilitate deception or unauthorized access. Keep the SOP to legitimate operational tasks. ## Test Prompts 1. Document my process for onboarding a new copywriting client into an SOP my assistant can follow. It starts when they sign and ends when the kickoff call is booked. 2. Here's a Loom transcript of me publishing a blog post in WordPress. Turn it into a step-by-step SOP with quality checks before publishing. 3. Write an SOP for how we handle a refund request, including the decision points for approve, partial, or deny, so any support rep can follow it.
Skill Details
What it does
Converts a described or recorded process into a standardized operating procedure.
When to use it
Use this skill when the user asks Claude to write an SOP, document a process, build a repeatable workflow, or turn a Loom or transcript into steps a team can follow. Trigger when the user mentions handing off a process, documenting how they do something, or phrases like 'document this so I can delegate it.' This skill helps produce a standardized SOP document with quality checks.
Expected output
SOP document
Included files
- SKILL.md
Package Preview
sop-writer/
SKILL.md
README.txt
Trigger Phrases
- "Document my process for onboarding a new copywriting client into an SOP my assistant can follow. It starts when they sign and ends when the kickoff call is booked."
- "Here's a Loom transcript of me publishing a blog post in WordPress. Turn it into a step-by-step SOP with quality checks before publishing."
- "Write an SOP for how we handle a refund request, including the decision points for approve, partial, or deny, so any support rep can follow it."