wiki-query
Answer questions by searching the compiled Obsidian wiki. Use this skill when the user asks a question about their knowledge base, wants to find information across their wiki, asks "what do I know about X", "find everything related to Y", or wants synthesized answers with citations from their wiki pages. Also use when the user wants to explore connections between topics in their wiki, or asks a multi-hop "how is X connected to Y", "what links X to Y", "trace the chain from X to Z", or "what does X depend on transitively" question — answered by walking typed edges across multiple hops. Works fr
npx skills add Ar9av/obsidian-wiki --skill wiki-query --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
What it does
Answer questions by searching the compiled Obsidian wiki. It supports questions about the user’s knowledge base, cross-wiki queries, and multi-hop connections between topics by walking typed edges across multiple hops. It can provide synthesized answers with citations from wiki pages and can operate in an index-only fast mode. It also accepts inline-vault routing like "wiki-query @work what do I know about X" via a Config Resolution Protocol.
How it works
The skill instructs the agent to act on a read-only wiki, using a tiered retrieval pipeline:
- Resolve configuration and load wiki settings.
- Start with a GraphRAG pre-pass to classify the query and identify candidate pages without reading bodies.
- If needed, perform an index pass to build a candidate set from frontmatter (title, tags, aliases, summary) and order by relevance and tier.
- Optionally use QMD if configured to augment results, with guardrails to drop any _raw/ paths.
- In Step 3, fetch relevant sections around query terms from top candidates without full-page reads.
- If still inconclusive, perform full reads of up to three top pages in a prioritized order, with special handling for relationship queries to surface typed edges from frontmatter.
- For path/multi-hop questions, run a dedicated multi-hop graph traversal using typed edges defined in frontmatter, performing a bounded BFS and reporting the chain with edge types.
- Do not modify wiki content; only possible write is a single append to log.md in Step 6.
When to use it
Use this skill for questions like:
- "what do I know about X" or "find everything related to Y"—information is synthesized with citations.
- Exploring connections or planning multi-hop questions like "how is X connected to Y" or "trace the chain from X to Z".
- When you need to walk typed edges across multiple hops to establish relationships.
- A fast index-only mode is available via keywords like "quick answer" or "fast lookup" to rely on summaries and frontmatter without page bodies.
What it can touch
It uses the following tools and inputs as specified in the skill: the graph index and page frontmatter for retrieval; optional QMD sources if configured; and grep-based access to files in the wiki vault. It does not edit content.
Caveats
- The skill is READ-ONLY and must not create or modify wiki content; only appends to log.md are permitted.
- In multi-hop traversal, it relies on frontmatter edges and may not read full page bodies unless necessary.
- If the wiki collection includes misconfigured paths (e.g., _raw/), results may be filtered accordingly and noted in updates.
- Outcomes are limited to what is stated in the wiki frontmatter, summaries, and cited pages; it will not fabricate new facts.
# 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: - quick note / gotcha → `wiki-capture --quick` - a full new page → `wiki-capture` - a project-knowledge sync → `wiki-update` ## Before You Start 1. **Resolve config** — follow the Config Resolution Protocol in `llm-wiki/SKILL.md` (inline `@name` override → walk up CWD for `.env` → `~/.obsidian-wiki/config` → prompt setup). For cross-project queries without `
- This skill is READ-ONLY
- Before You Start
- Visibility Filter (optional)
- Retrieval Protocol
- Step 0: GraphRAG Pre-pass (fast index query — no page reads)
- Step 1: Understand the Question
- Step 2: Index Pass (cheap)
- Step 3: Section Pass (medium cost — only if Steps 2/2b are inconclusive)
- Step 4: Full Read (expensive — last resort)
- Step 4b: Multi-hop Graph Traversal (typed edges)
- Step 5: Synthesize an Answer
- Step 6: Log the Query
- Answer Format
obsidian-wiki graph-query "$OBSIDIAN_VAULT_PATH" "<question>" --pretty
What does the wiki-query skill do?
Answer questions by searching the compiled Obsidian wiki. Use this skill when the user asks a question about their knowledge base, wants to find information across their wiki, asks "what do I know about X", "find everything related to Y", or wants synthesized answers with citations from their wiki pages. Also use when the user wants to explore connections between topics in their wiki, or asks a multi-hop "how is X connected to Y", "what links X to Y", "trace the chain from X to Z", or "what does X depend on transitively" question — answered by walking typed edges across multiple hops. Works fr
How do I install it?
Run `npx skills add Ar9av/obsidian-wiki --skill wiki-query --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From Ar9av/obsidian-wiki, a repository with 3,115 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.
