BD kb_web_query
Answer Research KB dialogue questions with team-overview-guided web search, external citations, optional reference attachments, and no QA persistence.
Answer Research KB dialogue questions with team-overview-guided web search, external citations, optional reference attachments, and no QA persistence.
As a process D 46/100 · Unfinished process — weak spots: result and completion, when it triggers, inputs and preconditions
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- 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: 6. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
name-formatname should be kebab-case (lowercase letters, digits, hyphens) - warning
description-no-whendescription does not say WHEN to use the skill (no "use when")
Process rating: all ten parameters 46/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 40Consistency. Frontmatter name (kb_web_query) differs from the folder (kb-web-query)
- 50Failures and branches. 0 branches, has a failure section
- 60Tools and files. Uses tools (web, python, node) that frontmatter does not declare
- 100Steps. 23 steps
- 100Execution cost. Instruction body is 1047 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
- +4Description does not say when NOT to use the skill (false activations)
- +3Output format is not stated: the model decides each time
- -37 of 8 scripts are never mentioned in SKILL.md
- +1No license
- +2Single-language instructions
- +3Description length 150: enough signal without eating the budget
- +4Structure: 6 headings
- +3Step-by-step instructions: 23 items
- +4Has examples (8 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 64.