CC worker-benchmarks
Run comprehensive worker system benchmarks and performance analysis
The skill promises to run comprehensive worker system benchmarks and output performance metrics. The files contain a single folder with 848 tokens of analyzer instructions, no scripts or examples. Quality score 72, process score 59—the gap suggests gaps in documentation or execution logic.
In practice: the skill targets nine platforms (Claude, Gemini, Cursor, and others), but no actual sandbox test was run. No critical errors, but specific performance metrics and interpretation guidelines are missing from the description. Install if you need a template for a first pass; rebuild if you need a ready-to-use tool.
Run comprehensive worker system benchmarks and performance analysis
As a process C 59/100 · Has gaps — weak spots: when it triggers, inputs and preconditions, failures and branches
The same skill appears in 1 more place: claude-flow
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: 1. 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")
Process rating: all ten parameters 59/100
- 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
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 1 mutating operations with no state check
- 60Result and completion. Output format stated, no completion criterion
- 100Tools and files. No external tools needed
- 100Steps. 20 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 848 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)
- +3Description length 67: 120–800 characters recommended
- +1No license
- +2Single-language instructions
- +4Structure: 13 headings
- +3Step-by-step instructions: 20 items
- +3Output format is stated explicitly
- +4Has examples (4 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 72.