audit-knowledge-base

Audits CLAUDE.md, skills, and memory files for bloat, stale references, and index drift.

Updated May 13, 2026
One-click install
npx skills add https://github.com/lovebirdsx/universe-editor --skill audit-knowledge-base-lovebirdsx
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: audit-knowledge-base
Source: https://github.com/lovebirdsx/universe-editor/tree/main/.claude/skills/audit-knowledge-base
Command: npx skills add https://github.com/lovebirdsx/universe-editor --skill audit-knowledge-base-lovebirdsx

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? AI knowledge bases that only grow become corrupted: CLAUDE.md files balloon past useful size, memory entries turn into implementation narratives, skill indexes fall out of sync with actual directories, and path references silently break after refactors. This Skill turns the quarterly knowledge-base audit into a fixed checklist so decay is caught and repaired on schedule. ## Core Features & Use Cases - Broken Reference & Size Inventory: Runs pnpm knowledge:check plus line-count scans to flag CLAUDE.md files over 400 lines and memory entries over 20 lines. - Memory Triage: Enforces the one-sentence-index convention, merges same-cluster entries, deletes content already absorbed into CLAUDE.md, and greps to verify referenced files and functions still exist. - Skills & CLAUDE.md Governance: Archives skills untouched for 6+ months, fixes descriptions that drifted into summaries, splits oversized CLAUDE.md files into per-directory subdomain docs, and syncs the nested knowledge map. - Use Case: After a large refactor, run the quarterly audit to find three stale memory paths, split a 600-line CLAUDE.md, and archive two dormant skills, finishing with pnpm check fully green. ## Quick Start Ask the AI to run the quarterly knowledge base audit over CLAUDE.md, .claude/skills, and .claude/memory and fix everything it finds.

Frequently Asked Questions about audit-knowledge-base

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I audit a Claude knowledge base for stale references?

Run pnpm knowledge:check to validate path references across memory, vendor, and CLAUDE.md files, then grep any file or function names mentioned in memory entries to confirm they still exist. Fix all findings in the same batch before committing.

When should a CLAUDE.md file be split into smaller documents?

Split when a CLAUDE.md exceeds 400 lines. Cut along chapter boundaries into per-directory subdomain documents, add a back-pointer to the parent at the top, and convert cross-references to explicit relative paths.

What is the size limit for Claude memory entries?

Each memory entry should stay at or under 20 lines excluding frontmatter, containing only a one-sentence status, a non-obvious lesson hook, and a pointer. Implementation narratives readable from git history or CLAUDE.md should be deleted.

How often should the knowledge base audit run?

Run it quarterly or after any large batch of refactoring. Skills untouched for over six months whose subsystem has stabilized are archived to .claude/skills-archive with the README index updated.

Why does the skill index drift out of sync with actual skill directories?

Drift happens when skills are added or archived without updating the README table or running pnpm skills:policy to sync agents/openai.yaml. The audit compares the README table against the actual .claude/skills directory listing to catch gaps.