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 from any project. Includes an index-only fast mode triggered by "quick answer", "just scan", "don't read the pages", "fast lookup" — returns answers from page summaries and frontmatter without reading page bodies. Accepts inline named-vault routing like "wiki-query @work what do I know about X" via the shared Config Resolution Protocol.

Quality

92%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

High

Do not use without reviewing

Quality

Content

88%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is a dense, highly actionable retrieval pipeline with explicit sequencing, guarded fallbacks, and concrete commands throughout. Its weaker dimensions are conciseness (some trim opportunities in the QMD section) and progressive disclosure (reference material inlined rather than split into bundle files).

Suggestions

Move the QMD CLI command catalog (Step 2b) and the graph-query output-field dictionary (Step 0) into a reference bundle file, leaving a one-line pointer so the SKILL.md body stays an overview.

Trim redundant routing statements — the 'do not edit, route to wiki-capture/wiki-update' guidance appears in both the READ-ONLY section and Step 5; consolidate to one.

Cut the bookkeeping-files exclusion rationale or compress it to one line, since it restates behavior the decision tree already implies.

Dimension	Reasoning	Score
Conciseness	Nearly all of the ~290 lines are skill-specific procedural instruction that assumes Claude's competence — there is no padding explaining what a wiki or grep is — but the QMD CLI command catalog and a few redundant routing/escalation notes could be trimmed.	4 / 5
Actionability	Provides copy-paste-ready bash commands (obsidian-wiki graph-query, graph-analyse), exact MCP tool fields, concrete grep patterns, BFS bounds, and an exact log-format string, covering the common query shapes (structural, path, relationship, index-only).	5 / 5
Workflow Clarity	A clearly sequenced Step 0–6 pipeline with an explicit decision tree, guard checkpoints (QMD unset, index-only stop, frontier cap), and escalation reporting that acts as feedback for the read-only retrieval flow.	5 / 5
Progressive Disclosure	Well-organized with labeled steps, decision trees, and tables, and external references are signaled by named skill/path, but reference material such as the QMD command catalog and graph-query field dictionary is inlined in one ~290-line file with no bundle files to offload it to.	4 / 5
	Total	18 / 20 Passed

Description

96%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is rich, third-person, and trigger-heavy, covering what the skill does and exactly when to invoke it with concrete natural-language phrasings. Its only soft spot is minor overlap risk with sibling wiki skills, which it mitigates via explicit routing.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — searching the compiled wiki, finding information, synthesized answers with citations, exploring topic connections, walking typed edges across multiple hops, an index-only fast mode, and inline named-vault routing — giving comprehensive coverage rather than vague language.	5 / 5
Completeness	Explicitly answers both what (answers questions by searching the compiled Obsidian wiki, multi-hop graph walks, index-only fast mode, inline vault routing) and when, with concrete "Use this skill when…" / "Also use when…" trigger clauses.	5 / 5
Trigger Term Quality	Packs in natural phrasings users would actually say — "what do I know about X", "find everything related to Y", "how is X connected to Y", "trace the chain from X to Z", "what does X depend on transitively", plus fast-mode triggers ("quick answer", "just scan", "don't read the pages") and "@work" routing.	5 / 5
Distinctiveness Conflict Risk	Has a clear read-only query niche and explicitly routes edit requests to sibling skills (wiki-capture, wiki-update), but those closely related wiki skills create minor overlap risk, so it sits just below the fully-distinct anchor.	4 / 5
	Total	19 / 20 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: Ar9av/obsidian-wiki
Path: .skills/wiki-query/SKILL.md
Commit: 52c9f2b

Reviewed: about 23 hours ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.