BC homey
Control Athom Homey smart home devices via local (LAN/VPN) or cloud APIs. List/control devices, trigger flows, query zones. Works with Homey Pro, Cloud, and Bridge.
Control Athom Homey smart home devices via local (LAN/VPN) or cloud APIs.
As a process C 56/100 · Has gaps — weak spots: result and completion, when it triggers, inputs and preconditions
How to improve
- 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:28High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)"integrity": "sha5…nS4+204nGb1RiX/WXYH…II9/e2DW…VvQ==",
detector -
low Secrets in code
secret-high-entropy-tokenpackage-lock.json:74High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)"integrity": "sha5…lFp+GOM5…xQA/qgTJ+8ANR3acjrog==",
detector -
low Secrets in code
secret-high-entropy-tokenpackage-lock.json:80High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)"integrity": "sha5…9dM/mwVgvbZJaSNaRk+bshk…Kbz+IoId…W0Q==",
detector -
low Secrets in code
secret-high-entropy-tokenpackage-lock.json:86High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)"integrity": "sha5…7Eq+PBZ7…nAJ+sLaS…Ld7+JrRJHA==",
detector -
low Secrets in code
secret-high-entropy-tokenpackage-lock.json:100High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)"integrity": "sha5…gXS+JH61oWprSLH+P+abTc…2u9/bUYNmHTGJx/UEmn…uig==",
detector
Files scanned: 23. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
✓ No remarks against the Agent Skills spec
Process rating: all ten parameters 56/100
- 0Result and completion. Does not say what the result is
- 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. 3 mutating operations with no state check
- 50Failures and branches. 0 branches, has a failure section
- 100Tools and files. No external tools needed
- 100Steps. 17 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1417 tokens
- low The response is described with custom markup (4 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)
- +3Output format is not stated: the model decides each time
- -44 reference files, but SKILL.md never points to them: the model will not open them
- -32 of 2 scripts are never mentioned in SKILL.md
- +1No license
- +2Single-language instructions
- +3Description length 164: enough signal without eating the budget
- +4Structure: 15 headings
- +3Step-by-step instructions: 17 items
- +4Has examples (17 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 77.