CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

wiki-query

Query the LLM Wiki — reads index.md first, drills into 3-10 relevant pages, synthesizes an answer with inline [[wikilink]] citations, and offers to file the answer back as a new comparison or synthesis page. Usage /wiki-query "<question>"

Quality

83%

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

82%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 an exceptionally lean, well-organized command doc: a clear six-step workflow, concrete paths and citation formats, and disciplined delegation to a sub-agent and reference files. The gaps are modest — no executable invocation examples for the two scripts, no handling for the no-results case, and references that point outside the skill's own bundle.

Suggestions

Show a one-line invocation example for each script (e.g. how to pass a query to wiki_search.py and what it returns) so the fallback and logging steps are copy-paste ready.

Add a brief branch for the zero-relevant-pages case (e.g. "if the index and BM25 both come up empty, say so and suggest filing the question as a stub page") to close the workflow's validation gap.

Since the referenced files (query-workflow.md, agents/wiki-librarian.md) are not part of this skill's bundle, consider either shipping them as local bundle files or stating in the body that this is a thin root-level copy that depends on the llm-wiki skill's files.

DimensionReasoningScore

Conciseness

The body never explains concepts Claude already knows (BM25 is named, not taught; sub-agents and wikilinks are used without preamble) and every section is functional: usage examples, a 6-step process, an output-format table, script paths, and three rules. Not 4: there is no over-explanation or padding to trim — the mild overlap between the usage examples and the output-format table serves different purposes (invocation vs. output shape).

5 / 5

Actionability

Concrete guidance throughout: "reads 3-10 pages in full", "runs engineering/llm-wiki/skills/llm-wiki/scripts/wiki_search.py (BM25)", "inline [[sources/xxx]] citations", "usually in comparisons/ or synthesis/". Not 5: the scripts are named by path but no invocation example is given (e.g. the argument shape for wiki_search.py), so the fallback and logging steps are not copy-paste ready; not 3: the guidance is specific and executable in structure, not pseudocode.

4 / 5

Workflow Clarity

The "What happens" section gives a clear 6-step sequence (index read → drill-in → follow links → fallback search if the index isn't enough → synthesize → offer file-back), with the fallback acting as a conditional checkpoint and the file-back gated on user confirmation. Not 5: there is no explicit validation of the synthesized answer and no guidance for the zero-relevant-pages case; not 3: the sequence is well defined with a conditional recovery path and the Rules section enforces per-claim citations as a quality check.

4 / 5

Progressive Disclosure

The body is a lean overview that delegates detail via clearly signaled one-level-deep references ("agents/wiki-librarian.md", "→ engineering/llm-wiki/skills/llm-wiki/SKILL.md", "→ engineering/llm-wiki/skills/llm-wiki/references/query-workflow.md") with a dedicated Skill Reference section. Not 5: the referenced files live outside this skill's directory (no local references/, scripts/, or assets/ bundle ships alongside this SKILL.md), so navigation depends on the wider repo layout and the repo-root-relative paths noted in the sync comment; not 3: structure is good and references are explicit, not buried.

4 / 5

Total

17

/

20

Passed

Description

75%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 specific, third-person, and clearly scoped to querying an LLM wiki, with concrete lifecycle actions and good natural keywords. Its main weakness is the missing 'Use when...' trigger clause — it provides invocation syntax but never states when the skill should be used, which caps completeness at 3.

Suggestions

Add an explicit trigger clause, e.g. "Use when the user asks a question about the wiki, wants sources compared or synthesized, or mentions wikilinks" — this lifts completeness from 3 to 5.

Include a few natural phrasing variations users might say ("ask the wiki", "search my notes", "look up") to round out trigger-term coverage.

Consider naming the wiki location or entry point (e.g. "wiki/index.md") in the description so the skill is distinguishable from any other wiki-query skill in the library.

DimensionReasoningScore

Specificity

Quotes: "reads index.md first", "drills into 3-10 relevant pages", "synthesizes an answer with inline [[wikilink]] citations", "offers to file the answer back as a new comparison or synthesis page" — multiple specific concrete actions covering the full query lifecycle, matching the comprehensive anchor. Not 4: unlike "minor gaps in coverage", the description covers input discovery, synthesis, citation, and persistence; not lower because nothing here is generic.

5 / 5

Completeness

The 'what' is clear ("reads index.md first... synthesizes an answer... offers to file the answer back"), but the only 'when' guidance is invocation syntax ("Usage /wiki-query \"<question>\""), which shows how to call it, not when to use it. Per the guideline, a missing 'Use when...' clause or equivalent explicit trigger guidance caps completeness at 3, so it cannot score 4 despite the strong 'what'.

3 / 5

Trigger Term Quality

Quotes: "Query the LLM Wiki", "citations", "comparison", "synthesis page" — good natural keywords users of this wiki would say. Not 5: common variations like "ask the wiki", "search the wiki", or "look up" are missing; not 3: coverage goes beyond "some relevant keywords" by naming comparison, synthesis, and citation tasks.

4 / 5

Distinctiveness Conflict Risk

Quotes: "Query the LLM Wiki", "inline [[wikilink]] citations" — a clear niche with distinct triggers (wiki, wikilinks, index.md) that no generic research or search skill would claim. Not 4: there is no meaningful overlap risk; the LLM-wiki framing is unambiguous.

5 / 5

Total

17

/

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

alirezarezvani/claude-skills

Path

.gemini/skills/wiki-query/SKILL.md

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.