← ClaudeAtlas

obsidian-querylisted

Specialist skill for answering questions FROM the Obsidian vault — "how does X work", "why did we choose Y", "what do we know about Z", "find the docs about…". It owns the hidden per-project index (a catalog of every note with one-line summaries, in <vault>/.claude-docs/) and run log, reads the index first to locate relevant notes, then synthesizes a cited answer. Valuable answers can be filed back into the vault. Use whenever the user asks a question whose answer should live in the documentation, or asks to find/locate notes.
rubber-ducks-syndicate/obsidian-documentation-skill · ★ 0 · AI & Automation · score 72
Install: claude install-skill rubber-ducks-syndicate/obsidian-documentation-skill
# Query Specialist (index-based retrieval) You turn the vault from write-only documentation into a queryable knowledge base. The pattern (after Karpathy's "LLM Wiki"): keep a compiled **index** of everything, read the index first, drill into only the relevant notes, answer with citations — no embeddings or RAG infrastructure needed at vault scale. Read `../obsidian-documentation/references/conventions.md` first (project scope, vault location resolution). ## The two files you own Both live in a **hidden dot-folder** — `<vault>/.claude-docs/<Project>/` — so Obsidian never shows them and the vault stays clean for humans. They are machine files: write plain relative paths (from the project folder), not wiki links, since Obsidian doesn't index dot-folders anyway. **`<vault>/.claude-docs/<Project>/index.md`** — content catalog, auto-generated (humans browse MOCs; you read this). One line per note: ```markdown --- project: "Atlas" updated: <date> --- # Index — Atlas > Auto-generated by obsidian-query. Do not edit by hand; ask for a rebuild instead. ## Project level - Architecture/System Overview.md — how the repos fit together · #architecture · upd 2026-06-01 - ADRs/… ## Web App (acme/atlas-web) - Web App/Features/Refunds/Refunds.md — customer-initiated refunds via Stripe; manual review > $500 · #feature #backend/api · upd 2026-06-10 - … ## API (acme/atlas-api) - … ``` Group entries by level: project-wide sections first, then one section per repository. One line = relat