CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

query

Answer questions using the brain's knowledge with 3-layer search, synthesis, and citation propagation. Use when the user asks a question, wants a lookup, or needs information from the brain.

Quality

86%

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

77%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 delivers excellent actionability and a well-validated workflow — concrete commands, worked graph examples, and a thorough failure-handling section with recovery loops. It is held back by redundant repetition of citation/hallucination rules, protocol-level detail inlined in SKILL.md, and the absence of a reference bundle to split that detail into.

Suggestions

Consolidate the citation, no-hallucination, and source-precedence rules — currently repeated across Contract, Phases, Output Format, Quality Rules, and Citation in Answers — into one authoritative section.

Move the Token-Budget Awareness internals (cost formulas, fractional-budget compatibility, adoption verification) into a reference file such as references/budget-policy.md, keeping only the recall example and the choose-recall-vs-search guidance inline.

Add a clearly signaled references section listing brain-first.md, MEMORY_VERBS_v1.md, and agent-operator-protocol.md with one-line descriptions instead of burying the links mid-prose.

DimensionReasoningScore

Conciseness

Mostly dense and useful, but citation rules are repeated across four sections (Contract, Output Format, Quality Rules, Citation in Answers), 'never hallucinate' appears four times, source precedence is stated three times, and the Token-Budget Awareness section carries protocol-spec internals (ceil cost estimates, fractional-budget compatibility, adoption-verification caveats) plus version/date-sensitive details ('gbrain ≥ 0.43', 'v0.10.1+', '2026-09-01') outside any deprecated section. Not 4: the redundancy and padding are more than minor; not 2: the phases, failure handling, and graph sections are tight and earn their tokens.

3 / 5

Actionability

Fully executable, copy-paste-ready commands cover the common cases: 'gbrain query "<q>" --since 2026-09-01 --until 2026-09-30', four worked graph-query examples ('gbrain graph-query companies/acme --type works_at --direction in'), and a recall example given in both bash and MCP JSON forms. This matches the anchor for specific examples covering common cases.

5 / 5

Workflow Clarity

The five-phase sequence (decompose → execute → read → synthesize → flag gaps) is explicit, phase 5 integrates notice-checking before claiming gaps, and 'When it fails' provides concrete feedback loops (degraded → try exact names/synonyms and surface the fix; page_not_found → search by title and check --source; listing_truncated → narrow before claiming absence). Clear sequence with explicit validation and error-recovery loops.

5 / 5

Progressive Disclosure

Good section headers, but there is no bundle: external references (skills/conventions/brain-first.md, docs/protocol/MEMORY_VERBS_v1.md, ../conventions/agent-operator-protocol.md) are buried mid-sentence in prose rather than clearly signaled, and roughly 45 lines of budget-packing protocol detail belong in a separate reference file. This matches 'some structure but content that should be separate is inline'; not 4 because the navigation to deeper material is not clearly organized.

3 / 5

Total

16

/

20

Passed

Description

91%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: it states concrete capabilities, gives an explicit 'Use when' clause with natural trigger phrasing, and the frontmatter's dedicated triggers list makes discovery terms comprehensive. The only weaknesses are slight under-coverage of the skill's full capability set and a broad 'asks a question' trigger that could collide with general search skills.

DimensionReasoningScore

Specificity

Lists several concrete actions — '3-layer search, synthesis, and citation propagation' — matching the anchor for several specific actions with minor gaps; graph traversal, gap flagging, and timeline lookups documented in the body are absent, keeping it below comprehensive (5).

4 / 5

Completeness

Explicitly answers both: what ('Answer questions using the brain's knowledge with 3-layer search, synthesis, and citation propagation') and when ('Use when the user asks a question, wants a lookup, or needs information from the brain') with concrete trigger phrases — a direct match to the anchor-5 example pattern.

5 / 5

Trigger Term Quality

The description's 'Use when the user asks a question, wants a lookup, or needs information from the brain' is supplemented by an explicit frontmatter triggers list ('what do we know about', 'tell me about', 'who is', 'look up', 'search for', 'background on', 'connections', 'graph query') giving comprehensive natural-term coverage including synonyms. Not 4: common variations users would actually say are already enumerated.

5 / 5

Distinctiveness Conflict Risk

'Using the brain's knowledge' / 'from the brain' carves a clear niche, but 'when the user asks a question' is broad enough to overlap with general Q&A or web-search skills — mostly distinct with minor overlap risk, not the minimal-conflict clarity of anchor 5.

4 / 5

Total

18

/

20

Passed

Validation

87%

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

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

relative_links

Relative link issues: 1 suspicious

Warning

Total

14

/

16

Passed

Repository

garrytan/gbrain

Path

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.