ha-automation-authorlisted

Authors one Home Assistant automation-logic or command artifact as spec-conformant YAML (or a sandboxed .py) from a described intent — an automation, script, scene, generic template entity, or a rest_command / shell_command / python_script — conforming to the matching spec/ha-automation/<topic>. Picks the artifact type, enforces a deliberate mode, stable id/unique_id, unavailable-guarded templates, shell-injection and python-sandbox safety, redirects legacy trigger helpers to modern equivalents, validates offline, and returns a conformance report. Activate on "write an automation that…", "create a script for…", "add a scene/template sensor/rest_command for…", "schreibe eine Automation, die…", "erstelle ein Script für…". Do not activate for blueprints (ha-blueprint-scaffold), stateful helpers (ha-helper-scaffold), derived/statistical sensors (ha-derived-sensor-author), Python custom integrations (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 Automation Author Spec: `spec/claude/ha-automation-author/en.md` (EN canonical) / `spec/claude/ha-automation-author/de.md` (DE translation). ## Why this is a skill, not an agent - **Human-visible authoring surface** — the user describes an intent and reads back the generated YAML and the conformance report; a skill keeps that on the visible command surface, like the sibling `ha-blueprint-scaffold`. - **Mid-flow interactivity** — artifact-type confirmation and the legacy-helper redirect are per-run dialogues the user must see and approve before generation. - **Orchestrator-leaning** — it may later dispatch a generation agent (as `ha-blueprint-scaffold` dispatches `ha-blueprint-author`); the skill-orchestrates default keeps the entry point in skill form. - Counter-dimension considered: the draft→validate→iterate loop could be an agent, but the type decision and the report belong in the user's working context; skill wins. ## When this skill activates Use this skill to author **one** non-blueprint automation-logic or command artifact from a described intent: an `automation`, `script`, `scene`, generic `template` entity, or a `rest_command` / `shell_command` / `python_script`. ## When NOT to activate - a parameterized, shareable blueprint → `ha-blueprint-scaffold` / `ha-blueprint-author` - a stateful helper (`input_*`, `counter`, `timer`, `schedule`) → `ha-helper-scaffold` - a derived/statistical helper sensor (`bayesian`, `derivative`, `filter`, `min_max`, `statistics