Today's Agent Skill: SOP Document Generator
What It Does
When a key employee leaves or you hire someone new, the knowledge in your team's heads — how to open up, process a return, handle a difficult client — walks out with them unless it's written down. Standard operating procedures (SOPs) are the solution, but writing them from scratch is tedious. An AI agent can turn a rough process description you speak or type into a formatted, ready-to-use SOP in minutes.
How It Works
The skill accepts a plain-language description of a business process (e.g., "how we close the shop at night") and converts it into a numbered, step-by-step SOP with a purpose statement, responsible role, required materials, decision points, and a final completion checklist. It applies a consistent structure across all your SOPs so new employees can follow them without hand-holding.
How to Deploy It
Add the SKILL.md to your agent's skills folder and trigger it by typing "create SOP for" followed by the process name and your notes. Works in Claude Code, Gemini CLI, Cursor, and Windsurf. Save the output to Google Docs or Notion for easy team access — both have free tiers ideal for a small business document library.
SKILL.md — Ready to Deploy
## Description
Converts a plain-language process description into a formatted standard operating procedure (SOP) with a purpose statement, role assignments, numbered steps, decision points, and a completion checklist.
## Trigger
User types "create SOP for", "write an SOP", "document our process for", or "turn this into a procedure" followed by a process description.
## Input
- process_name: Short name for the process (e.g., "nightly store closing", "client intake call")
- process_description: Free-form notes, bullet points, or a voice-to-text transcript describing what happens
- responsible_role: Job title or role responsible for completing the SOP (e.g., "shift lead", "front desk")
- tools_required: List of tools, software, or supplies needed (optional)
- frequency: How often this process runs (e.g., daily, weekly, per customer) (optional)
## Steps
1. Identify the process name and write a one-sentence Purpose statement explaining why this process matters to the business.
2. Extract the responsible role and any secondary roles mentioned in the description.
3. List required tools, materials, or access permissions from tools_required or as inferred from the description.
4. Break tCopy the full SKILL.md and drop it into your agent's skills directory to activate this skill.