wiki-lint
Skill1 starsChanged 23 days agoMITView on GitHub
Health-check the project wiki (personal `.wiki/` or team `docs/wiki/`) and report broken links, orphan pages, stale or unsourced claims, contradictions, duplicates, gaps and leaked secrets. Read-only; fixes only what the user approves. Use when the user asks to lint, audit, check or clean up the wiki, or periodically after several syncs.
42 other projects use a version of this.
Adopted by
Most recently taken up by
- Ar9av/obsidian-wikitheir own version, first seen Nov 8, 2026
- ggoosen/Digital-Workforcetheir own version, first seen Nov 8, 2026
- barakgut/llm-wikitheir own version, first seen Nov 1, 2026
- chobizzy/llm-wikitheir own version, first seen Nov 1, 2026
- wareagledusty/wiki-federation-starter-kittheir own version, first seen Nov 1, 2026
- leiverkus/research-superpowerstheir own version, first seen Nov 1, 2026
Used with
Projects with it also use wiki-capture, wiki-status and 8 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
jehrhardtSkillwiki-capture
Quickly capture raw thoughts, links, images, or notes to today's Obsidian daily note from anywhere in Pi. Use when the user wants to jot something down for later wiki processing.
Also in 6 projects that use this
nexuschainsSkillwiki-status
Reports the current state of the wiki vault — page counts, category breakdown, hub pages, orphans, stale entries, and a delta showing what has changed since the last ingest. Use this skill when the operator asks "what's the status", "wiki dashboard", "how many pages", "what's stale", "what's been ingested", "show me the delta", or "wiki health overview". Also surfaces structural insights (top hubs, fragmented clusters, bridge pages) when the operator asks "wiki insights", "what's central", or "show me the hubs". Read-only: this skill reports and recommends; it does not modify any files.
Also in 5 projects that use this
- nexuschainsSkill
cross-linker
Scans the wiki vault and adds missing [[wikilinks]] between pages that are related but not yet connected. Use this skill when the operator says "link my pages", "find missing links", "cross-reference the wiki", "connect my wiki", "add wikilinks", or after any large ingest to weave new pages into the existing knowledge graph. Also trigger when orphaned pages need connecting or when wiki-lint reports fragmented tag clusters. This is a write-heavy skill — it modifies page files to insert links, unlike wiki-lint which only reports.
Also in 4 projects that use this
Ivy-Chen1999Skillwiki-synthesize
Systematically discover synthesis opportunities across the Obsidian wiki — pairs or clusters of concepts that co-occur frequently across pages but have no synthesis page connecting them. Creates new synthesis/ pages that draw explicit cross-cutting conclusions. Use when the user says "synthesize my wiki", "find connections", "what concepts keep coming up together", "/wiki-synthesize", or after a large ingest when the vault has grown significantly.
Also in 4 projects that use this
- Ivy-Chen1999Skill
wiki-setup
Initialize a new Obsidian wiki vault with the correct structure, special files, and configuration. Use this skill when the user wants to set up a new wiki from scratch, initialize the vault structure, create the .env file, or says things like "set up my wiki", "initialize obsidian", "create a new vault", "get started with the wiki". Also use when the user needs to reconfigure their existing vault or fix a broken setup.
Also in 5 projects that use this
- +1 more from nexuschains
- +4 more from Ivy-Chen1999
Other versions42 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 42
- AgriciDaniel/claude-obsidian★ 16ksame name
- Ar9av/obsidian-wiki★ 3.7ksame name
- kfchou/wiki-skills★ 189same name
- IssacW228/student-llm-wiki★ 173same name
- vanillaflava/llm-wiki-skills★ 65same name
- cookyman74/llmwiki-harness★ 34same name
- Ivy-Chen1999/llm-wiki-kit★ 21same name
- schub-tech/llm-ideation-wiki★ 11same name
- CarbeneAI/Forge★ 9same name
- CodePhobiia/claude-roblox-game-studio★ 9same name
32 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository3 other files it gives its agents.
- wiki-initSkill
- wiki-syncSkill
- wiki-updateSkill
The file
We split this skill into the rules it gives an agent
3 rules. 0 are common, 1 is distinctive, and 2 are very specific to this project.
0
Common
Most of the 33 edited versions we read keep these.
1
Distinctive
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 16
Read the schema, index.md, and (personal mode) the last entries of .wiki/log.md.
- Very specific: line 21
Team mode: run node tools/wiki/wiki.mjs check (full mode).
- Distinctive: line 26
Personal mode: check by hand:
“Common” is measured: kept by at least 6 in 10 of the 33 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
wiki-lint
Audit the wiki against its own SCHEMA.md. Read-only by default: produce a report, then fix
only the items the user approves. Keep the report short and ordered by severity.
1. Load
Find the wiki: docs/wiki/SCHEMA.md (team mode) or .wiki/SCHEMA.md (personal mode). If both
exist, ask which one; if neither, suggest wiki-init.
Read the schema, index.md, and (personal mode) the last entries of .wiki/log.md. List every
page. .wiki/ is git-excluded, so search it with rg --no-ignore.
2. Mechanical checks (exact, no judgement)
Team mode: run node tools/wiki/wiki.mjs check (full mode). It covers frontmatter, broken
links, missing source files, symbols that no longer exist, possible duplicates, orphans, a stale
index.md and secrets. Use its output; do not redo these by hand. Also check
node tools/wiki/wiki.mjs build-index --check.
Personal mode: check by hand:
- Broken links: relative markdown links whose target file does not exist.
- Orphans: pages not linked from
index.md, and pages with no inbound link at all. - Index drift: index entries pointing at missing files, pages missing from the index.
- Frontmatter: missing or invalid
title,type,status,updated,sources; atypenot defined in the schema. - Secrets: token, key, password or private-URL patterns in wiki and raw files. Report the location only, never echo the value.
- Uncommitted wiki changes:
git -C .wiki status --short.
Both modes: compare .sync-state with the project HEAD (team mode: the default branch) and
report how many commits behind the wiki is.
3. Staleness (use git)
For each page and each path in sources:
- Path no longer exists: page is stale (renamed or deleted).
git log -1 --format=%cs -- <path>is newer than the page'supdateddate: page may be stale. Say which source changed.
Count (unverified) markers per page.
4. Judgement checks (read the pages)
- Contradictions between pages (same fact, different value).
- Duplicates the script cannot see: two pages about the same thing under unrelated names.
- Concepts without a page: names that recur in 3+ pages with no page of their own.
- Overloaded pages: a page that fails the "and" test and should be split.
- Thin pages: pages that restate file names without explaining the system.
- Gaps: up to three important areas of the project that no page covers.
- Convention drift: pages that ignore the schema (language, citation format, team mode: one sentence per line, deterministic paths).
5. Report
Group as Errors (broken links, secrets, invalid frontmatter), Stale (with the changed source), Quality (contradictions, duplicates, gaps, overloaded, thin), Housekeeping (index, sync lag, uncommitted). Each item: page path and a one-line fix. Lead with a one-line verdict and counts.
Personal mode: append ## [YYYY-MM-DD] lint | <counts> to .wiki/log.md and commit it in the
wiki repo (the only write allowed without approval). Team mode: write nothing.
Then ask which fixes to apply. When many pages are stale, suggest wiki-sync instead of
patching by hand. Team mode: fixes go on a branch and through a PR, never straight to the
default branch.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.