Help us improve
Share bugs, ideas, or general feedback.
From home-assistant
Fire a custom Home Assistant event. Use when the user wants to trigger automations that listen for custom event types, or test event-driven automations.
npx claudepluginhub cameri/claude-skills --plugin home-assistantHow this skill is triggered — by the user, by Claude, or both
Slash command
/home-assistant:fire-eventThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
<objective>
Guides technical evaluation of code review feedback: read fully, restate for understanding, verify against codebase, respond with reasoning or pushback before implementing.
Share bugs, ideas, or general feedback.
<quick_start>
/home-assistant:fire-event my_custom_event
/home-assistant:fire-event my_custom_event device=front_door action=opened
/home-assistant:fire-event call_service domain=light service=turn_off
</quick_start>
Load credentials before every call: ```bash source ~/.claude/channels/home-assistant/.env ``` If `.env` is missing or `HA_URL`/`HA_TOKEN` are not set, tell the user to run `/home-assistant:access` first. Parse `$ARGUMENTS`: - First arg: `` (required) — the event name (e.g. `my_custom_event`) - Remaining args: `key=value` pairs → event data payload (optional)If no additional args, send empty body {}.
httpie call with event data:
http --ignore-stdin -b POST "${HA_URL%/}/api/events/<event_type>" \
"Authorization: Bearer $HA_TOKEN" \
key="value" \
key2="value2"
httpie call with no data:
http --ignore-stdin -b POST "${HA_URL%/}/api/events/<event_type>" \
"Authorization: Bearer $HA_TOKEN"
Display result:
{"message": "Event <event_type> fired."} → show "Event fired: <event_type>"List active event types — fire-event list:
http --ignore-stdin -b GET "${HA_URL%/}/api/events" \
"Authorization: Bearer $HA_TOKEN"
Display as table: Event Type, Listener Count.
<success_criteria>
list subcommand shows all active event types
</success_criteria>