CC operator-scorecard
Three recap modes - default synthesizes agent health, community growth, and economic activity into a was-it-worth-it verdict; ops recaps what shipped and failed; push ranks push impact.
Three recap modes - default synthesizes agent health, community growth, and economic activity into a was-it-worth-it verdict; ops recaps what shipped and…
As a process C 51/100 · Has gaps — 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 SKILL.md body is over 5,000 tokens: move reference detail into references/ and load it when needed.
- The text references files that are not there: add them or drop the references.
- 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") - warning
body-longSKILL.md body ≈ 9110 tokens (recommended < 5000); move details to references/ - warning
missing-refreference to a missing file: [^/]+/[^/.]+ - note
edit-residuethe text marks something as outdated (lines 13, 45, 46): check that old rules are not kept next to new ones — the full check reads the text for contradictions
Process rating: all ten parameters 51/100
- 0Tools and files. 1 referenced file(s) missing: [^/]+/[^/.]+
- 0Result and completion. Does not say what the result is
- 30Inputs and preconditions. Does not say what the process needs to start
- 40Execution cost. Instruction body is 9110 tokens: crowds the task out of the window
- 50When it triggers. No condition that starts the skill
- 100Steps. 99 steps
- 100Failures and branches. 12 branches, has a failure section
- 100Consistency. Name and required fields are in place
- 100Running it twice. Mutating operations check current state
- 100Progress reporting. Reports progress
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low 15 top-level sections: this looks like several domains in one skill
- low The response is described with custom markup (10 tags): a typed call is more reliable
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
- +1No license
- +2Single-language instructions
- +3Description length 185: enough signal without eating the budget
- +4Structure: 35 headings
- +3Step-by-step instructions: 99 items
- +4Has examples (15 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 56.