How do I install the Sop Writer skill?

Run npx skillmds@latest add garphengate/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. 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?

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

Sop Writer by garphengate — Agent Skill

Name: Sop Writer
Author: GarphenGate

File contents

SOP Outline

Free gateway skill from the SOP Writer bundle by GarphenGate.

The skeleton that makes starting easy — and shows where the real SOP will need meat.

Procedure

Get the two-minute version. Ask the owner to describe the task as if telling a new employee in a hallway. Capture verbatim.
Pre-seed the skeleton: pull the trigger, the rough steps, and any tools mentioned straight from their description into the template below.
Mark every gap visibly with a question in place of content — "Done when? (how do you know this step worked?)" — so the empty spots teach what a real SOP needs.
Add the two exception prompts at the bottom: "Last time this went wrong, what happened?" and "What would a new person mess up?" — answered later, they become the SOP's most valuable lines.
Hand it over with one instruction: fill it in the next time you actually do the task, not from memory at a desk.

Output contract:

SOP OUTLINE: <task>  (skeleton — fill in while doing the task)
Purpose (one sentence): ...
Who does this: ...   Triggered by: ...   Tools: ...
Steps (one action each, note what 'done' looks like):
  1. <seeded from your description> — Done when: ?
  2. ...
When does this go differently?: ?
What would a new person get wrong?: ?
Stop and ask <who?> if: ?

Rules

Never present the seeded skeleton as a finished SOP; it says 'skeleton' in the title and keeps its question marks until the owner answers them.
Never seed more than the owner actually said; invented steps in a skeleton become false memories in the final document.
One skeleton per task; a hallway description that spans two outcomes gets two skeletons.
Steps touching legal, tax, or safety matters get a 'have a professional review this' tag, not improvised content.

Degradation

If the owner can't spare two minutes to describe the task, output the blank template with its embedded questions — it stands alone as a paper form anyone in the shop can fill in during the next run.

Like this? This is the free gateway skill for SOP Writer by Moltline Studio. The paid listing: https://www.agensi.io/skills/sop-writer-persona

---name: sop-writerdescription: Generate a fill-in skeleton for documenting any recurring task, pre-seeded from a two-minute description; use to start documenting today without the full interview.---# SOP Outline*Free gateway skill from the SOP Writer bundle by GarphenGate.*The skeleton that makes starting easy — and shows where the real SOP will need meat.## Procedure1. **Get the two-minute version.** Ask the owner to describe the task as if telling a new employee in a hallway. Capture verbatim.2. **Pre-seed the skeleton**: pull the trigger, the rough steps, and any tools mentioned straight from their description into the template below.3. **Mark every gap visibly** with a question in place of content — "Done when? (how do you know this step worked?)" — so the empty spots teach what a real SOP needs.4. **Add the two exception prompts** at the bottom: "Last time this went wrong, what happened?" and "What would a new person mess up?" — answered later, they become the SOP's most valuable lines.5. **Hand it over** with one instruction: fill it in the next time you actually do the task, not from memory at a desk.Output contract:```SOP OUTLINE: <task> (skeleton — fill in while doing the task)Purpose (one sentence): ...Who does this: ... Triggered by: ... Tools: ...Steps (one action each, note what 'done' looks like): 1. <seeded from your description> — Done when: ? 2. ...When does this go differently?: ?What would a new person get wrong?: ?Stop and ask <who?> if: ?```## Rules- Never present the seeded skeleton as a finished SOP; it says 'skeleton' in the title and keeps its question marks until the owner answers them.- Never seed more than the owner actually said; invented steps in a skeleton become false memories in the final document.- One skeleton per task; a hallway description that spans two outcomes gets two skeletons.- Steps touching legal, tax, or safety matters get a 'have a professional review this' tag, not improvised content.## DegradationIf the owner can't spare two minutes to describe the task, output the blank template with its embedded questions — it stands alone as a paper form anyone in the shop can fill in during the next run.---*Like this? This is the free gateway skill for **SOP Writer** by Moltline Studio. The paid listing: https://www.agensi.io/skills/sop-writer-persona*

Frequently asked questions

Sop Writer