CD validate
Freshly judge exact subject content against bead or caller acceptance, optionally persist verdict.v2 for a declared consumer, and stop. Triggers: "validate", "independently validate", "vibe".
Freshly judge exact subject content against bead or caller acceptance, optionally persist verdict.v2 for a declared consumer, and stop. Triggers: "validate"…
As a process D 46/100 · Unfinished process — References files that are not bundled: scripts/test-ci-deterministic-gates.sh
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.
- 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: 5. 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: scripts/test-ci-deterministic-gates.sh - note
frontmatter-keyunknown frontmatter key "practices" - note
frontmatter-keyunknown frontmatter key "hexagonal_role" - note
frontmatter-keyunknown frontmatter key "consumes" - note
frontmatter-keyunknown frontmatter key "produces" - note
frontmatter-keyunknown frontmatter key "context_rel" - note
frontmatter-keyunknown frontmatter key "skill_api_version" - note
frontmatter-keyunknown frontmatter key "output_contract"
Process rating: all ten parameters 46/100
- 0Tools and files. 1 referenced file(s) missing: scripts/test-ci-deterministic-gates.sh
- 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
- 40Result and completion. Does not say what the result is
- 50Failures and branches. 0 branches, has a failure section
- 100Steps. 12 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1508 tokens
- 100Running it twice. Mutating operations check current state
- low The response is described with custom markup (5 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
- +4Description does not say when NOT to use the skill (false activations)
- +3Output format is not stated: the model decides each time
- +4No input/output examples
- -33 of 4 scripts are never mentioned in SKILL.md
- +1No license
- +2Single-language instructions
- +5Description quotes 2 example trigger phrases
- +3Description length 191: enough signal without eating the budget
- +4Structure: 7 headings
- +3Step-by-step instructions: 12 items
Quality base 70; lint remarks subtract, signals add up to 100. Result: 61.