CF release
The single permitted path to a version tag, for any target declared in the project's .codearbiter/release-targets.md. Routed to when the user invokes /release on a non-default branch with a green suite. Takes the declared target as its one argument, derives the next identity under its declared version policy from Conventional-Commits history, rolls the commits into that target's CHANGELOG, writes an annotated tag in that target's namespace, and on authorization publishes it as a GitHub Release with the changelog section and exact declared assets. A release commit, if needed, routes through commit-gate; the tag and Release are never published without explicit authorization.
The single permitted path to a version tag, for any target declared in the project's .codearbiter/release-targets.md. Routed to when the user invokes /release…
As a process F 53/100 · Will not run — References files that are not bundled: ../../hooks/_releaselib.py, ../../hooks/<script>, ../../includes/anti-slop-design/core.md
How to improve
- 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
body-longSKILL.md body ≈ 27161 tokens (recommended < 5000); move details to references/ - warning
missing-refreference to a missing file: ../../hooks/_releaselib.py - warning
missing-refreference to a missing file: ../../hooks/<script> - warning
missing-refreference to a missing file: ../../includes/anti-slop-design/core.md - warning
missing-refreference to a missing file: ../../includes/anti-slop-design/medium-documents.md - note
edit-residuethe text marks something as outdated (lines 215, 234, 334, 335, 361): check that old rules are not kept next to new ones — the full check reads the text for contradictions
Process rating: all ten parameters 53/100
- 0Tools and files. 4 referenced file(s) missing: ../../hooks/_releaselib.py, ../../hooks/<script>, ../../includes/anti-slop-design/core.md
- 0Result and completion. Does not say what the result is
- 10Execution cost. Instruction body is 27161 tokens: crowds the task out of the window
- 30Inputs and preconditions. Does not say what the process needs to start
- 85Steps. 69 steps, 1 vague phrases
- 100When it triggers. States when to use and when not to
- 100Failures and branches. 2 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 The response is described with custom markup (62 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)
- -4Absolute local paths (C:\Users, /home/…): not portable
- +1No license
- +2Single-language instructions
- +3Description length 681: enough signal without eating the budget
- +4Structure: 11 headings
- +3Step-by-step instructions: 69 items
- +3Output format is stated explicitly
- +4Has examples (8 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 61.