ha-esphome-config-augmentlisted

Augments an existing ESPHome device-config YAML with one addition — a sensor/actuator platform block, an I2C bus or multiplexer channel, a locally consumed external component, or a new shared-package binding — conforming to spec/ha/esphome-config-patterns. Reads the device file and its shared packages first, verifies the component schema against the official ESPHome docs, keeps naming substitution-derived and credentials resolved from environment variables, and never duplicates a block a shared package already provides. Activate on "add a sensor to my ESPHome device", "wire a BME280 into box-01", or equivalent German requests. Do not activate for a brand-new device file (ha-esphome-config-scaffold), for reshaping the shared package itself (ha-esphome-package-author), for a Home-Assistant-driven value (ha-esphome-binding-add), for authoring a custom component (out of scope), for HA-side automations or dashboards, or for compiling/flashing.
nolte/claude-home-assistant · ★ 1 · AI & Automation · score 68

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

# HA ESPHome Config Augment Spec: `spec/claude/ha-esphome-config-augment/en.md` (EN canonical) / `spec/claude/ha-esphome-config-augment/de.md` (DE translation). Grounding spec: `spec/ha/esphome-config-patterns/en.md`. Adds exactly one addition to one existing device file per invocation, conforming to every MUST in the grounding spec. ## Why this is a skill, not an agent - **Quick, targeted change in the current context (decisive):** one block in one YAML file the conversation is already working on; per the change-scope and latency dimensions this routes to the main thread. - **Mid-flow approval:** the component choice, target bus, and naming are confirmed with the operator before writing — a wrong bus binding on a multiplexed topology is expensive to debug on-device. - **Counter-dimension considered:** schema lookup against the ESPHome docs is self-contained (agent bias), but the diff is small and iterated in conversation — isolation would cost more than it protects. ## When this skill activates The user asks to extend an existing ESPHome device — "add an SCD30 to box-02", "füge einen Sensor zum ESPHome-Gerät hinzu" — and the named device file exists. ## When NOT to activate - a brand-new device → `ha-esphome-config-scaffold` - the shared package itself (cut, parameters, `!extend` / `!remove`) → `ha-esphome-package-author` - a value or command Home Assistant drives → `ha-esphome-binding-add` - authoring the custom component itself (C++/Python) → out of scope; no ownin