vault-health
Skill166 starsChanged 5 months agoMITView on GitHub
Audit the vault for structural issues: unresolved wikilinks, orphan notes, dead-end notes, and Obsidian sync conflicts. Optional --fix flags create stubs or surface fixable issues.
7 other projects use a version of this.
Adopted by
Most recently taken up by
- Atmoskun/claude-skillstheir own version, first seen Nov 16, 2026
- jhs512/ibtheir own version, first seen Oct 15, 2026
- kingluminance/claude-skillstheir own version, first seen Oct 11, 2026
- RoseCompanion/obsidian-vault-health-checktheir own version, first seen Sep 20, 2026
- natscho-hh/ai-secondbrain-stacktheir own version, first seen Jul 5, 2026
- sergeeey/Claude-cod-top-2026their own version, first seen May 13, 2026
Other versions7 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 7
- sergeeey/Claude-cod-top-2026★ 9same name
- az9713/claude-code-obsidian★ 4same name
- natscho-hh/ai-secondbrain-stack★ 2same name
- jhs512/ib★ 1same name
- Atmoskun/claude-skills★ 0same name
- kingluminance/claude-skills★ 0same name
- RoseCompanion/obsidian-vault-health-check★ 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 repository29 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .agents/skills/CLAUDE.mdCLAUDE.md
- CLAUDE.mdCLAUDE.md
- .cursor/rules/qmd-search.mdcCursor rule
- .cursor/rules/skill-conventions.mdcCursor rule
- .cursor/rules/skill-registry.mdcCursor rule
- cache-notesSkill
- commitSkill
- defuddleSkill
- fill-participantsSkill
- followup-todosSkill
- json-canvasSkill
- last-1on1Skill
- mail-transcriptsSkill
- meetingSkill
- migrate-tagsSkill
- note-statusSkill
- obsidian-basesSkill
- obsidian-cliSkill
- obsidian-markdownSkill
- onboard-personSkill
- organize-meetingsSkill
- otter-fetchSkill
- people-stubsSkill
- qmdSkill
- recapSkill
- sprint-retroSkill
- sync-upstream-obsidianosSkill
- workspace-modeSkill
The file
We split this skill into the rules it gives an agent
3 rules. 0 are common, 2 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 3 edited versions we read keep these.
2
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 38
Run only the requested subset.
- Very specific: line 84
When obsidian sync:status reports conflicts:
- Distinctive: line 92
Never auto-restore — sync conflicts mean both sides have edits the user might want.
“Common” is measured: kept by at least 6 in 10 of the 3 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
Vault Health
Usage
/vault-health— Run all checks, present a triage report./vault-health unresolved— Only show unresolved[[wikilinks]]./vault-health orphans— Only show notes with no incoming links./vault-health deadends— Only show notes with no outgoing links./vault-health sync— Only check Obsidian sync conflicts./vault-health --fix-people— For unresolved[[@*]]links, prompt to createTeams/People/@Name.mdstubs in batch (delegates to/people-stubs).
Why this skill exists
The vault grows over time and accumulates structural debt:
- Dead
[[@Jane Doe]]links because the person file was never created. - Notes orphaned in subfolders, never linked from any project/team page.
- Sync conflicts when two devices edit the same file simultaneously.
This skill surfaces all of that in one pass.
Workflow
Step 1: Run all checks (or the subset requested)
| Check | Command | What it returns |
| Unresolved links | obsidian unresolved format=json | All [[link]] pointers with no target file. |
| Orphans | obsidian orphans format=json | Files no other file links to. |
| Deadends | obsidian deadends format=json | Files with no outgoing links. |
| Sync conflicts | obsidian sync:status format=json | Files with unresolved sync versions. |
Run only the requested subset; full sweep when no argument is given.
Step 2: Categorize and present
Group findings by type and severity:
## Unresolved wikilinks (12)
People-flavored ([[@*]]) — likely missing People files:
| # | Link | Referenced in (count) |
|---|------|----------------------|
| 1 | [[@Jane Doe]] | 6 meetings |
| 2 | [[@John Smith]] | 3 meetings |
Other unresolved:
| # | Link | Referenced in |
|---|------|---------------|
| 3 | [[+SomeNewTeam]] | 1 meeting |
## Orphan notes (4)
| # | Path | Created | Reason it might matter |
|---|------|---------|------------------------|
| 1 | Meetings/Engineering/Old Notes.md | 2026-01-12 | Probably needs to link to a project page |
## Deadend notes (8)
...
## Sync conflicts (0)
✓ All synced.For people-flavored unresolved links, sort by count descending — most-referenced unresolved person is most worth creating a file for.
Step 3: Offer fixes
- For
--fix-people(or after presenting): prompt the user to create People stubs in batch. Delegate to/people-stubswhich handles the actual creation. - For orphans/deadends: don't auto-fix. They might be intentional. Just surface.
- For sync conflicts: don't auto-fix. Sync conflicts need human judgment. Surface and tell the user to resolve via Obsidian's UI or
obsidian sync:history.
Step 4: Commit
See /commit. The skill itself doesn't write files (except via /people-stubs if invoked). If anything changed, commit message: chore(vault-health): create N people stubs from unresolved links (or similar).
Sync conflict resolution
When obsidian sync:status reports conflicts:
- List them with
obsidian sync:status format=json(path + version count per file). - For each conflicted file, surface in the report with these next-action hints:
- View versions:
obsidian sync:history file="<path>"— see what each side wrote. - Read a specific version:
obsidian sync:read file="<path>" version=<N>— preview without writing. - Restore:
obsidian sync:restore file="<path>" version=<N>— pick one side. - Manual merge (preferred when both sides have meaningful changes): open the file in Obsidian, use the Sync history pane to pick chunks.
- View versions:
- Never auto-restore — sync conflicts mean both sides have edits the user might want. Surface and let them choose.
Display sync conflicts at the top of the report (not last) — they're time-sensitive (the longer they sit, the more divergent the versions get).
Important Notes
- The skill is read-only by default — only
--fix-peopletriggers writes (and even then, via/people-stubswith confirmation). - Some orphans are intentional (e.g.
USER.md,README.md). Consider an exclusion list in a future iteration. - Sync conflict detection assumes Obsidian Sync is configured. If not, this check is a no-op (prints "✓ Sync not configured — skipped").
- Obsidian CLI requires the desktop app to be running. If it's not, the skill should print a helpful error.
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.

