ha-helper-scaffoldlisted

Scaffolds one Home Assistant stateful helper entity as a spec-conformant YAML block from a described intent — input_boolean, input_button, input_datetime, input_number, input_select, input_text, counter, timer, or schedule — conforming to the matching spec/ha-automation/<topic>. Picks the right helper type, sets every mandatory field (min/max, options, has_date/has_time, duration, weekly windows, restore), redirects measured/derived values to a sensor, names per ha/naming-conventions, and reports the helper's state, trigger events, and mutating services. Activate on "add an input_number/input_select helper for…", "create a timer/counter/schedule for…", "lege einen Helfer für… an". Do not activate for automations/scripts/scenes (ha-automation-author), derived/statistical sensors (ha-derived-sensor-author), real integration sensors, blueprints (ha-blueprint-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 Helper Scaffold Spec: `spec/claude/ha-helper-scaffold/en.md` (EN canonical) / `spec/claude/ha-helper-scaffold/de.md` (DE translation). ## Why this is a skill, not an agent - **Human-visible scaffolding surface** — the user describes what state they need held and reads back the YAML block plus the helper's read/mutate surface; a skill keeps this on the visible command surface, like the sibling scaffold skills. - **Mid-flow interactivity** — helper-type confirmation and the measured-value redirect are per-run dialogues the user approves before scaffolding. - **Bounded, inline generation** — a single helper block is small enough to generate inline; no isolated agent context is needed. - Counter-dimension considered: a one-shot generator could be an agent, but the type decision and the reported surface belong in the user's working context; skill wins. ## When this skill activates Use this skill to scaffold **one** stateful helper entity from a described intent: `input_boolean`, `input_button`, `input_datetime`, `input_number`, `input_select`, `input_text`, `counter`, `timer`, or `schedule`. ## When NOT to activate - an automation, script, scene, template entity, or command integration → `ha-automation-author` - a derived/statistical helper sensor (`bayesian`, `derivative`, … `utility_meter`, `group`) → `ha-derived-sensor-author` - a measured value from real hardware → belongs in an integration, not an input helper - a blueprint → `ha-blueprint-scaffold` - deploying/im