home-assistant-yaml

Featured

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, energy monitoring, Matter devices, automation debugging and traces, dashboard sections view, and trigger-based template entities.

AI & Automation 104 stars 3 forks Updated 6 days ago MIT

Install

View on GitHub

Quality Score: 88/100

Stars 20%
67
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
80
License 10%
100
Description 5%
100

Skill Content

# 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...

Details

Author
tonylofgren
Repository
tonylofgren/aurora-smart-home
Created
8 months ago
Last Updated
6 days ago
Language
Python
License
MIT

Integrates with

Bundled in these plugins

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Listed

ha-automation

Create or modify Home Assistant automations and scripts. Use when the user wants to automate behavior ("when X happens, do Y"), schedule something, or edit/fix an existing automation or script.

1 Updated today
LayerTM
AI & Automation Listed

ha-automation-author

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.

1 Updated 1 months ago
nolte
AI & Automation Listed

ha-automation-solution

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.

1 Updated 1 months ago
nolte