CD test
Write or assess tests that prove behavior and would fail without the fix. Use when: writing tests, TDD, or asked whether a green test is enough.
Write or assess tests that prove behavior and would fail without the fix.
As a process D 47/100 · Unfinished process — References files that are not bundled: ../validate/SKILL.md, ../implement/SKILL.md, ../domain/references/standards/test-pyramid.md
How to improve
- 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: 12. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
missing-refreference to a missing file: ../validate/SKILL.md - warning
missing-refreference to a missing file: ../implement/SKILL.md - warning
missing-refreference to a missing file: ../domain/references/standards/test-pyramid.md - warning
missing-refreference to a missing file: ../implement/references/difficult-failures.md - 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 47/100
- 0Tools and files. 4 referenced file(s) missing: ../validate/SKILL.md, ../implement/SKILL.md, ../domain/references/standards/test-pyramid.md
- 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
- 100Steps. 22 steps
- 100Result and completion. Output format and completion criterion are stated
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 2477 tokens
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
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)
- -5Name "test" says nothing about the task
- -31 of 1 scripts are never mentioned in SKILL.md
- +1No license
- +2Single-language instructions
- +3Description length 144: enough signal without eating the budget
- +4Structure: 9 headings
- +3Step-by-step instructions: 22 items
- +3Output format is stated explicitly
- +4Has examples (1 code blocks)
- +4Reference files are cited in the instructions (10 of 10)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 68.