Knowledge Ops
Authors and audits company SOPs and runbooks with a completeness discipline, and cleans up sprawling internal wikis by finding orphaned or stale pages.
Before & after
Same prompt, same agent — the only difference is the skill.
A good SOP audit should look at the completeness and accuracy of your procedures. You'll want to check if they're up to date and if they actually reflect how things are done now. Make sure they have clear steps and that someone can follow them without getting stuck. It's helpful to talk to the people who actually do the work to see if the SOPs match reality. You might want to check if there are any processes that don't have SOPs yet. Creating a consistent template for your SOPs can help ensure they're all structured the same way. You could assign someone to review and update them regularly. Would you like suggestions on how to organize and structure your SOPs?
SOP AUDIT RESULTS
5W2H COMPLETENESS SCORECARD
SOP: 'Onboard new team member' (2025-01, last updated 2026-03)
Who: HR + manager (CLEAR)
What: 15-step process (CLEAR)
When: Duration? No. ADD 'Total time: 4 hours'
Where: Remote or office? No. ADD 'Location: office for day 1'
Why: Purpose stated? Yes (employee productivity)
How: Steps detailed? Partial. Step 7 'Configure laptop' lacks concrete details
How much: Budget/resources? MISSING. ADD 'Hardware budget: 2k per employee'
Score: 5/7 (71%)
SOP: 'Incident communication cascade' (2024-11)
Status: STALE (8 months old, org restructured 3 months ago)
Issue: Lists 'VP Engineering' as escalation (role eliminated, CTO now)
Gaps: No timeline ('notify within X minutes?'). No success criteria.
Action: Archive to 'Archive/Incident-Comms-v1-Outdated', create new version
ORPHAN PAGE DETECTION
Pages with no inbound links:
Vendor evaluation process (42 views, 6 months, not linked from procurement page)
→ Link from 'New vendor request' SOP
Broken outbound links:
Sales onboarding links to deleted 'CRM configuration guide' (removed 2026-05)
→ Replace with current 'Salesforce 2026 setup'
MISSING SOPS (ad-hoc processes)
Approve remote work exception (2 per month, ad-hoc since 2025)
Risk: HIGH (no consistency, no audit trail)
Action: Priority 1, create by end of week
Budget reallocation mid-quarter (1-2 per quarter, finance gap)
Risk: MEDIUM (delays decisions, unclear escalation)
Action: Priority 2, document by end of August
RUNBOOK VERIFICATION (5 SOPs sampled)
Vendor offboarding, Step 3 'Revoke access to systems'
Named owner? No. ADD 'Owner: IT Security'
Expected duration? No. ADD 'Est. 2 hours'
Observable success signal? No. ADD 'Success: All 47 systems report access revoked'
Rollback path? No. ADD 'Rollback: Restore from access-control backup (1-hour window)'
Escalation contact? Partial. CLARIFY 'If data not deleted by T+7, escalate to CTO'
CLEANUP ROADMAP
This week: Flag 'Incident communication cascade' stale
Next 2 weeks: Create 'Remote work exception' SOP (high-risk gap)
Next 4 weeks: Update 5W2H scores for top 10 SOPs (target 85%+)
Next 8 weeks: Full wiki audit (link orphans, verify no broken references)About this skill
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").
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.
SKILL.md preview
---
name: knowledge-ops
description: Use this skill when authoring, validating, or cleaning up company SOPs and internal runbooks, or auditing a wiki for stale and orphaned pages.
version: 1.0.0
category: Business & Ops / Operations
author: AgentVolt
license: proprietary
tags:
- business-ops
- operations
---
# Knowledge Ops
Authors and audits company SOPs and runbooks with a completeness discipline, and cleans up sprawling internal wikis by finding orphaned or stale pages, so operational knowledge is actually usable in a crisis.
## When to use
… (sign up to view the full skill)More business & ops skills
View all Business & Ops skills →Capacity Planner
Builds an ops headcount plan using queueing math, P90 demand sizing, and shrinkage-adjusted FTE counts, ending in a quarterly hiring sequence with ramp and attrition built in.
Vendor Management
Runs vendor scorecards, SLA compliance checks, and third-party risk classification for SaaS and supplier relationships.
Internal Comms
Drafts and sequences an internal-only change-management communication, pairing Prosci ADKAR and Kotter's 8-step model into a touchpoint calendar and message set.
Procurement Optimizer
Runs structured spend audits, UNSPSC-aligned category analysis, and supplier rationalization.