How do I install the Sop Writer skill?

Run npx skillmds add majiayu000/sop-writer 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 Writer 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 Writer?

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 Writer free to use?

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

Who published Sop Writer?

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

Sop Writer by majiayu000 — Agent Skill

Name: Sop Writer
Rating: 4.2 (5 reviews)
Author: majiayu000

Sop Writer

Write a Standard Operating Procedure (SOP) for any operational task. Use when asked to write an SOP, standard operating procedure, work instruction, or operating manual. Produces a formal SOP with purpose, scope, procedure steps, quality checks, and version control.

majiayu000 680cf1f 2 files · 3.4 KB Updated Sep 9, 2026 567 repo stars

File contents

SOP Writer Skill

Produces formal, audit-ready SOPs suitable for regulated industries, ISO certification, or operational scaling.

Required Inputs

SOP title (e.g. "SOP-001: New Client Onboarding")
Department / function
Process description
Regulatory or quality standard (ISO 9001, GMP, CQC, FCA, etc.)
Roles involved
Tools or equipment used

Output Structure

[COMPANY NAME] — Standard Operating Procedure

Document ID	[SOP-XXX]
Title	[Title]
Department	[Department]
Version	1.0
Effective date	[Date]
Review date	[Date]
Status	Draft / Under review / Approved

1. Purpose

[1-2 sentences. Why does this SOP exist?]

2. Scope

Applies to: [Roles, departments, locations] Does not apply to: [Explicit exclusions]

3. Definitions

Term	Definition
[Term]	[Plain English definition]

4. Responsibilities

Role	Responsibility
[Role]	[Specific responsibility]

5. Required Materials / Tools / Access

[Item]

6. Procedure

Step	Action	Responsible	Record/Output
6.1.1	[Imperative action: "Open [system] and navigate to [location]"]	[Role]	[What to record]

NOTE: Steps must be written in imperative form. Each step must have one action only.

7. Quality Checks

Check point	What to verify	Pass criteria	If fail
[After step X]	[What to check]	[What good looks like]	[What to do]

8. Non-Conformance

[Immediate action]
[Who to notify]
[How to document deviation]

9. References

[Related SOPs, policies, standards]

10. Document History

Version	Date	Author	Changes
1.0	[Date]	[Name]	Initial release

Quality Checks

All steps written in imperative form ("Open...", "Navigate...", "Confirm...")
Each step has exactly one action
Role specified for every step
Quality checkpoints at critical stages
Non-conformance process defines who to notify and how to document
Document history table and review date are included

Example Trigger Phrases

"Write an SOP for [process]"
"Create a standard operating procedure for [task]"
"Write a work instruction for [process]"

---name: sop-writerdescription: Write a Standard Operating Procedure (SOP) for any operational task. Use when asked to write an SOP, standard operating procedure, work instruction, or operating manual. Produces a formal SOP with purpose, scope, procedure steps, quality checks, and version control.--- # SOP Writer Skill Produces formal, audit-ready SOPs suitable for regulated industries, ISO certification, or operational scaling. ## Required Inputs - **SOP title** (e.g. "SOP-001: New Client Onboarding") - **Department / function** - **Process description** - **Regulatory or quality standard** (ISO 9001, GMP, CQC, FCA, etc.) - **Roles involved** - **Tools or equipment used** ## Output Structure --- **[COMPANY NAME] — Standard Operating Procedure** | Document ID | [SOP-XXX] | |---|---| | Title | [Title] | | Department | [Department] | | Version | 1.0 | | Effective date | [Date] | | Review date | [Date] | | Status | Draft / Under review / Approved | --- ### 1. Purpose [1-2 sentences. Why does this SOP exist?] ### 2. Scope **Applies to:** [Roles, departments, locations] **Does not apply to:** [Explicit exclusions] ### 3. Definitions | Term | Definition | |---|---| | [Term] | [Plain English definition] | ### 4. Responsibilities | Role | Responsibility | |---|---| | [Role] | [Specific responsibility] | ### 5. Required Materials / Tools / Access - [Item] ### 6. Procedure | Step | Action | Responsible | Record/Output | |---|---|---|---| | 6.1.1 | [Imperative action: "Open [system] and navigate to [location]"] | [Role] | [What to record] | NOTE: Steps must be written in imperative form. Each step must have one action only. ### 7. Quality Checks | Check point | What to verify | Pass criteria | If fail | |---|---|---|---| | [After step X] | [What to check] | [What good looks like] | [What to do] | ### 8. Non-Conformance 1. [Immediate action] 2. [Who to notify] 3. [How to document deviation] ### 9. References [Related SOPs, policies, standards] ### 10. Document History | Version | Date | Author | Changes | |---|---|---|---| | 1.0 | [Date] | [Name] | Initial release | ## Quality Checks - [ ] All steps written in imperative form ("Open...", "Navigate...", "Confirm...") - [ ] Each step has exactly one action - [ ] Role specified for every step - [ ] Quality checkpoints at critical stages - [ ] Non-conformance process defines who to notify and how to document - [ ] Document history table and review date are included ## Example Trigger Phrases - "Write an SOP for [process]" - "Create a standard operating procedure for [task]" - "Write a work instruction for [process]"

Frequently asked questions