CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

query

Search the FPF knowledge base and display hypothesis details with assurance information

Quality

68%

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

Fix and improve this skill with Tessl

tessl review fix ./antigravity/skills/query/SKILL.md

The canonical home for this skill is query in NeoLabHQ/context-engineering-kit

SKILL.md
Quality
Evals
Security

Quality

Content

67%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 well-structured, task-specific reference with concrete search locations, output templates, and display legends for R_eff and dependency trees. Its main weaknesses are redundancy between the Examples and Search Methods/Output Format sections and unspecified search mechanics.

Suggestions

Merge the "Examples" section into "Search Methods" (or trim it to one end-to-end example) to remove the duplicated invocations and output blocks.

Specify how to search, e.g., "grep titles and content across .fpf/knowledge/*/*.md; an exact ID match short-circuits to the detail view" rather than the bare "Search ... by user query".

Consider moving the long Output Format example into a references/ file to slim the SKILL.md body toward an overview.

DimensionReasoningScore

Conciseness

The body avoids explaining known concepts and stays task-specific, but the "Examples" section duplicates the "Search Methods" invocations (/fpf:query caching, redis-caching, DRR) and re-renders the Output Format blocks, so it could be meaningfully tightened.

3 / 5

Actionability

Concrete guidance throughout: exact search locations (.fpf/knowledge/L0/ ... .fpf/evidence/), copy-ready output templates, and a legend for R:X.XX / CL:N. The how of matching text is left unspecified, which keeps it at mostly-executable rather than fully complete.

4 / 5

Workflow Clarity

A clear numbered 3-step run-time sequence with explicit conditionals ("If layer >= L1", "If has dependencies") for a read-only skill with no validation cap; the search mechanics themselves are implicit, a minor gap.

4 / 5

Progressive Disclosure

No bundle files exist and the single SKILL.md is well-organized with clear sections (Action, Search Locations table, Output Format, Search Methods, legends). The ~177-line body inlines long example-output blocks that could be split out, so structure is good but not fully optimized.

4 / 5

Total

15

/

20

Passed

Description

53%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 third-person, concise, and names a distinct domain with two concrete actions, but it reads as a bare capability statement. It lacks any "when to use" trigger guidance and natural trigger terms, which limits its discoverability and keeps completeness at the cap.

Suggestions

Add an explicit trigger clause, e.g., "Use when the user asks to query, search, or look up hypotheses, decisions (DRRs), or R_eff scores in the FPF knowledge base."

Include natural trigger phrases and synonyms users would say ("query", "lookup", "R_eff", "evidence", "dependency tree") alongside the domain vocabulary.

Enumerate the concrete outcomes (list hypotheses by layer, show R_eff breakdown, render dependency trees, list Design Rationale Records) to lift specificity toward comprehensive coverage.

DimensionReasoningScore

Specificity

"Search the FPF knowledge base and display hypothesis details with assurance information" names the domain plus two concrete actions (search, display), but stops short of listing several specific actions, matching the anchor for 1-2 concrete actions.

3 / 5

Completeness

The "what" is clear (search and display hypothesis details with assurance information) but there is no "Use when..." clause or equivalent trigger guidance, which caps completeness at 3 per the judging guidelines.

3 / 5

Trigger Term Quality

Terms like "search", "knowledge base", "hypothesis", and "assurance" are relevant but the description omits natural variations users would actually say (e.g., "query", "lookup", "R_eff", "evidence"), matching the some-relevant-keywords anchor.

3 / 5

Distinctiveness Conflict Risk

The FPF-specific vocabulary ("FPF knowledge base", "hypothesis details", "assurance") carves out a distinct niche with low overlap risk, though it falls short of the anchor-5 examples that pair niche actions with explicit trigger phrases.

4 / 5

Total

13

/

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

NeoLabHQ/context-engineering-kit

Path

antigravity/skills/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.