← ClaudeAtlas

vault-searchlisted

Use whenever the user wants to recall something from past work, find notes about a topic, or ask 'what did we decide about X', 'find everything about Y', 'summarize what we know about Z', 'что мы решили', 'что мы знаем про'. Prefer this over generic memory tools when an Obsidian vault is available — it synthesizes across multiple notes with source citations.
jojoprison/mnemo · ★ 5 · AI & Automation · score 80
Install: claude install-skill jojoprison/mnemo
# mnemo:ask — Vault Knowledge Search & Synthesis Search across the entire vault, read relevant notes, and synthesize an answer with source citations. ## Prerequisites & config Obsidian must be open. Config at `~/.mnemo/config.json` — reads `vault` and `links_section`. Full schema in `references/config-schema.md`. If missing, ask the user for vault name and save. ## Workflow ### Step 1: Accept Query Input as argument: `/mnemo:ask "what did we decide about pricing strategy?"` If no argument, ask: "What would you like to find in your vault?" ### Step 2: Extract Search Terms Break query into 2-4 key search terms. Example: - "what did we decide about pricing strategy?" → ["pricing", "strategy", "decision"] ### Step 3: Search Vault (parallel) **Run all searches in parallel — single assistant message with multiple Bash tool uses.** For 4 terms this takes ~180ms total instead of ~720ms sequential. ```bash obsidian search query="{term1}" vault="{vault}" obsidian search query="{term2}" vault="{vault}" obsidian search query="{term3}" vault="{vault}" obsidian search query="{term4}" vault="{vault}" ``` Collect all unique matching notes. Deduplicate. ### Step 3b: Also check Claude's memory/ index (not just Obsidian) Obsidian = user-facing knowledge; **`memory/`** (MEMORY.md + topic files) = Claude-facing technical context (gotchas, decisions, sessions) in a separate store. For recall queries ("what did we decide / how did we do X"), also scan the project's memory index — the