Use this skill when the user asks to "create an automation", "make an automation", "set up an automation", "list automations", "edit an automation", "delete an automation", "trigger an automation", "enable or disable an automation", "automate my lights", "when X happens do Y", "turn off lights at sunset", "notify me when someone arrives", "run something on a schedule", or any task involving Home Assistant automation creation or management.
How this skill is triggered — by the user, by Claude, or both
Slash command
/homeassistant-manager:automation-managementThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Use the `homeassistant-manager` MCP server to create, update, and manage Home Assistant automations.
Use the homeassistant-manager MCP server to create, update, and manage Home Assistant automations.
When the user describes an automation in natural language, translate it into HA automation structure and call ha_create_automation.
Ask (if not already clear):
{
"alias": "Human-readable name",
"description": "What this does",
"mode": "single",
"trigger": [...],
"condition": [...],
"action": [...]
}
See references/trigger-types.md for trigger syntax.
See references/action-types.md for action syntax.
ha_list_automations — shows all automations with enabled/disabled stateha_get_automation — full config of a specific automationha_update_automation — modify any fieldha_toggle_automationha_trigger_automationha_delete_automation (always confirm first)trigger: [{ platform: "time", at: "23:00:00" }]
action: [{ service: "light.turn_off", target: { entity_id: "all" } }]
trigger: [{ platform: "state", entity_id: "binary_sensor.hallway_motion", to: "on" }]
action: [{ service: "light.turn_on", target: { entity_id: "light.hallway" } }]
trigger: [{ platform: "state", entity_id: "lock.front_door", to: "unlocked" }]
action: [{ service: "notify.mobile_app_iphone", data: { message: "Front door unlocked" } }]
trigger: [{ platform: "sun", event: "sunset", offset: "-00:30:00" }]
action: [{ service: "light.turn_on", target: { entity_id: "light.outdoor" }, data: { brightness_pct: 80 } }]
trigger: [{ platform: "numeric_state", entity_id: "sensor.temperature", above: 80 }]
action: [{ service: "notify.notify", data: { message: "Temperature too high: {{ trigger.to_state.state }}°F" } }]
mode: restart for state-based automations that should restart if triggered againmode: queued for sequential actions that shouldn't overlapha_trigger_automation before relying on the trigger{{ }} syntax for dynamic valuesnpx claudepluginhub pzharyuk/ai-claude-plugins --plugin homeassistant-managerCreates bite-sized, testable implementation plans from specs or requirements, with file structure and task decomposition. Activates before coding multi-step tasks.