ha-automation-solutionlisted

Plans and orchestrates a complete Home Assistant YAML solution from a result-oriented requirement, so the user never has to pick which authoring skill to use. Decomposes the requirement into the minimal combination of artifacts across the ha-automation skill family, presents a dependency-ordered artifact plan for approval, then dispatches ha-automation-author, ha-helper-scaffold, ha-derived-sensor-author, and ha-blueprint-scaffold in order — threading entity_ids between steps — and flags requirements that actually need a custom integration. Activate on "I want my heat pump's daily energy on the dashboard and an alert when it's high", "set up presence-based lighting that only runs in the evening", "baue mir eine Lösung, die…", "richte… ein". Do not activate for a single clear artifact (let the owning skill handle it), Python custom integrations (ha-integration-scaffold), or deploying to a live HA instance. Supports resume on re-invocation.
nolte/claude-home-assistant · ★ 1 · AI & Automation · score 68

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

# HA Automation Solution Spec: `spec/claude/ha-automation-solution/en.md` (EN canonical) / `spec/claude/ha-automation-solution/de.md` (DE translation). This skill is the **front door** to the `ha-automation` skill family. It does not generate any artifact itself — it decomposes the requirement, plans the combination, and dispatches the owning authoring skills, each of which owns its generation and spec conformance. ## Why this is a skill, not an agent - **Plan-before-generate gate** — the artifact plan must be presented and explicitly approved before any generation; that human-visible gate is core to the contract and an agent's fire-and-forget shape would lose it. - **Mid-flow interactivity** — clarifying questions, plan confirmation, and the "this actually needs a custom integration" decision are per-run dialogues. - **Orchestrator that dispatches other skills** — the skill-orchestrates-skill default (see `skill-vs-agent`) keeps the entry point in skill form, like `ha-blueprint-scaffold` dispatching `ha-blueprint-author`. - Counter-dimension considered: the per-artifact generation could run as parallel agents, but the plan approval and the entity_id threading must stay visible in the user's context; skill wins. ## When this skill activates Use this skill when the user describes a **result** that likely needs more than one artifact, and should not have to know which authoring skill produces what. ## When NOT to activate - a single clear artifact (one automation, one h