CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

70

Quality

85%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

73%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.

A well-sequenced, highly actionable read-only retrieval protocol with strong workflow clarity and good external references. Its main weakness is conciseness — the QMD and GraphRAG sections are verbose and could be trimmed or split into reference files.

Suggestions

Tighten the QMD semantic-pass section: collapse the three CLI mode variants (quality/balanced/fast) into a compact table and move the extended caveats (operator-like token handling, _raw/ defensive filter) into a reference file.

Move the GraphRAG output-field reference and the structural-intents routing table into a separate reference doc, leaving SKILL.md a concise overview that links out for the field-by-field detail.

Trim the opening framing ('The wiki contains pre-synthesized, cross-referenced knowledge') and other mildly over-explanatory asides that restate what the wiki is rather than what to do with it.

DimensionReasoningScore

Conciseness

The body assumes Claude's competence (no 'what is a wiki/grep' explanations) and is operationally dense, but the QMD section (three CLI variants plus caveats) and the GraphRAG output-field reference could be tightened, matching the 'mostly efficient but could be tightened' 3 anchor rather than the lean 4.

3 / 5

Actionability

Provides concrete executable commands throughout — 'obsidian-wiki graph-query "$OBSIDIAN_VAULT_PATH" "<question>" --pretty', 'Grep -A 10 -B 2', QMD CLI invocations, and a precise log.md format — with only minor gaps from template placeholders and conditional transport-selection logic, fitting the 4 anchor.

4 / 5

Workflow Clarity

A clearly sequenced numbered pipeline (Step 0 through Step 6) with explicit decision trees, feedback loops (fallback when obsidian-wiki is absent, frontier caps, escalation reporting), and verification via staleness/trust annotations and retrieval accounting — matching the 5 anchor's explicit checkpoints and error-recovery loops; the destructive/batch cap does not apply since the skill is read-only.

5 / 5

Progressive Disclosure

Good section structure with well-signaled references to shared protocols ('follow the Config Resolution Protocol in llm-wiki/SKILL.md', the local $qmd-cli skill, .env.example); no bundle files are provided and some reference-like material (QMD CLI variants, GraphRAG output fields) is inlined, which keeps it just below the 5 anchor.

4 / 5

Total

16

/

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.

A strong, third-person description that clearly states what the skill does and when to use it, with comprehensive natural trigger phrases including synonyms and routing syntax. The only weakness is mild distinctiveness overlap from generic 'what do I know' phrasing.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'searching the compiled Obsidian wiki', 'synthesized answers with citations', 'walking typed edges across multiple hops', 'index-only fast mode', and 'inline named-vault routing' — covering the skill's capabilities comprehensively, matching the 5 anchor.

5 / 5

Completeness

Explicitly answers both 'what' ('Answer questions by searching the compiled Obsidian wiki … synthesized answers with citations') and 'when' ('Use this skill when the user asks a question about their knowledge base …') with concrete trigger phrases, matching the 5 anchor.

5 / 5

Trigger Term Quality

Surfaces many natural phrases a user 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', 'quick answer', 'just scan', 'wiki-query @work' — with synonyms and variations, matching the comprehensive 5 anchor.

5 / 5

Distinctiveness Conflict Risk

Clear niche (compiled Obsidian wiki, typed-edge multi-hop traversal) and explicitly distinguished from sibling skills it routes to (wiki-capture, wiki-update), but the generic phrasing 'what do I know about X' carries minor overlap risk with general research/knowledge skills, so it sits just below the 5 anchor.

4 / 5

Total

19

/

20

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
Ar9av/obsidian-wiki
Reviewed

Table of Contents

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.