borghei/Claude-Skills / business-operations/knowledge-ops
knowledge-ops
VerifiedAudit and repair an internal knowledge base — staleness, ownership gaps, orphans, duplication, and findability. Use when the wiki is untrusted, docs are out of date, nobody owns pages, or search returns the wrong answer.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 13.0 KB |
| assets/doc-ownership-charter.md | markdown | 3.4 KB |
| assets/kb-audit-report-template.md | markdown | 2.4 KB |
| assets/sample_kb.json | config | 3.9 KB |
| references/freshness-sla-and-ownership.md | markdown | 10.5 KB |
| references/information-architecture-patterns.md | markdown | 10.6 KB |
| scripts/doc_debt_ranker.py | script | 9.1 KB |
| scripts/kb_health_auditor.py | script | 10.2 KB |
| scripts/orphan_detector.py | script | 7.5 KB |
assets/doc-ownership-charter.md
View on GitHub# Document Ownership Charter
Adopt this as written or amend it deliberately. Its purpose is to make ownership a specific,
bounded, ten-minute-per-quarter commitment rather than an open-ended obligation people
reasonably decline.
---
## What an owner is
**A named person.** Not a team, not an alias, not a distribution list, not a role with no
current occupant. Teams may be recorded as a secondary routing field, but the review
notification goes to a human, because notifications sent to groups are read by nobody.
## What an owner is accountable for
1. **Accuracy at the review interval** for the page's tier.
2. **Deciding the page's fate at review time** — keep, update, merge, or archive. "Keep
as-is" is a valid and common outcome.
3. **Answering or routing questions** the page generates.
4. **Explicit handover** when changing role. An unhanded-over page is unowned.
## What an owner is NOT accountable for
- Writing all the content themselves
- Being the deepest subject expert
- Personally fielding every question
- Anything outside the review interval
## Tiers and intervals
| Tier | Test: if this were wrong for six months... | Review every | Stale at |
|------|-------------------------------------------|--------------|----------|
| Critical | someone takes a harmful action | 90 days | 120 days |
| Core | someone does their job badly and does not know | 180 days | 270 days |
| Reference | someone is mildly inconvenienced | 365 days | 540 days |
| Archive | nothing happens | never | never |
Tier by consequence, not by traffic. A rarely-read runbook is Critical; a popular FAQ is
Reference.
## The ten-minute review
1. **Is anything here now wrong?** No → re-date and you are done.
2. **Is anything missing that readers keep asking about?** Add it, or note it.
3. **Does this page still deserve to exist?** No → merge or archive.
About 60% of reviews end at step 1. If a review routinely takes an hour, the page is too
large — split it.
## Escalation when reviews go overdue
| Overdue by | What happens |
|-----------|--------------|
| 0-30 days | Reminder to the owner |
| 30-60 days | Reminder copies the owner's manager |
| 60-90 days (Critical) | Raised as a risk item; page shows a reader-visible "unverified" banner |
| 90+ days | Ownership reassigned, or the page is archived |
The visible banner is the point: it converts a hidden risk into one the reader can see.
## Handover
On role change, the outgoing owner either names a successor or returns the page to the
domain hub owner for reassignment. Pages returned and unclaimed after two rounds are
deletion candidates — non-acceptance is real information about whether the page matters.
## Deletion
Pages with zero inbound links and zero 90-day traffic are deleted, not archived. Version
history preserves them. Archive is for material with historical or compliance value, not for
material we are reluctant to delete.
Pages with inbound links are redirected, never removed silently. A 404 on a bookmarked page
costs more trust than the stale page did.
---
## Acceptance
| Page or space | Owner (named person) | Team | Tier | Accepted on |
|---------------|---------------------|------|------|-------------|
| | | | | |
Ownership is assigned on an **opt-out** basis: you are the owner of the pages listed above
unless you reply saying otherwise. Opt-out assignment achieves several times the coverage of
opt-in, and the pages nobody will claim are exactly the pages worth deleting.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |