wiki-query is the read-only retrieval skill of the obsidian-wiki set. It answers from pre-synthesized pages, starting with a cheap graph query and the index, and only opens page sections or whole pages when it must.
It supports factual, relationship, path, synthesis, gap and challenge questions, annotates stale, disputed and archived citations, and ends every answer with a retrieval report of what it saw, read and dropped.
What You Get
- An answer with wikilink citations and a list of pages consulted
- A gaps line that says what the wiki does not cover
- A retrieval line with candidates seen, read and dropped
- Typed-edge paths between two concepts with hop counts and weak-link flags
- Trust annotations on stale, disputed, verified and archived pages
- A challenge answer that leads with the vault’s own counter-evidence
Common Use Cases
- Asking what your notes say about a topic with cited pages
- Finding how two concepts connect when no page links them directly
- Checking your own past decisions before committing to a new plan
What Makes It Unique
It is built to spend as little reading as possible, using a graph index, frontmatter greps and section reads before full pages, and it reports what it left unread. Structural questions get exact computed answers, event-time frontmatter keeps superseded pages from passing as current, and challenge mode argues against the user using earlier decisions and failures in the vault. Requests to save or change anything are routed to other skills.
Under The Hood
The skill is instructions for the agent. It reads pages and runs the obsidian-wiki command line tool for graph queries, path analysis and one log entry per query, which is its only write. When a QMD collection is configured it queries it through an MCP tool or the qmd command. It does not fetch web pages or call remote APIs, and it tells the agent never to edit pages, the index, the hot file or the manifest, even when a change looks helpful.