BF api-contract-tester
Validate API contracts between services using consumer-driven contract testing. Generate and verify Pact contracts, OpenAPI compliance tests, and schema compatibility checks for microservices.
As a process F 47/100 · Will not run — References files that are not bundled: [^"]+
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- The text references files that are not there: add them or drop the references.
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: 2. 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") - warning
missing-refreference to a missing file: [^"]+
Process rating: all ten parameters 47/100
Will not run. References files that are not bundled: [^"]+
- 0Tools and files. 1 referenced file(s) missing: [^"]+
- 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
- 30Running it twice. 6 mutating operations with no state check
- 60Result and completion. Output format stated, no completion criterion
- 60Failures and branches. 2 branches
- 100Steps. 21 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1378 tokens
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)
- +1No license
- +2Single-language instructions
- +3Description length 192: enough signal without eating the budget
- +4Structure: 13 headings
- +3Step-by-step instructions: 21 items
- +3Output format is stated explicitly
- +4Has examples (9 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 69.
External checks
ClawHub: clean
The inspected skill content is repo-focused developer guidance with high-impact commands disclosed and generally gated by user intent or confirmation.
LLM: benign (medium) · VirusTotal: · 29 May 2026