How do I install the Sop Generator skill?

Run npx skillmds add winbda/sop-generator in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Sop Generator safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Sop Generator?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Sop Generator free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Sop Generator?

Winbda (@winbda) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Sop Generator by winbda — Agent Skill

Name: Sop Generator
Rating: 4.666666666666667 (3 reviews)
Author: Winbda

Sop Generator

Create clear, step-by-step Standard Operating Procedures for any business process. TRIGGERS - Use this skill when: - User wants to document a process or create an SOP - User mentions standard operating procedures, process documentation, or playbooks - User wants to create repeatable workflows for their team

Winbda bae8449 2.6 KB Updated Sep 8, 2026 3 repo stars

File contents

SOP Generator

Overview

Creates clear, actionable SOPs that anyone can follow. Includes step-by-step instructions, decision trees, quality checks, and troubleshooting guides.

Workflow

Step 1: Understand the Process

Ask the user:

Process name: What is this SOP for?
Who performs it: Role/person responsible
Frequency: How often is this done?
Steps: Walk me through it (or describe the outcome)
Tools needed: Software, access, or resources required
Common mistakes: What goes wrong?

Step 2: Structure the SOP

# SOP: [Process Name]

## Document Info
| Field | Value |
|-------|-------|
| **Version** | 1.0 |
| **Created** | [Date] |
| **Owner** | [Name/Role] |
| **Frequency** | [How often] |
| **Est. Time** | [Duration] |
| **Last Updated** | [Date] |

## Purpose
[One sentence: why this process exists and what it achieves]

## Scope
- **Who**: [roles that use this SOP]
- **When**: [triggers for starting this process]
- **Prerequisites**: [what must be true before starting]

## Tools & Access Required
- [ ] [Tool 1] — [access level needed]
- [ ] [Tool 2] — [access level needed]

## Step-by-Step Procedure

### Step 1: [Action Verb] [What]
**Time**: ~X minutes
**Tool**: [if applicable]

[Clear instruction — one action per step]

> ⚠️ **Note**: [Important caveat or common mistake]

**Checkpoint**: [How to verify this step is done correctly]

### Step 2: [Action Verb] [What]
[Continue pattern...]

### Decision Point: [Question]
- **If YES** → Go to Step X
- **If NO** → Go to Step Y

## Quality Checklist
- [ ] [Check 1]
- [ ] [Check 2]
- [ ] [Check 3]

## Troubleshooting

| Problem | Likely Cause | Solution |
|---------|-------------|----------|
| [Issue 1] | [Why] | [Fix] |
| [Issue 2] | [Why] | [Fix] |

## Escalation
If something isn't covered above, contact:
- **[Role]**: [how to reach them]

## Change Log
| Date | Version | Changes | Author |
|------|---------|---------|--------|
| [Date] | 1.0 | Initial creation | [Name] |

Quality Checklist

Each step starts with an action verb
One action per step (not compound steps)
Decision points clearly mapped
Checkpoints after critical steps
Troubleshooting covers top 3-5 issues
Time estimates included
Tools and access listed upfront

---name: sop-generatordescription: Create clear, step-by-step Standard Operating Procedures for any business process. TRIGGERS - Use this skill when: - User wants to document a process or create an SOP - User mentions standard operating procedures, process documentation, or playbooks - User wants to create repeatable workflows for their team---# SOP Generator## OverviewCreates clear, actionable SOPs that anyone can follow. Includes step-by-step instructions, decision trees, quality checks, and troubleshooting guides.## Workflow### Step 1: Understand the ProcessAsk the user:1. **Process name**: What is this SOP for?2. **Who performs it**: Role/person responsible3. **Frequency**: How often is this done?4. **Steps**: Walk me through it (or describe the outcome)5. **Tools needed**: Software, access, or resources required6. **Common mistakes**: What goes wrong?### Step 2: Structure the SOP```markdown# SOP: [Process Name]## Document Info| Field | Value ||-------|-------|| **Version** | 1.0 || **Created** | [Date] || **Owner** | [Name/Role] || **Frequency** | [How often] || **Est. Time** | [Duration] || **Last Updated** | [Date] |## Purpose[One sentence: why this process exists and what it achieves]## Scope- **Who**: [roles that use this SOP]- **When**: [triggers for starting this process]- **Prerequisites**: [what must be true before starting]## Tools & Access Required- [ ] [Tool 1] — [access level needed]- [ ] [Tool 2] — [access level needed]## Step-by-Step Procedure### Step 1: [Action Verb] [What]**Time**: ~X minutes**Tool**: [if applicable][Clear instruction — one action per step]> ⚠️ **Note**: [Important caveat or common mistake]**Checkpoint**: [How to verify this step is done correctly]### Step 2: [Action Verb] [What][Continue pattern...]### Decision Point: [Question]- **If YES** → Go to Step X- **If NO** → Go to Step Y## Quality Checklist- [ ] [Check 1]- [ ] [Check 2]- [ ] [Check 3]## Troubleshooting| Problem | Likely Cause | Solution ||---------|-------------|----------|| [Issue 1] | [Why] | [Fix] || [Issue 2] | [Why] | [Fix] |## EscalationIf something isn't covered above, contact:- **[Role]**: [how to reach them]## Change Log| Date | Version | Changes | Author ||------|---------|---------|--------|| [Date] | 1.0 | Initial creation | [Name] |```## Quality Checklist- [ ] Each step starts with an action verb- [ ] One action per step (not compound steps)- [ ] Decision points clearly mapped- [ ] Checkpoints after critical steps- [ ] Troubleshooting covers top 3-5 issues- [ ] Time estimates included- [ ] Tools and access listed upfront

Frequently asked questions