wiki-query

Answer an explicitly vault-scoped question from an Obsidian wiki without changing it. Use when the user selects the vault as the evidence source: query the wiki, query quick, query deep, explain from the wiki, summarize the vault, find in wiki, search the wiki, or based on the wiki. Do not route ordinary general-knowledge questions here.

Quality

89%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

92%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-crafted skill body: concise, executable, and clearly sequenced with explicit verification gates and a fallback path. The only minor gap is a placeholder product-root path, which is adequately justified, keeping actionability just below perfect.

Dimension	Reasoning	Score
Conciseness	Lean and efficient throughout — no padding explaining what Obsidian, vaults, or retrieval are; every section and code block earns its place and assumes Claude's competence.	5 / 5
Actionability	Provides concrete, mostly copy-paste-ready bash commands with specific flags ('python3 "$RETRIEVE" --vault "$VAULT" "$QUERY" --top 5 --no-rerank --explain'); the only gap is the placeholder PRODUCT_ROOT path, though its resolution is explicitly justified.	4 / 5
Workflow Clarity	Clear sequence (Select depth → Retrieve → Assess evidence → Answer → Checkpoint) with explicit validation: the 'contracts --verify' capability check gates retrieval, path-stays-in-vault verification, and a documented fallback when retrieval is unavailable.	5 / 5
Progressive Disclosure	Well-organized into clear sections with one-level-deep, clearly signaled references ([wiki-retrieve], [wiki-cli], [provenance.md]) and no nested or buried pointers; navigation is straightforward.	5 / 5
	Total	19 / 20 Passed

Description

86%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 description that clearly states what it does, when to use it with concrete trigger phrases, and an explicit routing boundary. It is slightly less comprehensive on distinct concrete actions and has minor overlap with sibling wiki skills, keeping it just below a perfect mark on specificity and distinctiveness.

Dimension	Reasoning	Score
Specificity	Names the domain ('an explicitly vault-scoped question from an Obsidian wiki') and one concrete action ('Answer... without changing it') with read-only intent, but does not list multiple distinct concrete actions beyond answering, so coverage is not comprehensive.	3 / 5
Completeness	Explicitly answers both what ('Answer an explicitly vault-scoped question from an Obsidian wiki without changing it') and when ('Use when the user selects the vault as the evidence source: ...') with concrete trigger phrases and an explicit routing boundary.	5 / 5
Trigger Term Quality	Comprehensive natural trigger phrases including synonyms — 'query the wiki, query quick, query deep, explain from the wiki, summarize the vault, find in wiki, search the wiki, or based on the wiki' — covering the ways a user would naturally request this skill.	5 / 5
Distinctiveness Conflict Risk	Clear niche (vault-scoped read-only wiki queries) with an explicit boundary ('Do not route ordinary general-knowledge questions here'), but minor overlap risk with closely related sibling skills (wiki-retrieve, wiki-cli) referenced in the body.	4 / 5
	Total	17 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
relative_links	Relative link issues: 3 suspicious	Warning

	Total	15 / 16 Passed

Repository: AgriciDaniel/claude-obsidian
Path: skills/wiki-query/SKILL.md
Commit: ad67087

Reviewed: 10 days 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.