How do I install the Sop Manager skill?

Run npx skillmds@latest add officebeats/sop-manager 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 Manager 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 Manager?

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

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

Who published Sop Manager?

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

Sop Manager by officebeats — Agent Skill

Name: Sop Manager
Rating: 4.666666666666667 (3 reviews)
Author: officebeats

Sop Manager

Create, normalize, organize, and validate privacy-safe SOPs, runbooks, checklists, and worked examples for product management and consulting workflows. Use for `/sop`, SOP capture from transcripts or docs, release/process runbooks, and local-only operating procedures.

officebeats Updated Sep 10, 2026

File contents

SOP Manager

Storage Contract

Real SOP content goes under 6. SOPs/ and is local-only.

Tracked toolkit skeletons go under:

.agent/templates/sops/
.agent/workflows/sop.md
.agent/skills/sop-manager/SKILL.md

Never store sensitive, stakeholder-specific, customer-specific, or meeting-specific SOP content in .agent/ templates.

Folder Taxonomy

Use domain-first routing:

6. SOPs/
  company/
    product-ops/
      release-management/
  consulting/
    client-delivery/
  shared/
    product-management/
    consulting/

Extend this structure only when the new folder is meaningful for repeated use.

SOP Artifact Types

Choose the smallest useful artifact set:

sop.md: stable, ticket/client/project-agnostic operating procedure.
runbook-template.md: fill-in template for the next execution.
example-runbook.md: specific worked example that may contain sensitive details.
checklist.md: operational checklist for repeated execution.
comms-template.md: manual-send message draft.

Workflow

Identify audience: product manager, program manager, consultant, CTT/release team, or leadership operator.
Extract the stable process from the source material.
Separate reusable process from one-time example details.
Route the SOP to 6. SOPs/<domain>/<type>/<process>/.
Use templates from .agent/templates/sops/ when creating new artifacts.
Keep source systems read-only.
Validate privacy with git check-ignore for real SOP content.
Report file paths, sources, and any assumptions.

Source-System Rules

Allowed:

Read local files.
Read scoped transcript/meeting/chat excerpts.
Read explicitly provided Jira or Confluence references.
Use source links in the SOP for traceability.

Prohibited:

Sending or drafting Slack/Teams/email messages unless explicitly asked for local copy text only.
Editing Jira or Confluence.
Adding comments, worklogs, transitions, assignments, or page updates.
Uploading files or transmitting sensitive data.

Quality Bar

Each reusable SOP must include:

Purpose.
When to use.
Inputs.
Roles.
Workflow steps.
Output artifacts.
Guardrails.
Validation checklist.
Template/runbook relationship when applicable.

Each runbook template must include:

Fill-in placeholders.
Source links.
environment/context fields when relevant.
Result capture.
Closeout checklist.

Each worked example must clearly say:

It is an example, not the reusable SOP.
It may contain local-only sensitive detail.
It should remain under 6. SOPs/ and ignored by git.

Privacy Validation

For every real SOP content file, run:

git check-ignore -v "<path>"

For every skeleton .gitkeep file intended to preserve folder structure, confirm it is not ignored:

git check-ignore -v "<path-to-.gitkeep>"

If a real SOP file is not ignored, stop and fix .gitignore before reporting completion.

---name: sop-managerdescription: Create, normalize, organize, and validate privacy-safe SOPs, runbooks, checklists, and worked examples for product management and consulting workflows. Use for `/sop`, SOP capture from transcripts or docs, release/process runbooks, and local-only operating procedures.---# SOP Manager## Storage ContractReal SOP content goes under `6. SOPs/` and is local-only.Tracked toolkit skeletons go under:```text.agent/templates/sops/.agent/workflows/sop.md.agent/skills/sop-manager/SKILL.md```Never store sensitive, stakeholder-specific, customer-specific, or meeting-specific SOP content in `.agent/` templates.## Folder TaxonomyUse domain-first routing:```text6. SOPs/ company/ product-ops/ release-management/ consulting/ client-delivery/ shared/ product-management/ consulting/```Extend this structure only when the new folder is meaningful for repeated use.## SOP Artifact TypesChoose the smallest useful artifact set:* `sop.md`: stable, ticket/client/project-agnostic operating procedure.* `runbook-template.md`: fill-in template for the next execution.* `example-runbook.md`: specific worked example that may contain sensitive details.* `checklist.md`: operational checklist for repeated execution.* `comms-template.md`: manual-send message draft.## Workflow1. Identify audience: product manager, program manager, consultant, CTT/release team, or leadership operator.2. Extract the stable process from the source material.3. Separate reusable process from one-time example details.4. Route the SOP to `6. SOPs/<domain>/<type>/<process>/`.5. Use templates from `.agent/templates/sops/` when creating new artifacts.6. Keep source systems read-only.7. Validate privacy with `git check-ignore` for real SOP content.8. Report file paths, sources, and any assumptions.## Source-System RulesAllowed:* Read local files.* Read scoped transcript/meeting/chat excerpts.* Read explicitly provided Jira or Confluence references.* Use source links in the SOP for traceability.Prohibited:* Sending or drafting Slack/Teams/email messages unless explicitly asked for local copy text only.* Editing Jira or Confluence.* Adding comments, worklogs, transitions, assignments, or page updates.* Uploading files or transmitting sensitive data.## Quality BarEach reusable SOP must include:* Purpose.* When to use.* Inputs.* Roles.* Workflow steps.* Output artifacts.* Guardrails.* Validation checklist.* Template/runbook relationship when applicable.Each runbook template must include:* Fill-in placeholders.* Source links.* environment/context fields when relevant.* Result capture.* Closeout checklist.Each worked example must clearly say:* It is an example, not the reusable SOP.* It may contain local-only sensitive detail.* It should remain under `6. SOPs/` and ignored by git.## Privacy ValidationFor every real SOP content file, run:```bashgit check-ignore -v "<path>"```For every skeleton `.gitkeep` file intended to preserve folder structure, confirm it is not ignored:```bashgit check-ignore -v "<path-to-.gitkeep>"```If a real SOP file is not ignored, stop and fix `.gitignore` before reporting completion.

Frequently asked questions