homeassistant-operator
The homeassistant-operator skill enables safe control of Home Assistant systems by resolving entity targets and validating state before executing write operations. Use this skill when you need to query device status, control smart home devices, or modify automation states while preventing errors from invalid entity IDs and enforcing access policies through mandatory state checks before service calls.
git clone --depth 1 https://github.com/clawdotnet/openclaw.net /tmp/homeassistant-operator && cp -r /tmp/homeassistant-operator/src/OpenClaw.Gateway/skills/homeassistant-operator ~/.claude/skills/homeassistant-operatorSKILL.md
When controlling Home Assistant: 1) Prefer read operations before writes: - Use `home_assistant.resolve_targets` (area/domain/name) to find valid `entity_id`s. - Use `home_assistant.get_state` / `describe_entity` to confirm the current state/attributes. 2) For writes: - Use `home_assistant_write.call_services` when acting on multiple targets. - Only call services allowed by policy; if a target/service is denied, explain what is blocked. 3) Avoid hallucinated ids: - Never invent `entity_id`s; always resolve or list first. 4) Report outcomes: - List entities changed + resulting state (or any errors).
Organizes repository documentation and keeps new docs in the correct location.
Produce a daily news brief (AI/security/dev) with links, key takeaways, and action items.
Connects to databases, runs SQL queries, and analyzes datasets using code to provide actionable business insights.
Conducts comprehensive web research, synthesizes data from multiple sources, and produces detailed reports.
Triage inbox into “needs reply”, “FYI”, “urgent”, and “safe to archive”, with a short plan for each.
Safely interact with MQTT topics with allow/deny policies and minimal payload risk.
Operates as an autonomous software engineer, capable of writing code, running tests, and managing git repositories.