← ClaudeAtlas

home-assistant-yamllisted

Home Assistant YAML configuration and automation. The most common skill for general HA questions. Covers automations, blueprints, scripts, scenes, template sensors, Lovelace dashboards, Mushroom cards, packages, helpers, presence detection, voice Assist, calendar automation, Jinja2 templates, notification patterns, and energy monitoring.
tonylofgren/aurora-smart-home · ★ 85 · Data & Documents · score 78
Install: claude install-skill tonylofgren/aurora-smart-home
# Home Assistant Automation Reference skill for Home Assistant configuration and automation. ## Overview **Core principle:** Never generate YAML without understanding the user's intent. Automation vs blueprint, UI editor vs YAML files, and entity naming conventions must be clarified first. **Context:** This skill requires intent clarification before any YAML generation. Automations are specific to a user's setup; blueprints are reusable templates. The format (UI vs YAML) affects how entities are referenced. ## The Iron Law ``` CLARIFY INTENT BEFORE GENERATING ANY YAML USE MODERN SYNTAX: action: (not service:), triggers:/conditions:/actions: (plural) ``` Ask: Automation or Blueprint? Format: UI or YAML? Never assume. Never skip these questions. ## Official Reference Files (read before generating YAML) Before generating any automation YAML, read the relevant official reference file: | YAML element | Official reference | |---|---| | Actions (`action:`, `target:`, `data:`) | `references/actions-2026-official.md` | | Triggers (`triggers:`, `trigger:`) | `references/triggers-2026-official.md` | | Conditions (`conditions:`, `condition:`) | `references/conditions-2026-official.md` | These files capture the current official HA docs (snapshot 2026-05-30) and supersede the older `actions.md`, `conditions.md`, and `triggers-advanced.md` files for syntax questions. Read only the file(s) relevant to what the user is building. ## The Process ``` User request │ ▼ Ask: Au