Skip to content

borghei/Claude-Skills / business-operations/knowledge-ops

knowledge-ops

Verified

Audit 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.

assets/kb-audit-report-template.md

View on GitHub
# Knowledge Base Audit — <scope>

**As-of date:** <YYYY-MM-DD> (required — an undated audit cannot be trended)
**Scope:** <spaces / directories included>
**Previous audit:** <date, score> | **Prepared by:** <name>

---

## Headline

**Health score: <n>/100 — <band>**

<Two sentences. What the score means in operational terms, and the one thing that would move
it most. Not a summary of the tables below.>

| Metric | This audit | Previous | Target |
|--------|-----------|----------|--------|
| Health score | | | 80+ |
| Freshness rate | | | 80% |
| Ownership coverage | | | 90% |
| Critical-tier compliance | | | 100% |
| Live page count | | | flat or falling |

## Inventory

| Tier | Pages | Within SLA | Stale | Unowned |
|------|-------|-----------|-------|---------|
| Critical | | | | |
| Core | | | | |
| Reference | | | | |
| Archive | | n/a | n/a | n/a |

## Critical-tier exceptions

Every stale or unowned Critical-tier page, listed individually. These are risk items,
not backlog items.

| Page | Owner | Age | Issue | Remediation owner | Due |
|------|-------|-----|-------|-------------------|-----|
| | | | | | |

## Structural findings

**Connectivity:** <n>% of pages have at least one inbound link.

| Finding | Count | Notes |
|---------|-------|-------|
| Orphans — high traffic (findability bug) | | Link from a hub urgently |
| Orphans — zero traffic (dead weight) | | Delete |
| Dead links | | Fix first; cheapest and most visible |
| Duplicate titles | | Merge into the most-linked path |
| Hub pages | | Confirm each has a named owner |

### Duplicate clusters

| Title | Paths | Merge target (most inbound links) | Owner |
|-------|-------|-----------------------------------|-------|
| | | | |

## Remediation plan

Generated by `doc_debt_ranker.py`. Take the top 10 into one sprint; the rest of the
backlog is a measurement instrument, not a plan.

| # | Action | Page | Bucket | Effort | Owner |
|---|--------|------|--------|--------|-------|
| 1 | | | | | |

**Sprint effort:** <n> hours | **Total backlog:** <n> hours | **Dropped as low-value:** <n> hours

## Deletions proposed

<List. State explicitly whether deletion authority exists. If it does not, say so here —
it roughly doubles the remediation effort and the plan above assumes an answer.>

## Decisions needed

- [ ] <Decision> — owner: <name>, needed by: <date>

## Next audit

**Date:** <date, one quarter out> | **Same `--as-of` convention:** yes
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: 472kUpdated Claude CodeCodexVerifiedInstall
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: 472kUpdated Claude CodeCodexVerifiedInstall
rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first.Stars: 194kUpdated Claude CodeCodexVerifiedInstall