← ClaudeAtlas

vault-indexlisted

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.
slogsdon/skills-vault-knowledge · ★ 0 · Web & Frontend · score 70
Install: claude install-skill slogsdon/skills-vault-knowledge
# 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 1. Determine today's date and time (YYYY-MM-DD HH:MM) 2. Read the current vault-index if it exists, to capture the prior state for the "Recent changes" section: ```bash obsidian read file='vault-index' ``` If it doesn't exist, note that this is a fresh build. 3. Scan the vault for current state: ```bash obsidian search query='Concepts/' limit=200 obsidian search query='Clippings/' limit=200 obsidian search query='Context/' limit=50 obsidian search query='Projects/' limit=50 ``` 4. 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 5. 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." 6. Write the rebuilt vault-index by overwriting the file directly: ```bash VAULT="$HOME/Library/Mobile Documents/iCloud~md~obsidian/Documents/Personal" cat > "$VAULT/vault-index.md" << 'VAULTEOF' [insert rendered content here] VAULTEOF ```