vault-lint
Skill0 starsChanged 3 months agoMITView on GitHub
Use when /vault-lint is invoked or when Shane wants a weekly vault health check. Scans Concepts/ and the broader vault for contradictions, orphan pages, missing Concept pages, and stale claims.
5 other projects use a version of this.
Adopted by
Most recently taken up by
- jamejialicona-cmyk/vault-startertheir own version, first seen Sep 22, 2026
- Lucioway/way-stacktheir own version, first seen Aug 31, 2026
- tograf/sidebraintheir own version, first seen Jun 21, 2026
- hootbu/llm-wiki-mindtheir own version, first seen May 1, 2026
- Howie126313/obsidian-vault-kittheir own version, first seen Apr 13, 2026
Other versions5 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 5
- Howie126313/obsidian-vault-kit★ 3same name
- jamejialicona-cmyk/vault-starter★ 2same name
- hootbu/llm-wiki-mind★ 1same name
- tograf/sidebrain★ 1same name
- Lucioway/way-stack★ 0same name
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 repository17 other files it gives its agents.
- backlinksSkill
- challengeSkill
- connectSkill
- expandSkill
- fix-nested-code-fencesSkill
- ghostSkill
- ingestSkill
- learnedSkill
- mapSkill
- meetingSkill
- obsidianSkill
- source-mineSkill
- traceSkill
- vault-indexSkill
- vault-retrieveSkill
- weekly-learningsSkill
- weekly-signalsSkill
The file
We split this skill into the rules it gives an agent
4 rules. 0 are common, 2 are distinctive, and 2 are very specific to this project.
0
Common
Most of the 4 edited versions we read keep these.
2
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 14
Run the four scans below using obsidian CLI commands via bash
- Distinctive: line 17
Do NOT auto-fix anything — surface for Shane to decide
- Very specific: line 41
Read each page that contains wiki-links and collect every [[linked page]] reference.
- Distinctive: line 56
Run searches for noun phrases that appear frequently across the vault.
“Common” is measured: kept by at least 6 in 10 of the 4 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
Skill: /vault-lint
Weekly vault health scan — contradictions, orphans, missing Concept pages, and stale claims — output is a prioritized action list, not a report.
Don't: auto-fix anything — surface for Shane to decide. Don't use this for targeted note exploration — that's the obsidian skill.
Steps
- Run the four scans below using
obsidianCLI commands via bash - Collate results into a prioritized action list
- Present findings grouped by category with specific file names and fix instructions
- Do NOT auto-fix anything — surface for Shane to decide
Scan 1 — Contradictions between Concept pages
obsidian search query='Concepts/' limit=50For each Concept page found, read it. Compare claims across pages. Flag pairs where one page asserts X and another asserts not-X (or a materially different position on the same topic).
Output format:
CONTRADICTION: Concepts/[A] vs Concepts/[B]
[A] says: "[quote]"
[B] says: "[quote]"
→ Resolve by: updating whichever is older or merging into a single pageScan 2 — Orphan pages (no inbound links)
obsidian search query='[[' limit=100Read each page that contains wiki-links and collect every [[linked page]] reference. Any Concept page that appears in zero link lists is an orphan.
Output format:
ORPHAN: Concepts/[page]
Created: [date if available]
→ Link from a related note or delete if supersededScan 3 — Concepts mentioned 3+ times without a dedicated page
obsidian search query='TERM' limit=20Run searches for noun phrases that appear frequently across the vault. Count mentions. Any term appearing 3+ times that does NOT have a matching file in Concepts/ is a gap.
Strategy: search for terms surfaced during recent /connect and /trace runs first; also scan Daily Notes for recurring nouns.
Output format:
MISSING CONCEPT: "[term]" (N mentions, no Concepts/[term] page)
Seen in: [list of note names]
→ Create Concepts/[term] pageScan 4 — Stale claims superseded by newer sources
obsidian search query='Clippings/' limit=30For each Concept page, check if any claim is contradicted or significantly updated by a more recent Clipping. Look for:
- Dates cited in Concept pages that are older than 2 years
- Clippings that explicitly update or retract a prior claim
- Concepts referencing statistics or studies where a newer Clipping cites updated data
Output format:
STALE: Concepts/[page]
Claim: "[quote from concept page]"
Superseded by: Clippings/[newer source] ([date])
→ Update claim or add caveat in Concepts/[page]Fallback (if qwen unavailable)
Execute all four scans directly using obsidian search and obsidian read commands via bash. Apply the same logic described above. The scans are bash-executable without Qwen.
Output structure
Present findings in this order, most actionable first:
- Contradictions (fix these — they corrupt the knowledge base)
- Missing Concepts (create these — reduces future orphan risk)
- Orphans (link or delete)
- Stale claims (update or caveat)
End with a one-line summary: "N issues found across Concepts/ — X contradictions, Y orphans, Z missing pages, W stale claims."
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.

