CD SKILL.md
Control Home Assistant devices.
Control Home Assistant devices.
As a process D 35/100 · Unfinished process — weak spots: steps, result and completion, when it triggers
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
For the model run — optional
- 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 · 5
✓ No critical or high findings
Medium and low: 5
-
low Secrets in code
secret-high-entropy-tokenpackage-lock.json:133High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)"integrity": "sha5…wIN//F77/IADDSs58i+MDaO…jeo+YFg==",
detector -
low Secrets in code
secret-high-entropy-tokenpackage-lock.json:322High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)"integrity": "sha5…rV7+Ocb9…VUE+VuKP…3mQ==",
detector -
low Secrets in code
secret-high-entropy-tokenpackage-lock.json:384High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)"integrity": "sha5…MY5+vUsR…C6y+e9rv…1Aw==",
detector -
low Secrets in code
secret-high-entropy-tokenpackage-lock.json:403High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)"integrity": "sha5…tVz+G+ogqe…TUV+SUcj…k2A==",
detector -
low Secrets in code
secret-high-entropy-tokenpackage-lock.json:525High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)"integrity": "sha5…Ki1+FTWx…bJ0+OjgA==",
detector
Files scanned: 28. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
name-formatname should be kebab-case (lowercase letters, digits, hyphens) - warning
description-shortdescription under 40 chars: too little signal for triggering - warning
description-no-whendescription does not say WHEN to use the skill (no "use when")
Process rating: all ten parameters 35/100
- 0Result and completion. Does not say what the result is
- 0When it triggers. No condition that starts the skill
- 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
- 25Steps. 1 steps
- 40Consistency. Frontmatter name (SKILL.md) differs from the folder (claw-hass)
- 100Tools and files. No external tools needed
- 100Execution cost. Instruction body is 30 tokens
- 100Running it twice. No mutating operations
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)
- +3Description length 31: 120–800 characters recommended
- +3No numbered steps or checklist
- +3Output format is not stated: the model decides each time
- +4No input/output examples
- -15SKILL.md body under 300 characters: nearly empty
- +1No license
- +2Single-language instructions
- +4Structure: 3 headings
Quality base 70; lint remarks subtract, signals add up to 100. Result: 34.