CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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").

72

Quality

90%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

The canonical home for this skill is knowledge-ops in alirezarezvani/claude-skills

SKILL.md
Quality
Evals
Security

Quality

Content

81%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A strong, highly actionable body: copy-paste commands with flags and thresholds, a four-step workflow with explicit validation and a post-sprint verification loop, and useful assumptions/anti-patterns sections. The main costs are token efficiency — narrative scene-setting and repeated enumerations — and two long inline sections (forcing-question library, Distinct from) that would sit better in reference files.

Suggestions

Replace the narrative Purpose opener ('An ops organization three years in accumulates a sprawl...') with a compact bullet list of the seven failure modes; cut the scene-setting.

State the runbook six-check list once in the Scripts section and refer to it elsewhere ('the six checks above') instead of enumerating it in When to use, Workflow step 2, and Scripts.

Move the forcing-question library with its canon citations into a reference file (e.g., references/forcing_questions.md), keeping only a one-line pointer plus the tool invocation order in SKILL.md.

DimensionReasoningScore

Conciseness

The body is mostly dense and actionable, but there is trimmable content: the narrative Purpose opener ("An ops organization three years in accumulates a sprawl: 600 Notion pages, 200 Confluence runbooks, three Obsidian vaults...") is scene-setting Claude doesn't need, and the runbook six-check list (named owner, duration, success signal, failure signal, rollback, escalation contact) is enumerated three times (When to use, Workflow step 2, Scripts) and the regulated-profile overlays twice. It sits between anchors 2 and 3: several padded/repeated sections, but the majority of sections (Scripts, Assumptions, Anti-patterns) earn their tokens, so it is not 'noticeably verbose' overall.

3 / 5

Actionability

Guidance is copy-paste executable: concrete commands with flags ("kb_ingester.py --input <vault-dir>", "runbook_validator.py --input <runbook.md>", "sop_generator.py --input <metadata.json> --profile <ops|support|finance|hr|it|regulated>", "--stale-days"), explicit verdict thresholds ("≥ 80 = SAFE-TO-USE, 60-79 = USE-WITH-CAUTION, < 60 = NOT-SAFE"), defined output formats (traffic-light, validity score 0-100, top-20 cleanup list), and a self-contained runnable quick example ("python3 scripts/kb_ingester.py --sample"). Commands cover the common cases, matching the score-5 anchor; the sop_generator metadata fields are enumerated, leaving no material gap.

5 / 5

Workflow Clarity

The four-step flow is clearly sequenced with explicit validation checkpoints and a feedback loop: step 2 validates every runbook ("A runbook scoring < 60 is not safe to use in an incident"), and step 4 closes the loop ("Re-run kb_ingester.py after the cleanup sprint to verify orphan-page count is down and glossary drift is resolved"). A seven-question pre-flight checklist gates tool invocation. This matches the score-5 anchor (clear sequence, explicit validation, feedback loop, checklist) rather than 4, since checkpoints exist at both per-runbook and per-sprint level; the batch/destructive cap does not apply because cleanup is explicitly a 'priority queue, not a delete list' with post-sprint verification.

5 / 5

Progressive Disclosure

Structure is good: a clearly signaled References section with three one-level-deep files, each given a one-line scope (e.g., "references/runbook_canon.md — Google SRE Workbook (runbook chapter), Atlassian incident-management runbooks..."), and a Scripts section that abstracts the three tools with their flags. It falls short of 5 because the ~30-line forcing-question library with inline canon citations and the six-entry 'Distinct from' section are detail that belongs in reference files rather than the overview; it is above 3 because the references are clearly signaled and navigation is easy. (No references/ or scripts/ files were present in the bundle to verify the referenced paths.)

4 / 5

Total

17

/

20

Passed

Description

100%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

An exemplary description: explicit "Use when" triggers scoped to named personas, comprehensive concrete capabilities enumerated at attribute level, natural user phrasings including quoted example requests, and a clearly bounded organizational-knowledge-management niche. It is long but every clause carries capability or trigger information rather than padding.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions with attribute-level detail: "author, validate, or clean up company SOPs and internal runbooks", "5W2H completeness checks (Who-What-When-Where-Why-How-HowMuch)", "cross-link and orphan-page validation", "KB ingestion + hygiene reporting", and "runbook step verification (named owner, expected duration, observable success signal, rollback path, escalation contact)". Coverage is comprehensive with no gaps, matching the score-5 anchor rather than 4.

5 / 5

Completeness

It explicitly answers both: what ("score completeness, detect anti-patterns, and emit prioritized cleanup lists" plus the enumerated author/validate/cleanup capabilities) and when ("Use when a Head of Ops, Knowledge Manager, or TPM-Internal needs to author, validate, or clean up company SOPs and internal runbooks"), with concrete quoted trigger phrases — a clear score-5 match.

5 / 5

Trigger Term Quality

Natural terms users would actually say are covered including synonyms: "SOPs", "runbooks", "Notion/Confluence/Obsidian wiki", "vendor offboarding", "employee onboarding", plus quoted user utterances "validate this runbook before it goes into rotation" and "audit our Confluence wiki for stale and orphaned SOPs". This comprehensively covers natural phrasings, matching the score-5 anchor; score 4 would require missing common variations, which is not the case.

5 / 5

Distinctiveness Conflict Risk

A clear, well-bounded niche — organizational SOP/runbook authoring and KB hygiene for ops personas with named artifact types (SOP, runbook, glossary, wiki exports) — with distinct triggers unlikely to fire for adjacent skills. The persona scoping and specific artifact vocabulary give minimal conflict risk.

5 / 5

Total

20

/

20

Passed

Validation

81%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

relative_links

Relative link issues: 1 missing

Warning

referenced_paths_exist

Referenced path issues: 7 missing

Warning

Total

13

/

16

Passed

Repository

alirezarezvani/claude-skills

Path

.gemini/skills/knowledge-ops/SKILL.md

Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.