BD home-assistant-hub
Real-time Home Assistant monitoring, alert rules, TTS voice notifications on Echo devices, Telegram delivery, entity inspection. Service calls are HARD-DENIED by default — require explicit safe-domains opt-in.
Real-time Home Assistant monitoring, alert rules, TTS voice notifications on Echo devices, Telegram delivery, entity inspection.
As a process D 45/100 · Unfinished process — weak spots: result and completion, when it triggers, inputs and preconditions
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- 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 Dangerous commands
cmd-background-processdaemon.sh:15Starts a background / autostarted processdisown $NODEPID
-
low Exfiltration
exfil-webhook-urlscripts/telegram-deliver.js:61Webhook / callback URL commonly used for exfiltration (verify the destination) (placeholder value)const url = `https://api.telegram.org/bot${botToken}/sendMessage`;placeholder -
low Dangerous commands
cmd-background-processSKILL.md:66Starts a background / autostarted process (quoted — discussed, not commanded)The hub runs as background processes (`nohup`, `disown`) that persist beyond your session. `pkill -f "ha-hub.js start"` can match multiple processes. Always verify process state before killing.
quoted -
low Dangerous commands
cmd-background-processstart.sh:8Starts a background / autostarted processnohup node "$SCRIPT_DIR/scripts/ha-hub.js" start > "$SCRIPT_DIR/logs/hub.log" 2>&1 &
-
low Dangerous commands
cmd-background-processstart.sh:11Starts a background / autostarted processdisown $HUB_PID
Files scanned: 12. 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") - note
frontmatter-keyunknown frontmatter key "homepage"
Process rating: all ten parameters 45/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. 4 mutating operations with no state check
- 50Failures and branches. 0 branches, has a failure section
- 60Tools and files. Uses tools (bash, node) that frontmatter does not declare
- 75Steps. 3 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 3702 tokens
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 209: enough signal without eating the budget
- +4Structure: 19 headings
- +3Step-by-step instructions: 3 items
- +4Has examples (15 code blocks)
- +4Reference files are cited in the instructions (1 of 1)
- +3All 3 scripts are documented
Quality base 70; lint remarks subtract, signals add up to 100. Result: 78.