Ha blueprint scaffold
Skill nolte/claude-home-assistant/skills/ha-blueprint-scaffold
Scaffolds a single Home Assistant blueprint (automation, script, or template domain) as a self-contained, spec-conformant YAML file — by gathering the intent, running a pre-flight, and dispatching the ha-blueprint-author agent for the draft-validate-iterate loop, then relaying its conformance report. Activate on phrasings like "scaffold a blueprint for X", "create an automation blueprint", "turn this automation into a blueprint", "draft a motion-light blueprint", "schreibe ein Blueprint für X", "erstelle ein Automations-Blueprint", "mach aus dieser Automation ein Blueprint". Do not activate for custom-integration scaffolding (ha-integration-scaffold), Lovelace cards (ha-lovelace-card-scaffold), integration services (ha-service-definition-add), or importing/deploying into a running HA instance.From its SKILL.md
npx -y skills add nolte/claude-home-assistant --skill ha-blueprint-scaffoldAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
7.4 KB, as published. Nobody here has run it
HA Blueprint Scaffold
Spec: spec/claude/ha-blueprint-scaffold/en.md (EN canonical) / spec/claude/ha-blueprint-scaffold/de.md (DE translation).
This skill is the entry point for creating a blueprint. It does not generate the YAML itself — it gathers parameters, runs a pre-flight, and dispatches the ha-blueprint-author agent, which owns the draft → validate → iterate loop and the conformance report against spec/ha/blueprint-patterns/en.md.
Why this is a skill, not an agent
- Orchestrator role (decisive): the procedure gathers intent interactively, runs the pre-flight, and then dispatches the
ha-blueprint-authoragent for the heavy authoring — perskill-vs-agent, the orchestrator in the hybrid pattern is always a skill. - Mid-flow interactivity: blueprint intent (domain, inputs, trigger shape) is elicited from the operator before any file exists; that dialogue lives in the main conversation.
- Counter-dimension considered: the YAML authoring itself is self-contained (agent bias) — which is exactly why it is delegated to the sibling agent instead of making this wrapper an agent.
When this skill activates
Use this skill when the user wants to create one Home Assistant blueprint (automation, script, or template) from a described intent — typically to package a reusable automation for sharing or for their own home.
When NOT to activate
- scaffolding a Python custom integration →
ha-integration-scaffold - scaffolding a Lovelace card →
ha-lovelace-card-scaffold - defining an integration service →
ha-service-definition-add - importing, deploying, or pushing a blueprint into a running HA instance → out of scope (generation only)
Hard rules
- Never generate the blueprint inline. The
ha-blueprint-authoragent is the sole generation path; this skill gathers inputs, pre-flights, dispatches, and relays. Do not rebuild the agent's loop here. - Intent is mandatory. Without a described intent there is no dispatch. Everything else may fall back to a documented default.
- Never overwrite an existing blueprint. If the resolved path already exists, abort with the path quoted. Collision is a user-disambiguation problem.
- Never silently default. When the user is silent on
domain,target_dir,author, orsource_url, use the documented defaults — but state every default in the dispatch and in the relayed report. - One blueprint, one domain, one run. No multi-blueprint batches, no Python, no live-HA import.
- Verify HA internals against the official docs. Don't reproduce HA API signatures, lifecycle hooks, conventions, or schemas from memory — when uncertain, consult the official docs before generating or relying on it: Developer docs
developers.home-assistant, architecture/blueprint/YAML docshome-assistant.io(seespec/ha/upstream-docs-verification/en.md).
Inputs
| Field | Required | Default | Notes |
|---|---|---|---|
intent | yes | — | What the blueprint should do, in prose |
domain | no | automation | One of automation, script, template |
target_dir | no | repo root | Where to write; an HA config tree triggers the blueprints/<domain>/<author>/ path derivation |
author | no | git user or local | Namespace folder + author key |
file_name | no | derived from name (snake_case) | The .yaml filename, per spec/ha/naming-conventions/en.md |
source_url | no | — | Canonical origin; set only when the blueprint is meant to be shared |
If the user is silent on any optional field, use the default but state it explicitly in the output.
Pre-flight (every run, in order — abort on first failure)
intentis present and non-empty. If not, ask for it; do not dispatch.target_direxists (or its parent is writable). If the path is unusable, abort and say why.- Resolve the target path. When
target_diris an HA config tree, deriveblueprints/<domain>/<author>/<file_name>.yaml; otherwise honor the caller's path. - The resolved blueprint file does not already exist. If it does, abort with the path quoted.
Workflow
1) Resolve and confirm
Print one paragraph stating: domain, resolved file path, author, whether source_url is set, and every default that was assumed. Wait for user confirmation.
2) Dispatch the agent
Dispatch the ha-blueprint-author agent, passing every gathered parameter (intent, domain, target_dir, author, file_name, source_url). The agent reads ha/blueprint-patterns, drafts the inputs/selectors/body, wires the !input → variables/trigger_variables bridge, validates offline, repairs, and returns a CONFORMANT / NEEDS-WORK report.
3) Relay the report
Surface the agent's report verbatim plus the relative path to the written file. Do not echo the full blueprint YAML unless the user asks. When the report is NEEDS-WORK, forward the agent's named caller follow-ups as the user's next decisions.
Boundaries
- The generative loop and all spec conformance →
ha-blueprint-authoragent - Blueprint authoring rules (schema, selectors, templating, modes, versioning) →
ha/blueprint-patterns - Custom-integration scaffold →
ha-integration-scaffold - Backward-compatible edits to an existing blueprint → no owning skill yet; edit manually against
spec/ha/blueprint-patterns/en.md