Audit and maintain the health of the Obsidian wiki. Use this skill when the user wants to check their wiki for issues, find orphaned pages, detect contradictions, identify stale content, fix broken wikilinks, or perform general maintenance on their knowledge base. Also triggers on "clean up the wiki", "what needs fixing", "audit my notes", or "wiki health check".
You are performing a health check on an Obsidian wiki. Your goal is to find and fix structural issues that degrade the wiki's value over time.
Before scanning anything: follow the Retrieval Primitives table in llm-wiki/SKILL.md. Prefer frontmatter-scoped greps and section-anchored reads over full-page reads. On a large vault, blindly reading every page to lint it is exactly what this framework is built to avoid.
.env to get OBSIDIAN_VAULT_PATHindex.md for the full page inventorylog.md for recent activity contextRun these checks in order. Report findings as you go.
Find pages with zero incoming wikilinks. These are knowledge islands that nothing connects to.
.md files in the vault[[page-name]] referencesindex.md and log.md) are orphansHow to fix:
Find [[wikilinks]] that point to pages that don't exist.
How to check:
\[\[.*?\]\] across all pages.md file existsHow to fix:
Every page should have: title, category, tags, sources, created, updated.
How to check:
^--- at file heads) instead of reading every page in fullHow to fix:
Every page should have a summary: frontmatter field — 1–2 sentences, ≤200 chars. This is what cheap retrieval (e.g. wiki-query's index-only mode) reads to avoid opening page bodies.
How to check:
^summary: across the vaultHow to fix:
Pages whose updated timestamp is old relative to their sources.
How to check:
updated timestamps to source file modification timesClaims that conflict across pages.
How to check:
How to fix:
Verify index.md matches the actual page inventory.
How to check:
index.md to actual files on diskindex.md still match page contentCheck whether pages are being honest about how much of their content is inferred vs extracted. See the Provenance Markers section in llm-wiki for the convention.
How to check:
provenance: block or any ^[inferred]/^[ambiguous] markers, count sentences/bullets and how many end with each markerextracted, inferred, ambiguous)synthesis/sources: in frontmatter: flag as "unsourced synthesis" — the page is making connections but has nothing to citeprovenance: frontmatter block, flag it when any field is more than 0.20 off from the recomputed valueprovenance: frontmatter and no markers — treated as fully extracted by conventionHow to fix:
synthesis/ pagesources: to frontmatter or clearly label the page as synthesisprovenance: frontmatter to match the recomputed valuesChecks whether pages that share a tag are actually linked to each other. Tags imply a topic cluster; if those pages don't reference each other, the cluster is fragmented — knowledge islands that should be woven together.
How to check:
n = count of pages with this tagactual_links = count of wikilinks between any two pages in this tag group (check both directions)cohesion = actual_links / (n × (n−1) / 2)How to fix:
cross-linker skill targeted at the fragmented tag — it will surface and insert the missing linksChecks that visibility/ tags are applied correctly and aren't silently missing where they matter.
How to check:
password, api_key, secret, token, ssn, email:, phone: followed by an actual value (not a field description). If a page matches and lacks visibility/pii or visibility/internal, flag it as a likely mis-classification.visibility/pii without sources:: A page tagged visibility/pii should always have a sources: frontmatter field — if there's no provenance, there's no way to verify the classification. Flag any visibility/pii page missing sources:.visibility/ tags are system tags and must not appear in _meta/taxonomy.md. If found there, flag as misconfigured — they'd be counted toward the 5-tag limit on pages that include them.How to fix:
visibility/pii (or visibility/internal if it's team-context rather than personal data) to the page's frontmatter tagssources:: add provenance or escalate to the user — don't auto-fillvisibility/ entries from _meta/taxonomy.mdReport findings as a structured list:
## Wiki Health Report
### Orphaned Pages (N found)
- `concepts/foo.md` — no incoming links
### Broken Wikilinks (N found)
- `entities/bar.md:15` — links to [[nonexistent-page]]
### Missing Frontmatter (N found)
- `skills/baz.md` — missing: tags, sources
### Stale Content (N found)
- `references/paper-x.md` — source modified 2024-03-10, page last updated 2024-01-05
### Contradictions (N found)
- `concepts/scaling.md` claims "X" but `synthesis/efficiency.md` claims "not X"
### Index Issues (N found)
- `concepts/new-page.md` exists on disk but not in index.md
### Missing Summary (N found — soft)
- `concepts/foo.md` — no `summary:` field
- `entities/bar.md` — summary exceeds 200 chars
### Provenance Issues (N found)
- `concepts/scaling.md` — AMBIGUOUS > 15%: 22% of claims are ambiguous (re-source or move to synthesis/)
- `entities/some-tool.md` — drift: frontmatter says inferred=0.10, recomputed=0.45
- `concepts/transformers.md` — hub page (31 incoming links) with INFERRED=28%: errors here propagate widely
- `synthesis/speculation.md` — unsourced synthesis: no `sources:` field, 55% inferred
### Fragmented Tag Clusters (N found)
- **#systems** — 7 pages, cohesion=0.06 ⚠️ — run cross-linker on this tag
- **#databases** — 5 pages, cohesion=0.10 ⚠️
### Visibility Issues (N found)
- `entities/user-records.md` — contains `email:` value pattern but no `visibility/pii` tag
- `concepts/auth-flow.md` — tagged `visibility/pii` but missing `sources:` frontmatter
- `_meta/taxonomy.md` — contains `visibility/internal` entry (system tag must not be in taxonomy)
Append to log.md:
- [TIMESTAMP] LINT issues_found=N orphans=X broken_links=Y stale=Z contradictions=W prov_issues=P missing_summary=S fragmented_clusters=F visibility_issues=V
Offer to fix issues automatically or let the user decide which to address.