ha-discovery-augmentlisted

Augments an existing Home Assistant Custom Integration with one network or bus discovery mechanism beyond Zeroconf — DHCP, SSDP/uPnP, USB, HomeKit, or MQTT discovery — conforming to spec/ha/discovery-mechanisms. Sets the manifest matcher list, implements the typed async_step_<mechanism> in config_flow.py, forwards into a confirm step (never a direct async_create_entry), and wires the unique_id plus _abort_if_unique_id_configured(updates=...) host/IP update path (the Gold discovery-update-info rule). Narrows generic OUI/bridge-chip matchers. Activate on "add DHCP/SSDP/USB/HomeKit/MQTT discovery", "discover the device by MAC/vid:pid/model", "füge DHCP-Discovery hinzu". Do not activate for mDNS/Zeroconf (ha/zeroconf-discovery, scaffold), Bluetooth (ha/bluetooth), greenfield scaffolding (ha-integration-scaffold), generic config-flow auth steps (ha-config-flow-augment), 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 Discovery Augment Spec: `spec/claude/ha-discovery-augment/en.md` (EN canonical) / `spec/claude/ha-discovery-augment/de.md` (DE translation). ## Why this is a skill, not an agent - **Human-visible augmentation surface** — the user describes how the device announces itself and reads back the manifest matcher, the config-flow step, 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 mechanism choice, the matcher narrowing, and the Zeroconf/Bluetooth redirect are per-run dialogues the user approves before generation. - **Bounded, inline generation** — one mechanism's manifest matcher plus its discovery step fit inline; no isolated agent context is needed. - Counter-dimension considered: the draft→validate loop could be an agent, but the mechanism decision and the report belong in the user's working context; skill wins. ## When this skill activates Use this skill to add **one** discovery mechanism — DHCP, SSDP/uPnP, USB, HomeKit, or MQTT — to an existing integration so the user doesn't have to type a host or pick the integration manually. ## When NOT to activate - mDNS/Zeroconf discovery → `ha/zeroconf-discovery` (the scaffold already produces it) - Bluetooth discovery → separate sibling spec `ha/bluetooth` - greenfield integration scaffolding → `ha-integration-scaffold` - generic config-flow auth/selection st