Knowledge Base Strategic Audit

Use it for

Kasimir’s Obsidian Knowledge Graph Demo

The prompt

You are analyzing this knowledge base from the inside. Read the folder structure, frontmatter, tags, and wikilinks across all Markdown files. Do not search for specific topics — instead, produce a strategic audit with the following sections:

1. **Taxonomy Coverage** — What are the primary categories/pillars/tags in use? How many notes fall under each? Which are overrepresented and which are thin?

2. **Content Distribution** — Break down the notes by type (raw sources, synthesis, insights, session extracts, commands/skills, etc.). What proportion is raw vs. processed? Are there large pools of unprocessed material?

3. **Relationship Strength** — Which notes have the most inbound links? Which have zero? Flag orphan notes (no inbound or outbound links) and hub notes (>10 inbound). Are the hubs actually load-bearing or are they artificial concentrators?

4. **Quality Score Distribution** (if quality scores are present in frontmatter) — What is the score distribution? Are there clusters of high-quality material that haven't been cross-referenced or surfaced?

5. **Connection Gaps** — Identify 3–5 pairs or clusters of notes that are thematically related but not linked. These are missing edges in your knowledge graph.

6. **Top Inference Entry Points** — Which 5 notes would be the best starting points for inference sessions? These are notes that are well-linked, well-scored, and sit at the intersection of multiple themes.

7. **Recommended Next Actions** — Based on the above, what are the 3 highest-leverage maintenance actions? (e.g., "Develop pillar 3 — only 4 notes vs. 47 in pillar 1", "Link the procurement framework cluster to the client retention cluster — 6 notes in each with no cross-links")

Be specific and use actual note titles, tag names, and counts from what you find. This is an operational audit, not a summary.

Worked example

No worked example recorded yet.