CD implement
Change or repair code, config or services without weakening tests; report what ran and what did not. Use when: implementing a change or fixing a defect.
Change or repair code, config or services without weakening tests; report what ran and what did not.
As a process D 43/100 · Unfinished process — References files that are not bundled: ../test/SKILL.md, ../test/references/error-recovery.md, ../rpi/references/boundaries.md
The same skill appears in 1 more place: agentops
What is at stake
Medium-severity findings: the skill is probably honest, but read what alarmed the scanner.
Below is the worst case for this category. The finding here is medium: the guard saw a sign, not a proof.
The skill contains commands that delete files, rewrite disks or execute code fetched from the network. The agent may run them without asking if it believes the instructions require it.
Replace destructive commands with safe equivalents that ask for confirmation, scope them to one folder, and stop piping curl into a shell: pin a version and a checksum.
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 · 1
✓ No critical or high findings
Medium and low: 1
-
medium Dangerous commands
cmd-pipe-to-shellreferences/scaffold/agent-facing-tool-scaffolds.md:12Downloads and executes remote code from an unrecognised host (pipe to shell) (quoted — discussed, not commanded)- Avoid `curl | sh` in generated docs unless the repo explicitly accepts it.
quoted
Files scanned: 5. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
missing-refreference to a missing file: ../test/SKILL.md - warning
missing-refreference to a missing file: ../test/references/error-recovery.md - warning
missing-refreference to a missing file: ../rpi/references/boundaries.md - warning
missing-refreference to a missing file: ../agent-native/references/session-associations.md - warning
missing-refreference to a missing file: ../agent-native/SKILL.md - warning
missing-refreference to a missing file: ../using-gc/SKILL.md - warning
missing-refreference to a missing file: ../rpi/SKILL.md - warning
missing-refreference to a missing file: ../validate/SKILL.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 "output_contract" - note
frontmatter-keyunknown frontmatter key "context_rel" - note
frontmatter-keyunknown frontmatter key "skill_api_version" - note
edit-residuethe text marks something as outdated (lines 26, 27): check that old rules are not kept next to new ones — the full check reads the text for contradictions
Process rating: all ten parameters 43/100
- 0Tools and files. 8 referenced file(s) missing: ../test/SKILL.md, ../test/references/error-recovery.md, ../rpi/references/boundaries.md
- 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
- 30Running it twice. 5 mutating operations with no state check
- 40Result and completion. Does not say what the result is
- 50Failures and branches. 0 branches, has a failure section
- 100Steps. 11 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 2868 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)
- +3Output format is not stated: the model decides each time
- +1No license
- +2Single-language instructions
- +3Description length 152: enough signal without eating the budget
- +4Structure: 6 headings
- +3Step-by-step instructions: 11 items
- +4Has examples (1 code blocks)
- +4Reference files are cited in the instructions (3 of 3)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 73.