---

name: knowledge-ops description: Use when Use when a Head of Ops, Knowledge Manager, or TPM-Internal needs to author, validate, or clean up company SOPs and internal runbooks (procurement intake, vendor offboarding, incident-comms cascade,...

Knowledge Ops

Use when a Head of Ops, Knowledge Manager, or TPM-Internal needs to author, validate, or clean up company SOPs and internal runbooks (procurement intake, vendor offboarding, incident-comms cascade, employee onboarding) — including 5W2H completeness checks (Who-What-When-Where-Why-How-HowMuch), cross-link and orphan-page validation across a sprawling Notion/Confluence/Obsidian wiki, KB ingestion + hygiene reporting, and runbook step verification (named owner, expected duration, observable success signal, rollback path, escalation contact). Pairs Ishikawa's 5W2H method, Gawande's The Checklist Manifesto, ISO 9001, ITIL v4, and Google SRE Workbook runbook discipline with deterministic stdlib-only Python tools that score completeness, detect anti-patterns, and emit prioritized cleanup lists (e.g., "validate this runbook before it goes into rotation", "audit our Confluence wiki for stale and orphaned SOPs"). — One of 337+ skills in Ali Reza's multi-agent claude-skills collection (Claude, Codex, Gemini, Hermes; ~19k stars).

What you get

• Public GitHub repo (alirezarezvani/claude-skills)
• the knowledge-ops skill folder with SKILL.md. Part of a 337-skill / 30-agent / 70-command install.

Customize your output

• Fork the repo and adapt the skill's instructions and references to your workflow.

Example output

Activates automatically when your request matches Knowledge Ops; chains with the other skills, agents, and commands in the collection.

Best for

Creators, builders, and teams using Claude Code.