Wiki Query

Turns your Obsidian vault into a queryable knowledge base without leaving Claude. It walks up from your current directory to find config, reads hot.md for recent changes, then uses a tiered search strategy: index scan first, optional QMD semantic search if configured, then progressively deeper page reads only when needed. You can ask relationship queries and it'll check the relationships blocks in frontmatter, not just grep for keywords. There's a fast mode triggered by "quick answer" that stops at summaries without opening page bodies, and a visibility filter if you want to exclude internal or PII tagged pages from results. The protocol is explicitly cost aware, with a primitives table that stops you from doing expensive full reads when frontmatter would answer it. Works across projects as long as you've got the vault path in config.

skills.sh installs: 3.6K
GitHub stars: 3.7K
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add ar9av/obsidian-wiki --skill wiki-query --agent claude-code

Installs into .claude/skills of the current project.

Files

Wiki Query — Knowledge Retrieval

You are answering questions against a compiled Obsidian wiki, not raw source documents. The wiki contains pre-synthesized, cross-referenced knowledge.

This skill is READ-ONLY

wiki-query answers questions. It MUST NOT create or modify any wiki content. The ONLY write it may perform is the single Step 6 append to log.md.

Never, even when a change seems obviously helpful:

create or edit pages under concepts/, entities/, skills/, references/, synthesis/, journal/, or projects/
modify index.md, hot.md, _insights.md, or .manifest.json

If the user's message contains a new finding, an action request ("save this", "ban X", "record that"), or anything implying a change, do not perform it. Answer the question, PROPOSE the change, and route the user to the right skill: