BB api-review
Evaluates API surface design, consistency, and exemplar alignment
As a process B 69/100 · Nearly there — weak spots: when it triggers, inputs and preconditions, consistency
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
For the model run — optional
- 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: 5. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
description-no-whendescription does not say WHEN to use the skill (no "use when") - note
frontmatter-keyunknown frontmatter key "triggers" - note
frontmatter-keyunknown frontmatter key "source" - note
frontmatter-keyunknown frontmatter key "source_plugin"
Process rating: all ten parameters 69/100
- 0Inputs and preconditions. Does not say what the process needs to start
- 20When it triggers. No condition that starts the skill
- 40Consistency. Frontmatter name (api-review) differs from the folder (nm-pensive-api-review)
- 60Result and completion. Output format stated, no completion criterion
- 100Tools and files. No external tools needed
- 100Steps. 11 steps
- 100Failures and branches. 1 branches, has a failure section
- 100Execution cost. Instruction body is 958 tokens
- 100Running it twice. No mutating operations
- 100Progress reporting. Reports progress
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)
- +3Description length 65: 120–800 characters recommended
- +4No input/output examples
- +1No license
- +2Single-language instructions
- +4Structure: 19 headings
- +3Step-by-step instructions: 11 items
- +3Output format is stated explicitly
Quality base 70; lint remarks subtract, signals add up to 100. Result: 65.
External checks
ClawHub: clean
This skill is a documented API review workflow with broad activation terms but no hidden, destructive, or credential-seeking behavior.
LLM: benign (high) · VirusTotal: · 26 Aug 2026