ha-device-automation-addlisted

Augments an existing Home Assistant Custom Integration with one device-automation kind — a device trigger, condition, or action — conforming to spec/ha/device-automations. Creates the matching platform module (device_trigger.py / device_condition.py / device_action.py) with its async_get_* list (CONF_PLATFORM/CONF_DOMAIN/CONF_DEVICE_ID/CONF_TYPE fields), a module-constant *_SCHEMA the core applies (never manually), the attach/check/call function, optional capabilities, and the device_automation strings.json entries. Runs an entity-vs-device value check and flags HA's stance that no new device automations are accepted. Activate on "add a device trigger for…", "expose a remote button press as a device trigger", "füge eine Device-Action hinzu". Do not activate for entity automations (ha/entity-architecture), registered services (ha-service-definition-add), greenfield scaffolding (ha-integration-scaffold), or deploying to a live HA instance.
nolte/claude-home-assistant · ★ 1 · AI & Automation · score 68

Install: claude install-skill nolte/claude-home-assistant

# HA Device Automation Add Spec: `spec/claude/ha-device-automation-add/en.md` (EN canonical) / `spec/claude/ha-device-automation-add/de.md` (DE translation). ## Why this is a skill, not an agent - **Human-visible augmentation surface** — the user describes a device interaction and reads back the platform module, the schema, and the conformance report; a skill keeps this on the visible command surface, like the sibling augment skills (`ha-config-flow-augment`, `ha-coordinator-add`, `ha-repairs-add`). - **Mid-flow interactivity** — the kind decision and the entity-vs-device value check (with HA's "no new device automations" caveat) are per-run dialogues the user approves before generation. - **Bounded, inline generation** — one platform module plus its schema and strings fit inline; no isolated agent context is needed. - Counter-dimension considered: the draft→validate loop could be an agent, but the kind decision and the trade-off advice belong in the user's working context; skill wins. ## When this skill activates Use this skill to add **one** device-automation kind — a device trigger, condition, or action — to an existing integration, typically for a device-native event with no entity binding (e.g. a remote button press). ## When NOT to activate - entity automations (state/event model without device indirection) → `ha/entity-architecture` - a registered service with its own schema → `ha-service-definition-add` / `ha/services` - greenfield integration scaffolding → `ha