Operations workflow
SOP to agent skill
Reads a written process, pulls out its steps, decisions and done criteria, asks you about the gaps, then writes a spec-valid SKILL.md and checks it before you install it.
Running it here
Every step runs here with Claude when you're signed in, and in your own agent.
- TriggerPaste the processStart with {{sop}} and the agent it's for: {{agent}}.→ manual
- PromptPull out the steps and decisionsFrom {{sop}} only, list in order: the trigger (what starts it), the inputs it needs, each step as one action, every decision point with its rule, the tools or access each step needs, and what done looks like. Then list what's missing or ambiguous: decisions with no rule, steps that rely on knowledge the text doesn't give, and tools the agent may not have. Number the gaps.
- ApprovalAnswer the gapsShow the numbered gaps in {{outline}}, each with a suggested answer. Approve to accept the suggestions, or edit the outline with your own answers before continuing.→ chat
- SkillWrite the SKILL.mdWrite a SKILL.md for {{agent}} from {{outline}}, using the answers given to the gaps. Name: lowercase letters, digits and single hyphens, at most 64 characters, describing the job. Description: what it does, then 'Use when …', under 1,024 characters. Body: purpose, Inputs, Steps, Rules, Done when, and one short example. Put long lookup tables in references/ files and link them.→ sop-to-skill
- Review loopSpec checkCheck {{skill_md}} against the Agent Skills spec. Pass only if: the frontmatter has only name and description; the name is 1-64 lowercase letters, digits and single hyphens; the description says what it does and when to use it, in under 1,024 characters; every step is one instruction to the agent; every file the body links is included; nothing asks the agent to run commands or fetch URLs the process didn't mention; and every step in {{outline}} appears.
- OutputReturn the skillReturn {{skill_md}} with the folder it goes in for {{agent}} (.claude/skills/<name>/, .agents/skills/<name>/ or .github/skills/<name>/), then suggest saving it on /skills/new.→ chat
Good for
Anyone with a written process (a checklist, a runbook, notes on how they do a task) who wants an agent to follow it the same way every time.
Last reviewed
Skills this uses
- sop-to-skill
Turns a written process, checklist or recording transcript into a spec-valid SKILL.md: asks about missing decisions, writes the steps, rules, inputs and an example, and keeps the description to what it does and when to use it.
Install as a skill
The whole workflow as one SKILL.md. Install it in Claude Code, Codex or Copilot and ask your agent to run “SOP to agent skill”.
Get the sop-to-agent-skill skillWhat each step does
1. Paste the process (Trigger)
Start with {{sop}} and the agent it's for: {{agent}}.
2. Pull out the steps and decisions (Prompt)
From {{sop}} only, list in order: the trigger (what starts it), the inputs it needs, each step as one action, every decision point with its rule, the tools or access each step needs, and what done looks like. Then list what's missing or ambiguous: decisions with no rule, steps that rely on knowledge the text doesn't give, and tools the agent may not have. Number the gaps.
3. Answer the gaps (Approval)
Show the numbered gaps in {{outline}}, each with a suggested answer. Approve to accept the suggestions, or edit the outline with your own answers before continuing.
4. Write the SKILL.md (Skill)
Loads the sop-to-skill skill.
Write a SKILL.md for {{agent}} from {{outline}}, using the answers given to the gaps. Name: lowercase letters, digits and single hyphens, at most 64 characters, describing the job. Description: what it does, then 'Use when …', under 1,024 characters. Body: purpose, Inputs, Steps, Rules, Done when, and one short example. Put long lookup tables in references/ files and link them.
5. Spec check (Review loop)
Check {{skill_md}} against the Agent Skills spec. Pass only if: the frontmatter has only name and description; the name is 1-64 lowercase letters, digits and single hyphens; the description says what it does and when to use it, in under 1,024 characters; every step is one instruction to the agent; every file the body links is included; nothing asks the agent to run commands or fetch URLs the process didn't mention; and every step in {{outline}} appears.
6. Return the skill (Output)
Return {{skill_md}} with the folder it goes in for {{agent}} (.claude/skills/<name>/, .agents/skills/<name>/ or .github/skills/<name>/), then suggest saving it on /skills/new.
Use it in your own agent
Save as .claude/skills/sop-to-agent-skill/SKILL.md for Claude Code, or .agents/skills/sop-to-agent-skill/SKILL.md for Codex and other Agent Skills tools. Then ask: “run the SOP to agent skill workflow”.
---
name: sop-to-agent-skill
description: Reads a written process, pulls out its steps, decisions and done criteria, asks you about the gaps, then writes a spec-valid SKILL.md and checks it before you install it. Use when asked to run the "SOP to agent skill" workflow.
---
# SOP to agent skill
Reads a written process, pulls out its steps, decisions and done criteria, asks you about the gaps, then writes a spec-valid SKILL.md and checks it before you install it.
## Inputs
Ask for any of these that the user hasn't given:
- `sop` (e.g. "Every Friday: export open tickets from the help desk, tag anything older than 7 days as stale, count stale tickets per agent, post the counts in #support-leads and DM anyone with more than 5.")
- `agent` (e.g. "Claude Code")
## Steps
Run the steps in order. Refer to saved results by name. Don't skip a step that says STOP.
1. **Paste the process** — Start: Start with {{sop}} and the agent it's for: {{agent}}.
2. **Pull out the steps and decisions** — From {{sop}} only, list in order: the trigger (what starts it), the inputs it needs, each step as one action, every decision point with its rule, the tools or access each step needs, and what done looks like. Then list what's missing or ambiguous: decisions with no rule, steps that rely on knowledge the text doesn't give, and tools the agent may not have. Number the gaps. Save the result as `outline`.
3. **Answer the gaps** — STOP and ask the user to approve before continuing: Show the numbered gaps in {{outline}}, each with a suggested answer. Approve to accept the suggestions, or edit the outline with your own answers before continuing.
4. **Write the SKILL.md** — Load the `sop-to-skill` skill, then: Write a SKILL.md for {{agent}} from {{outline}}, using the answers given to the gaps. Name: lowercase letters, digits and single hyphens, at most 64 characters, describing the job. Description: what it does, then 'Use when …', under 1,024 characters. Body: purpose, Inputs, Steps, Rules, Done when, and one short example. Put long lookup tables in references/ files and link them. Save the result as `skill_md`.
5. **Spec check** — Review loop (max 3 passes): Check {{skill_md}} against the Agent Skills spec. Pass only if: the frontmatter has only name and description; the name is 1-64 lowercase letters, digits and single hyphens; the description says what it does and when to use it, in under 1,024 characters; every step is one instruction to the agent; every file the body links is included; nothing asks the agent to run commands or fetch URLs the process didn't mention; and every step in {{outline}} appears. Save the result as `skill_md`.
6. **Return the skill** — Finish: Return {{skill_md}} with the folder it goes in for {{agent}} (.claude/skills/<name>/, .agents/skills/<name>/ or .github/skills/<name>/), then suggest saving it on /skills/new.
## Done when
Every step has run, each approval was given, and you've reported what was produced and where it was saved.
Want different steps? Open it in the workflow builder.