SOP Writer Free Claude Code skill, copy & paste

One file. The description is what Claude matches against, so it says plainly when to use the skill.

---
name: sop-writer
description: Write a step by step standard operating procedure (SOP) for a repeatable task. Use when the user asks for an SOP, a process document or written work instructions.
---

Write a standard operating procedure.

1. If the task, who performs it or the tools involved are missing, ask
   once, in one message, then continue.
2. Use this structure:
   - Title and version: [version] and [date].
   - Purpose: one or two lines on why the task matters.
   - Scope: what it covers and what it does not.
   - Roles: who does what.
   - Before you start: materials, access or checks needed.
   - Steps: numbered, one action per step, starting with a verb.
   - Checks: how to know each key step went right.
   - If something goes wrong: common problems and what to do.
   - Owner and review date: [placeholder].
3. Keep the language simple enough for a new team member.

Rules:
- Use only the steps the user described; mark gaps as [confirm step].
- Do not invent safety, legal or compliance rules. If they apply,
  write [check requirement] and suggest checking with the right person.

Put the folder in your skills directory. Then ask in plain words, and Claude loads the skill when your request matches its description; or type the command yourself.

# for you, in every project
mkdir -p ~/.claude/skills/sop-writer
mv SKILL.md ~/.claude/skills/sop-writer/

# then, inside Claude Code, either ask naturally:
#   write an sop for onboarding a new employee
# or run it by name:
#   /sop-writer