AB version-decide
Decide the NEXT SemVer version number from the SCOPE OF CODE CHANGES for an upcoming release, and output a single, unambiguous recommendation with cited standard clauses. Use only when the user is deciding which version to assign to a release they are about to cut (e.g. "what version should this release be", "major or minor or patch", "what to bump in 0.x", "how to advance alpha/beta/rc", "is this breaking"). NOT for: looking up an already-published version, asking the install command, CalVer/date-based versioning, or general release/project-management questions. Ships a deterministic arithmetic core: same input always yields the same output.
Decide the NEXT SemVer version number from the SCOPE OF CODE CHANGES for an upcoming release, and output a single, unambiguous recommendation with cited…
As a process B 72/100 · Nearly there — weak spots: result and completion, inputs and preconditions, running it twice
How to improve
- 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: 14. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- note
frontmatter-keyunknown frontmatter key "slug" - note
frontmatter-keyunknown frontmatter key "displayName" - note
frontmatter-keyunknown frontmatter key "summary" - note
edit-residuethe text marks something as outdated (lines 97): check that old rules are not kept next to new ones — the full check reads the text for contradictions
Process rating: all ten parameters 72/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 30Running it twice. 7 mutating operations with no state check
- 100Tools and files. Tools declared in frontmatter
- 100Steps. 18 steps
- 100When it triggers. States when to use and when not to
- 100Failures and branches. 5 branches, has a failure section
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 2733 tokens
- 100Progress reporting. Reports progress
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low The response is described with custom markup (3 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
- +3Output format is not stated: the model decides each time
- +2Single-language instructions
- +5Description quotes 5 example trigger phrases
- +4Description says when NOT to use the skill
- +3Description length 650: enough signal without eating the budget
- +4Structure: 13 headings
- +3Step-by-step instructions: 18 items
- +4Has examples (3 code blocks)
- +4Reference files are cited in the instructions (5 of 5)
- +3All 3 scripts are documented
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 98.