wiki-lint
Original:🇺🇸 English
Translated
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".
9installs
Sourcear9av/obsidian-wiki
Added on
NPX Install
npx skill4agent add ar9av/obsidian-wiki wiki-lintTags
Translated version includes tags in frontmatterSKILL.md Content
View Translation Comparison →Wiki Lint — Health Audit
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 . 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.
llm-wiki/SKILL.mdBefore You Start
- Read to get
.envOBSIDIAN_VAULT_PATH - Read for the full page inventory
index.md - Read for recent activity context
log.md
Lint Checks
Run these checks in order. Report findings as you go.
1. Orphaned Pages
Find pages with zero incoming wikilinks. These are knowledge islands that nothing connects to.
How to check:
- Glob all files in the vault
.md - For each page, Grep the rest of the vault for references
[[page-name]] - Pages with zero incoming links (except and
index.md) are orphanslog.md
How to fix:
- Identify which existing pages should link to the orphan
- Add wikilinks in appropriate sections
2. Broken Wikilinks
Find that point to pages that don't exist.
[[wikilinks]]How to check:
- Grep for across all pages
\[\[.*?\]\] - Extract the link targets
- Check if a corresponding file exists
.md
How to fix:
- If the target was renamed, update the link
- If the target should exist, create it
- If the link is wrong, remove or correct it
3. Missing Frontmatter
Every page should have: title, category, tags, sources, created, updated.
How to check:
- Grep frontmatter blocks (scope to at file heads) instead of reading every page in full
^--- - Flag pages missing required fields
How to fix:
- Add missing fields with reasonable defaults
3a. Missing Summary (soft warning)
Every page should have a frontmatter field — 1–2 sentences, ≤200 chars. This is what cheap retrieval (e.g. 's index-only mode) reads to avoid opening page bodies.
summary:wiki-queryHow to check:
- Grep frontmatter for across the vault
^summary: - Flag pages without it, but as a soft warning, not an error — older pages predating this field are fine; the check exists to nudge ingest skills into filling it on new writes.
- Also flag pages whose summary exceeds 200 chars.
How to fix:
- Re-ingest the page, or manually write a short summary (1–2 sentences of the page's content).
4. Stale Content
Pages whose timestamp is old relative to their sources.
updatedHow to check:
- Compare page timestamps to source file modification times
updated - Flag pages where sources have been modified after the page was last updated
5. Contradictions
Claims that conflict across pages.
How to check:
- This requires reading related pages and comparing claims
- Focus on pages that share tags or are heavily cross-referenced
- Look for phrases like "however", "in contrast", "despite" that may signal existing acknowledged contradictions vs. unacknowledged ones
How to fix:
- Add an "Open Questions" section noting the contradiction
- Reference both sources and their claims
6. Index Consistency
Verify matches the actual page inventory.
index.mdHow to check:
- Compare pages listed in to actual files on disk
index.md - Check that summaries in still match page content
index.md
7. Provenance Drift
Check whether pages are being honest about how much of their content is inferred vs extracted. See the Provenance Markers section in for the convention.
llm-wikiHow to check:
- For each page with a block or any
provenance:/^[inferred]markers, count sentences/bullets and how many end with each marker^[ambiguous] - Compute rough fractions (,
extracted,inferred)ambiguous - Apply these thresholds:
- AMBIGUOUS > 15%: flag as "speculation-heavy" — even 1-in-7 claims being genuinely uncertain is a signal the page needs tighter sourcing or should be moved to
synthesis/ - INFERRED > 40% with no in frontmatter: flag as "unsourced synthesis" — the page is making connections but has nothing to cite
sources: - Hub pages (top 10 by incoming wikilink count) with INFERRED > 20%: flag as "high-traffic page with questionable provenance" — errors on hub pages propagate to every page that links to them
- Drift: if the page has a frontmatter block, flag it when any field is more than 0.20 off from the recomputed value
provenance:
- AMBIGUOUS > 15%: flag as "speculation-heavy" — even 1-in-7 claims being genuinely uncertain is a signal the page needs tighter sourcing or should be moved to
- Skip pages with no frontmatter and no markers — treated as fully extracted by convention
provenance:
How to fix:
- For ambiguous-heavy: re-ingest from sources, resolve the uncertain claims, or split speculative content into a page
synthesis/ - For unsourced synthesis: add to frontmatter or clearly label the page as synthesis
sources: - For hub pages with INFERRED > 20%: prioritize for re-ingestion — errors here have the widest blast radius
- For drift: update the frontmatter to match the recomputed values
provenance:
8. Fragmented Tag Clusters
Checks 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:
- For each tag that appears on ≥ 5 pages:
- = count of pages with this tag
n - = count of wikilinks between any two pages in this tag group (check both directions)
actual_links cohesion = actual_links / (n × (n−1) / 2)
- Flag any tag group where cohesion < 0.15 and n ≥ 5
How to fix:
- Run the skill targeted at the fragmented tag — it will surface and insert the missing links
cross-linker - If a tag group is large (n > 15) and still fragmented, consider splitting it into more specific sub-tags
Output Format
Report findings as a structured list:
markdown
## 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 ⚠️After Linting
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=FOffer to fix issues automatically or let the user decide which to address.