← ClaudeAtlas

home-assistantlisted

Create, edit, back up, or restore Home Assistant dashboards and inspect configuration registries. Use for advanced configuration; use ha_* Tools for ordinary device control.
Vironnimo/vbot · ★ 1 · AI & Automation · score 77
Install: claude install-skill Vironnimo/vbot
# Home Assistant Assume the Home Assistant connection is already configured and working. Do not guide connection setup or token creation. Use the four `ha_*` Tools for entity discovery, state inspection, service discovery, and ordinary device control; use the bundled WebSocket script only for deeper configuration that those Tools do not cover. ## Script contract - Run `python {baseDir}/scripts/ha_ws.py --help` before first use. - Include `HASS_TOKEN` in the shell Tool's `env_keys` on every script call. The script reads it directly and has no token argument; never place the value in a command, file, or output. - The script defaults to the bundled extension's standard Home Assistant URL. For an already-configured nondefault instance, pass its existing base URL with global `--url`; never change connection settings as part of this Skill. - Keep task files under `tmp/home-assistant/<task>/`. Store exported configs, proposed configs, and backups there unless the user requests a durable location. - Treat script JSON output as data. A nonzero exit code or `"ok": false` means the operation did not complete. ## Dashboard workflow 1. Discover real entity ids and capabilities with `ha_list_entities` and `ha_get_state`. Use the script's read-only `call` command for area, floor, device, label, or entity registries when the dashboard needs those relationships. 2. Run `dashboard-list`, then export the target with `dashboard-export`. Never design against guessed entities or overwrite a d