vault-index
Skill0 starsChanged 3 months agoMITView on GitHub
Rebuild the vault-index note from current vault state. Use when /vault-index is invoked, when the morning skill flags "vault-index not found" or a stale delta, when the user asks "what's in my vault" / "give me a vault overview" / "how's my vault organized", or after a large batch of new Concepts has landed. Do NOT use for searching specific notes — use the obsidian skill instead.
2 other projects use a version of this.
Adopted by
Most recently taken up by
- letsloose501/sqs-agent-memorytheir own version, first seen Nov 3, 2026
- Lucioway/way-stacktheir own version, first seen Aug 31, 2026
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 2
- letsloose501/sqs-agent-memory★ 2same 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-lintSkill
- vault-retrieveSkill
- weekly-learningsSkill
- weekly-signalsSkill
The file
We split this skill into the rules it gives an agent
10 rules. About 0 are common, 10 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈10
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 16
Read the current vault-index if it exists, to capture the prior state for the "Recent changes" section:
- Distinctive: line 20
If it doesn't exist, note that this is a fresh build.
- Distinctive: line 31
All Concept page names (as wikilinks)
- Distinctive: line 32
All Clipping note names (newest first based on filename date prefix, if any)
- Distinctive: line 33
All Context file names
- Distinctive: line 34
All Project note names
- Distinctive: line 38
Write the rebuilt vault-index by overwriting the file directly:
- Distinctive: line 45
Use the exact format specified below.
- Distinctive: line 57
Write the note with this exact structure.
- Distinctive: line 102
Do not include Daily Notes in the index — those are temporal logs, not knowledge graph nodes, and adding them would make the morning delta …
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Skill: /vault-index
Rebuild vault-index.md from current vault state so the morning skill's overnight delta is accurate — stale or absent index degrades morning briefings.
Don't: include Daily Notes in the index — they're temporal logs, not knowledge graph nodes. Don't run this for targeted note lookup — use the obsidian skill instead.
Steps
- Determine today's date and time (YYYY-MM-DD HH:MM)
- Read the current vault-index if it exists, to capture the prior state for the "Recent changes" section:
If it doesn't exist, note that this is a fresh build.obsidian read file='vault-index' - Scan the vault for current state:
obsidian search query='Concepts/' limit=200 obsidian search query='Clippings/' limit=200 obsidian search query='Context/' limit=50 obsidian search query='Projects/' limit=50 - From the scan results, compile:
- All Concept page names (as wikilinks)
- All Clipping note names (newest first based on filename date prefix, if any)
- All Context file names
- All Project note names
- Diff against the prior vault-index (from step 2) to identify what's new or missing. If no prior index exists, mark all entries as "Initial build."
- Write the rebuilt vault-index by overwriting the file directly:
Use the exact format specified below.VAULT="$HOME/Library/Mobile Documents/iCloud~md~obsidian/Documents/Personal" cat > "$VAULT/vault-index.md" << 'VAULTEOF' [insert rendered content here] VAULTEOF - Commit the change:
VAULT="$HOME/Library/Mobile Documents/iCloud~md~obsidian/Documents/Personal" git -C "$VAULT" add '<the note paths you wrote>' && git -C "$VAULT" commit -m "docs: rebuild vault-index [YYYY-MM-DD]" - Report what changed: counts per section, and anything flagged in the diff.
vault-index.md format
Write the note with this exact structure. The morning skill parses the section headers to detect drift — keep them verbatim.
# Vault Index
*Last updated: YYYY-MM-DD HH:MM*
## Concepts (N)
[[Concept page 1]]
[[Concept page 2]]
...
## Clippings (N)
[[Clipping note 1]]
[[Clipping note 2]]
...
## Context (N)
[[Context/accountability]]
[[Context/patterns]]
...
## Projects (N)
[[Projects/Project Name]]
...
## Recent changes
*Since prior index:*
- Added: [[Note A]], [[Note B]] (or "none")
- Removed: [names] (or "none" — note: removals are best-effort based on what was in the prior index)When the morning skill flags drift
The morning skill reports drift when it finds Concept pages, Clippings, or Context files not listed in the current index. After morning surfaces this, invoke /vault-index to reconcile. The rebuilt index becomes the new baseline.
Notes on scan completeness
obsidian search returns results sorted by recency, limit 200. If any section likely has more than 200 entries, note it in the output and suggest running the rebuild in sections. In practice, Concepts and Clippings are the two sections most likely to grow beyond this.
Do not include Daily Notes in the index — those are temporal logs, not knowledge graph nodes, and adding them would make the morning delta meaningless.
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.

