BC research-lookup
Answers a focused factual or technical question from current sources with links, a definition, a number, a method's origin, a library's behavior, what a specific paper found, using literature, research_search, webfetch and the scholarly APIs, and knowing when the question is really a literature review. Use for quick grounded lookups during research or writing. Not for surveying a topic (use literature-review) or for verifying a manuscript's citations (use citations).
Answers a focused factual or technical question from current sources with links, a definition, a number, a method's origin, a library's behavior, what a…
As a process C 57/100 · Has gaps — weak spots: result and completion, inputs and preconditions, failures and branches
How to improve
- Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 0
✓ No critical or high findings
Files scanned: 1. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- note
frontmatter-keyunknown frontmatter key "summary" - note
frontmatter-keyunknown frontmatter key "role"
Process rating: all ten parameters 57/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Failures and branches. Linear process with no failure handling
- 0Progress reporting. Says nothing while it works
- 50When it triggers. No condition that starts the skill
- 100Tools and files. Tools declared in frontmatter
- 100Steps. 18 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 755 tokens
- 100Running it twice. No mutating operations
Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.
Quality signals
- +5Description has no quoted example phrases that should trigger the skill
- +3Output format is not stated: the model decides each time
- +4No input/output examples
- +2Single-language instructions
- +4Description says when NOT to use the skill
- +3Description length 471: enough signal without eating the budget
- +4Structure: 5 headings
- +3Step-by-step instructions: 18 items
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 83.