{"id":"2089b9fc-40bd-49d6-8dfc-290cabb2c762","entityType":"agent","slug":"clawhub-oomol-oo-home-assistant","name":"Home Assistant","canonicalUrl":"https://www.xpersona.co/agent/clawhub-oomol-oo-home-assistant","canonicalPath":"/agent/clawhub-oomol-oo-home-assistant","generatedAt":"2026-10-10T17:35:38.972Z","source":"CLAWHUB","claimStatus":"UNCLAIMED","verificationTier":"NONE","summary":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"medium","updatedAt":"2026-10-10T15:12:31.885Z","emptyReason":null},"description":"Home Assistant (home-assistant.io). Use this skill for ANY Home Assistant request — reading, creating, updating, and deleting data. Whenever a task involves Home Assistant, use this skill instead of calling the API directly.","descriptionLabel":"Source description","evidenceSummary":"Capability contract not published. No trust telemetry is available yet. 1.4K downloads reported by the source. Last updated 10/10/2026.","installCommand":"clawhub skill install s1790xw8jww1c6hgm8aqy9q25187t1rg:oo-home-assistant","sourceUrl":"https://clawhub.ai/oomol/oo-home-assistant","homepage":"https://clawhub.ai/oomol/skills/oo-home-assistant","primaryLinks":[{"label":"View on ClawHub","url":"https://clawhub.ai/oomol/oo-home-assistant","kind":"source"},{"label":"Homepage","url":"https://clawhub.ai/oomol/skills/oo-home-assistant","kind":"homepage"}],"safetyScore":84,"overallRank":62,"popularityScore":63,"trustScore":null,"claimedByName":null,"isOwner":false,"seoDescription":"Home Assistant technical dossier on Xpersona with agent coverage, OPENCLEW support, and live trust metadata."},"coverage":{"evidence":{"source":"public-profile","verified":false,"confidence":"medium","updatedAt":"2026-10-10T15:12:31.885Z","emptyReason":null},"protocols":[{"protocol":"OPENCLEW","label":"OpenClaw","status":"self-declared","notes":"Declared in the public agent profile."}],"capabilities":[],"verifiedCount":0,"selfDeclaredCount":1,"capabilityMatrix":{"rows":[{"key":"OPENCLEW","type":"protocol","support":"unknown","confidenceSource":"profile","notes":"Listed on profile"}],"flattenedTokens":"protocol:OPENCLEW|unknown|profile"}},"adoption":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"medium","updatedAt":"2026-10-10T15:12:31.885Z","emptyReason":null},"stars":null,"forks":null,"downloads":1366,"packageName":null,"latestVersion":"1.0.6","tractionLabel":"1.4K downloads"},"release":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"medium","updatedAt":"2026-10-10T15:12:31.825Z","emptyReason":null},"lastUpdatedAt":"2026-10-10T15:12:31.885Z","lastCrawledAt":"2026-10-10T15:12:31.825Z","lastIndexedAt":null,"nextCrawlAt":"2026-10-11T15:12:31.825Z","lastVerifiedAt":null,"highlights":[{"version":"1.0.6","createdAt":"2026-09-20T03:13:13.415Z","changelog":"- Operates Home Assistant through the OOMOL `home_assistant` connector using the `oo` CLI, with credentials injected server-side. - Provides read access to instance config, entity states, services, events, registries, history, logbook, calendars, templates, and related items. - Supports controlling entities through service calls, firing events, and executing Home Assistant script sequences. - Includes admin-level configuration actions for validating, fetching, saving, and deleting UI-editable automations, scenes, and scripts. - Documents safety expectations for read, write, and destructive actions, including explicit confirmation before state-changing operations. Source: `oomol-lab/skills@792ad44`","fileCount":3,"zipByteSize":4193},{"version":"1.0.5","createdAt":"2026-09-15T05:32:58.262Z","changelog":"- Operate Home Assistant through the OOMOL-connected `oo` CLI without handling raw credentials. - Inspect live action schemas before submitting requests. - Read entity states, history, logs, registries, calendars, services, events, and configuration. - Control devices, fire events, execute scripts, render templates, and validate configurations. - Create, update, fetch, and delete UI-managed automations, scenes, and scripts with explicit safety confirmations. Source: `oomol-lab/skills@75bac03`","fileCount":3,"zipByteSize":4333},{"version":"1.0.3","createdAt":"2026-08-11T08:10:10.389Z","changelog":"- Operate Home Assistant through the OOMOL-connected `oo` CLI, without handling raw credentials directly. - Inspect live action schemas before sending payloads, so requests match the authoritative connector contract. - Run Home Assistant reads for states, history, logbook entries, registries, services, calendars, events, templates, and configs. - Perform controlled writes for services, scripts, automations, and scenes, with destructive actions clearly separated and gated. - Validate and check Home Assistant configuration before storing changes, reducing bad automations and broken config. - Use one skill for the full Home Assistant workflow: discovery, diagnostics, control, and config management. Source: `oomol-lab/skills@46cfb3e`","fileCount":3,"zipByteSize":4138},{"version":"1.0.2","createdAt":"2026-06-16T09:57:49.391Z","changelog":"- Provides Home Assistant automation support through the OOMOL `home_assistant` connector and `oo` CLI. - Runs authenticated actions without exposing raw Home Assistant tokens to the assistant. - Supports reading instance config, entity states, known events, available services, and rendered templates. - Supports state-changing operations through service calls and custom event firing, with confirmation required before writes. - Guides setup only when needed for missing CLI, auth, connection, credential, scope, or billing errors. Source: `oomol-lab/skills@4597539`","fileCount":3,"zipByteSize":3418},{"version":"1.0.1","createdAt":"2026-06-09T10:15:13.507Z","changelog":"- Operates Home Assistant through the OOMOL `home_assistant` connector without exposing raw credentials. - Supports reading instance configuration, entity states, event types, and available services. - Enables entity control through Home Assistant service calls such as `light.turn_on` and `switch.turn_off`. - Can fire Home Assistant events with optional event data. - Renders Home Assistant templates against the connected instance. - Includes safety guidance for confirming state-changing actions and using live connector schemas before requests. Source: `oomol-lab/skills@146ef20`","fileCount":3,"zipByteSize":3321},{"version":"1.0.0","createdAt":"2026-06-03T16:00:03.656Z","changelog":"- Connects Codex to Home Assistant through the OOMOL `home_assistant` connector, with credentials handled server-side. - Provides safe read actions for inspecting instance configuration, entity states, event types, and available services. - Supports targeted entity lookup via `get_state` and full environment discovery via `list_states`, `list_events`, and `list_services`. - Enables Home Assistant automation workflows by calling services, firing events, and rendering templates against the connected instance. - Documents a schema-first workflow using `oo connector schema` before running actions, plus clear safety guidance for state-changing operations.","fileCount":11,"zipByteSize":7357}]},"execution":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"low","updatedAt":null,"emptyReason":"No published capability contract is available yet."},"installCommand":"clawhub skill install s1790xw8jww1c6hgm8aqy9q25187t1rg:oo-home-assistant","setupComplexity":"low","setupSteps":["Install using `clawhub skill install s1790xw8jww1c6hgm8aqy9q25187t1rg:oo-home-assistant` in an isolated environment before connecting it to live workloads.","No published capability contract is available yet, so validate auth and request/response behavior manually.","Review the upstream CLAWHUB listing at https://clawhub.ai/oomol/oo-home-assistant before using production credentials."],"contract":{"contractStatus":"missing","authModes":[],"requires":[],"forbidden":[],"supportsMcp":false,"supportsA2a":false,"supportsStreaming":false,"inputSchemaRef":null,"outputSchemaRef":null,"dataRegion":null,"contractUpdatedAt":null,"sourceUpdatedAt":null,"freshnessSeconds":null},"invocationGuide":{"preferredApi":{"snapshotUrl":"https://www.xpersona.co/api/v1/agents/clawhub-oomol-oo-home-assistant/snapshot","contractUrl":"https://www.xpersona.co/api/v1/agents/clawhub-oomol-oo-home-assistant/contract","trustUrl":"https://www.xpersona.co/api/v1/agents/clawhub-oomol-oo-home-assistant/trust"},"curlExamples":["curl -s \"https://www.xpersona.co/api/v1/agents/clawhub-oomol-oo-home-assistant/snapshot\"","curl -s \"https://www.xpersona.co/api/v1/agents/clawhub-oomol-oo-home-assistant/contract\"","curl -s \"https://www.xpersona.co/api/v1/agents/clawhub-oomol-oo-home-assistant/trust\""],"jsonRequestTemplate":{"query":"summarize this repo","constraints":{"maxLatencyMs":2000,"protocolPreference":["OPENCLEW"]}},"jsonResponseTemplate":{"ok":true,"result":{"summary":"...","confidence":0.9},"meta":{"source":"CLAWHUB","generatedAt":"2026-10-10T17:35:38.971Z"}},"retryPolicy":{"maxAttempts":3,"backoffMs":[500,1500,3500],"retryableConditions":["HTTP_429","HTTP_503","NETWORK_TIMEOUT"]}},"endpoints":{"dossierUrl":"https://www.xpersona.co/api/v1/agents/clawhub-oomol-oo-home-assistant/dossier","snapshotUrl":"https://www.xpersona.co/api/v1/agents/clawhub-oomol-oo-home-assistant/snapshot","contractUrl":"https://www.xpersona.co/api/v1/agents/clawhub-oomol-oo-home-assistant/contract","trustUrl":"https://www.xpersona.co/api/v1/agents/clawhub-oomol-oo-home-assistant/trust"}},"reliability":{"evidence":{"source":"runtime-metrics","verified":false,"confidence":"low","updatedAt":null,"emptyReason":"No trust, reliability, or runtime telemetry is available."},"trust":{"status":"unavailable","handshakeStatus":"UNKNOWN","verificationFreshnessHours":null,"reputationScore":null,"p95LatencyMs":null,"successRate30d":null,"fallbackRate":null,"attempts30d":null,"trustUpdatedAt":null,"trustConfidence":"unknown","sourceUpdatedAt":null,"freshnessSeconds":null},"decisionGuardrails":{"doNotUseIf":["Contract metadata is missing or unavailable for deterministic execution."],"safeUseWhen":[],"riskFlags":["missing_or_unavailable_contract","trust_data_unavailable","schema_references_missing"],"operationalConfidence":"low"},"executionMetrics":{"observedLatencyMsP50":null,"observedLatencyMsP95":null,"estimatedCostUsd":null,"uptime30d":null,"rateLimitRpm":null,"rateLimitBurst":null,"lastVerifiedAt":null,"verificationSource":null},"runtimeMetrics":{"successRate":null,"avgLatencyMs":null,"avgCostUsd":null,"hallucinationRate":null,"retryRate":null,"disputeRate":null,"p50Latency":null,"p95Latency":null,"lastUpdated":null}},"benchmarks":{"evidence":{"source":"no-benchmark-data","verified":false,"confidence":"low","updatedAt":null,"emptyReason":"No benchmark suites or observed failure patterns are available."},"suites":[],"failurePatterns":[]},"artifacts":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"medium","updatedAt":"2026-10-10T15:12:31.885Z","emptyReason":null},"readme":"Skill: Home Assistant\n\nOwner: oomol\n\nSummary: Home Assistant (home-assistant.io). Use this skill for ANY Home Assistant request — reading, creating, updating, and deleting data. Whenever a task involves Home Assistant, use this skill instead of calling the API directly.\n\nTags: latest:1.0.6\n\nVersion history:\n\nv1.0.6 | 2026-09-20T03:13:13.415Z | user\n\n- Operates Home Assistant through the OOMOL `home_assistant` connector using the `oo` CLI, with credentials injected server-side.\n- Provides read access to instance config, entity states, services, events, registries, history, logbook, calendars, templates, and related items.\n- Supports controlling entities through service calls, firing events, and executing Home Assistant script sequences.\n- Includes admin-level configuration actions for validating, fetching, saving, and deleting UI-editable automations, scenes, and scripts.\n- Documents safety expectations for read, write, and destructive actions, including explicit confirmation before state-changing operations.\n\nSource: `oomol-lab/skills@792ad44`\n\nv1.0.5 | 2026-09-15T05:32:58.262Z | user\n\n- Operate Home Assistant through the OOMOL-connected `oo` CLI without handling raw credentials.\n- Inspect live action schemas before submitting requests.\n- Read entity states, history, logs, registries, calendars, services, events, and configuration.\n- Control devices, fire events, execute scripts, render templates, and validate configurations.\n- Create, update, fetch, and delete UI-managed automations, scenes, and scripts with explicit safety confirmations.\n\nSource: `oomol-lab/skills@75bac03`\n\nv1.0.3 | 2026-08-11T08:10:10.389Z | user\n\n- Operate Home Assistant through the OOMOL-connected `oo` CLI, without handling raw credentials directly.\n- Inspect live action schemas before sending payloads, so requests match the authoritative connector contract.\n- Run Home Assistant reads for states, history, logbook entries, registries, services, calendars, events, templates, and configs.\n- Perform controlled writes for services, scripts, automations, and scenes, with destructive actions clearly separated and gated.\n- Validate and check Home Assistant configuration before storing changes, reducing bad automations and broken config.\n- Use one skill for the full Home Assistant workflow: discovery, diagnostics, control, and config management.\n\nSource: `oomol-lab/skills@46cfb3e`\n\nv1.0.2 | 2026-06-16T09:57:49.391Z | user\n\n- Provides Home Assistant automation support through the OOMOL `home_assistant` connector and `oo` CLI.\n- Runs authenticated actions without exposing raw Home Assistant tokens to the assistant.\n- Supports reading instance config, entity states, known events, available services, and rendered templates.\n- Supports state-changing operations through service calls and custom event firing, with confirmation required before writes.\n- Guides setup only when needed for missing CLI, auth, connection, credential, scope, or billing errors.\n\nSource: `oomol-lab/skills@4597539`\n\nv1.0.1 | 2026-06-09T10:15:13.507Z | user\n\n- Operates Home Assistant through the OOMOL `home_assistant` connector without exposing raw credentials.\n- Supports reading instance configuration, entity states, event types, and available services.\n- Enables entity control through Home Assistant service calls such as `light.turn_on` and `switch.turn_off`.\n- Can fire Home Assistant events with optional event data.\n- Renders Home Assistant templates against the connected instance.\n- Includes safety guidance for confirming state-changing actions and using live connector schemas before requests.\n\nSource: `oomol-lab/skills@146ef20`\n\nv1.0.0 | 2026-06-03T16:00:03.656Z | user\n\n- Connects Codex to Home Assistant through the OOMOL `home_assistant` connector, with credentials handled server-side.\n- Provides safe read actions for inspecting instance configuration, entity states, event types, and available services.\n- Supports targeted entity lookup via `get_state` and full environment discovery via `list_states`, `list_events`, and `list_services`.\n- Enables Home Assistant automation workflows by calling services, firing events, and rendering templates against the connected instance.\n- Documents a schema-first workflow using `oo connector schema` before running actions, plus clear safety guidance for state-changing operations.\n\nArchive index:\n\nArchive v1.0.6: 3 files, 4193 bytes\n\nFiles: skill-card.md (2239b), SKILL.md (7816b), _meta.json (136b)\n\nFile v1.0.6:SKILL.md\n\n---\nname: oo-home-assistant\ndescription: \"Home Assistant (home-assistant.io). Use this skill for ANY Home Assistant request — reading, creating, updating, and deleting data. Whenever a task involves Home Assistant, use this skill instead of calling the API directly.\"\nallowed-tools: [Bash(oo *)]\nmetadata:\n title: \"Home Assistant\"\n author: \"OOMOL\"\n version: \"1.0.6\"\n services: [\"home_assistant\"]\n icon: \"https://static.oomol.com/logo/third-party/home_assistant.svg\"\n---\n\n# Home Assistant\n\nOperate **Home Assistant** through your OOMOL-connected account. This skill calls the `home_assistant` connector with the [oo CLI](https://github.com/oomol-lab/oo-cli); OOMOL injects credentials server-side, so you never handle raw tokens.\n\n## Running an action\n\nAssume the user has already installed the oo CLI, signed in, and connected Home Assistant. **Do not run `oo auth login` or open the connection URL proactively — just run the action.** Fall back to [First-time setup](#first-time-setup) only when a command actually fails with an auth or connection error.\n\n**1. Inspect the contract** to get the authoritative input/output schema before building a payload:\n\n```bash\noo connector schema \"home_assistant\" --action \"\"\n```\n\n**2. Run the action** with a JSON payload that matches the input schema:\n\n```bash\noo connector run \"home_assistant\" --action \"\" --data '' --json\n```\n\n- `--data` takes a JSON object string or `@path/to/file.json`; omit it to send `{}`.\n- The response is `{ \"data\": ..., \"meta\": { \"executionId\": \"...\" } }`; the execution id lives under `meta.executionId`.\n\nEach action is listed below with a one-line description; actions that change state carry a `[write]` or `[destructive]` tag. Before constructing `--data`, fetch the action's live schema with `oo connector schema` to get its authoritative input fields.\n\n## Available actions\n\n- `call_service` — Call a Home Assistant service to control entities, such as light.turn_on or switch.turn_off. [destructive]\n- `check_config` — Ask Home Assistant to validate its own configuration files and report errors and warnings. Requires an admin access token.\n- `delete_automation_config` — Delete one Home Assistant automation. Requires an admin access token, and only covers entries stored in the Home Assistant UI-editable config; entries defined in other YAML files return not found. [destructive]\n- `delete_scene_config` — Delete one Home Assistant scene. Requires an admin access token, and only covers entries stored in the Home Assistant UI-editable config; entries defined in other YAML files return not found. [destructive]\n- `delete_script_config` — Delete one Home Assistant script. Requires an admin access token, and only covers entries stored in the Home Assistant UI-editable config; entries defined in other YAML files return not found. [destructive]\n- `execute_script` — Run a Home Assistant script sequence containing service calls, delays, and conditions. [write]\n- `fire_event` — Fire one Home Assistant event with optional event data. [destructive]\n- `get_automation_config` — Fetch the stored configuration for one Home Assistant automation. Requires an admin access token, and only covers entries stored in the Home Assistant UI-editable config; entries defined in other YAML files return not found.\n- `get_config` — Fetch the Home Assistant instance configuration.\n- `get_error_log` — Fetch the Home Assistant error log for the current session as plain text. Home Assistant serves this only when the instance runs with file logging enabled, so it can report not found on an otherwise healthy instance.\n- `get_history` — Fetch recorded state history for one or more Home Assistant entities over a time period, for answering questions about how a value changed.\n- `get_logbook` — Fetch the Home Assistant logbook: the human-readable timeline of what happened and what triggered it, for diagnosing why something changed.\n- `get_registries` — List Home Assistant entity, device, area, floor, and label registries over the WebSocket API.\n- `get_scene_config` — Fetch the stored configuration for one Home Assistant scene. Requires an admin access token, and only covers entries stored in the Home Assistant UI-editable config; entries defined in other YAML files return not found.\n- `get_script_config` — Fetch the stored configuration for one Home Assistant script. Requires an admin access token, and only covers entries stored in the Home Assistant UI-editable config; entries defined in other YAML files return not found.\n- `get_state` — Fetch the current state for one Home Assistant entity.\n- `list_calendar_events` — List the events on one Home Assistant calendar between a start and end time.\n- `list_calendars` — List the calendar entities exposed by Home Assistant.\n- `list_device_automations` — List the triggers, conditions, and actions supported by one Home Assistant device.\n- `list_events` — List Home Assistant event types currently known by the instance.\n- `list_services` — List Home Assistant service domains and their available services.\n- `list_states` — List all current Home Assistant entity states.\n- `render_template` — Render a Home Assistant template against the connected instance.\n- `save_automation_config` — Create or replace one Home Assistant automation. Posting to an unused id creates the automation. Requires an admin access token, and only covers entries stored in the Home Assistant UI-editable config; entries defined in other YAML files return not found. [destructive]\n- `save_scene_config` — Create or replace one Home Assistant scene. Posting to an unused id creates the scene. Requires an admin access token, and only covers entries stored in the Home Assistant UI-editable config; entries defined in other YAML files return not found. [destructive]\n- `save_script_config` — Create or replace one Home Assistant script. Posting to an unused key creates the script. Requires an admin access token, and only covers entries stored in the Home Assistant UI-editable config; entries defined in other YAML files return not found. [destructive]\n- `search_related` — Find Home Assistant items related to an entity, device, area, automation, or configuration entry.\n- `validate_config` — Validate Home Assistant trigger, condition, and action configurations before storing an automation.\n\n## Safety\n\n- Untagged actions are reads (get / list / search) — safe to run directly.\n- **Actions tagged `[write]` change Home Assistant state — confirm the exact payload and effect with the user before running.**\n- **Actions tagged `[destructive]` remove or overwrite data — always confirm the target and get explicit approval first.**\n\n## First-time setup\n\nThese are **one-time** steps — do not repeat them on every call. Run a step only when a command fails for the matching reason.\n\n- **`oo: command not found`** — install the oo CLI (other platforms: ):\n\n ```bash\n curl -fsSL https://cli.oomol.com/install.sh | bash # macOS / Linux\n ```\n\n ```powershell\n irm https://cli.oomol.com/install.ps1 | iex # Windows PowerShell\n ```\n\n- **Not signed in / authentication error** — sign in to your OOMOL account once:\n\n ```bash\n oo auth login\n ```\n\n- **`scope_missing` / `credential_expired` / `app_not_ready` / `app_not_found`** — Home Assistant is not connected, or the connection expired or lacks a scope. Connect once (auth type: API key) at:\n\n ```text\n https://console.oomol.com/app-connections?provider=home_assistant\n ```\n\n- **HTTP 402 / `OOMOL_INSUFFICIENT_CREDIT`** — billing stop. Recharge at `https://console.oomol.com/billing/token-recharge` before retrying.\n\n## Resources\n\n- Home Assistant homepage: https://www.home-assistant.io\n\nFile v1.0.6:_meta.json\n\n{\n \"ownerId\": \"kn7fzg3sx4xr7ssnc2yyhpndx187yacb\",\n \"slug\": \"oo-home-assistant\",\n \"version\": \"1.0.6\",\n \"publishedAt\": 1789873993415\n}\n\nFile v1.0.6:skill-card.md\n\n## Description:\n\nHome Assistant (home-assistant.io). Use this skill for Home Assistant requests involving reading, creating, updating, and deleting data through the OOMOL-connected Home Assistant connector.\n\nThis skill is ready for commercial/non-commercial use.\n\n## Publisher:\n\n[oomol](https://clawhub.ai/user/oomol)\n\n### License/Terms of Use:\n\nMIT-0\n\n## Use Case:\n\nExternal users and developers use this skill to inspect and operate a connected Home Assistant instance through the OOMOL `home_assistant` connector. It supports reading entity state and configuration, running service calls and scripts, firing events, and managing UI-editable automations, scenes, and scripts.\n\n### Deployment Geography for Use:\n\nGlobal\n\n## Known Risks and Mitigations:\n\nRisk: The skill can control Home Assistant devices and make state-changing or destructive configuration changes.\n\nMitigation: Require explicit approval for write and destructive actions, confirm the exact target and payload, and connect Home Assistant with the minimum scopes needed.\n\nRisk: Fallback setup includes remote installer scripts that may be executed directly in a shell.\n\nMitigation: Prefer installing the oo CLI through a verified package or reviewed installer before using the skill.\n\n## Reference(s):\n\n- [Home Assistant homepage](https://www.home-assistant.io)\n- [oo CLI](https://github.com/oomol-lab/oo-cli)\n- [oo CLI install guide](https://cli.oomol.com/install-guide.md)\n- [ClawHub skill page](https://clawhub.ai/oomol/skills/oo-home-assistant)\n- [OOMOL publisher profile](https://clawhub.ai/user/oomol)\n\n## Skill Output:\n\n**Output Type(s):** [Shell commands, Configuration, Guidance, Text]\n\n**Output Format:** [Markdown with inline shell commands and JSON payload examples]\n\n**Output Parameters:** [1D]\n\n**Other Properties Related to Output:** [Uses live connector schemas before constructing action payloads.]\n\n## Skill Version(s):\n\n1.0.6 (source: server release metadata and SKILL.md frontmatter)\n\n## Ethical Considerations:\n\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment.\n\nArchive v1.0.5: 3 files, 4333 bytes\n\nFiles: skill-card.md (2666b), SKILL.md (7762b), _meta.json (136b)\n\nFile v1.0.5:SKILL.md\n\n---\nname: oo-home-assistant\ndescription: \"Home Assistant (home-assistant.io). Use this skill for ANY Home Assistant request — reading, creating, updating, and deleting data. Whenever a task involves Home Assistant, use this skill instead of calling the API directly.\"\nallowed-tools: [Bash(oo *)]\nmetadata:\n title: \"Home Assistant\"\n author: \"OOMOL\"\n version: \"1.0.5\"\n services: [\"home_assistant\"]\n icon: \"https://static.oomol.com/logo/third-party/home_assistant.svg\"\n---\n\n# Home Assistant\n\nOperate **Home Assistant** through your OOMOL-connected account. This skill calls the `home_assistant` connector with the [oo CLI](https://github.com/oomol-lab/oo-cli); OOMOL injects credentials server-side, so you never handle raw tokens.\n\n## Running an action\n\nAssume the user has already installed the oo CLI, signed in, and connected Home Assistant. **Do not run `oo auth login` or open the connection URL proactively — just run the action.** Fall back to [First-time setup](#first-time-setup) only when a command actually fails with an auth or connection error.\n\n**1. Inspect the contract** to get the authoritative input/output schema before building a payload:\n\n```bash\noo connector schema \"home_assistant\" --action \"\"\n```\n\n**2. Run the action** with a JSON payload that matches the input schema:\n\n```bash\noo connector run \"home_assistant\" --action \"\" --data '' --json\n```\n\n- `--data` takes a JSON object string or `@path/to/file.json`; omit it to send `{}`.\n- The response is `{ \"data\": ..., \"meta\": { \"executionId\": \"...\" } }`; the execution id lives under `meta.executionId`.\n\nEach action is listed below with a one-line description; actions that change state carry a `[write]` or `[destructive]` tag. Before constructing `--data`, fetch the action's live schema with `oo connector schema` to get its authoritative input fields.\n\n## Available actions\n\n- `call_service` — Call a Home Assistant service to control entities, such as light.turn_on or switch.turn_off.\n- `check_config` — Ask Home Assistant to validate its own configuration files and report errors and warnings. Requires an admin access token.\n- `delete_automation_config` — Delete one Home Assistant automation. Requires an admin access token, and only covers entries stored in the Home Assistant UI-editable config; entries defined in other YAML files return not found. [destructive]\n- `delete_scene_config` — Delete one Home Assistant scene. Requires an admin access token, and only covers entries stored in the Home Assistant UI-editable config; entries defined in other YAML files return not found. [destructive]\n- `delete_script_config` — Delete one Home Assistant script. Requires an admin access token, and only covers entries stored in the Home Assistant UI-editable config; entries defined in other YAML files return not found. [destructive]\n- `execute_script` — Run a Home Assistant script sequence containing service calls, delays, and conditions.\n- `fire_event` — Fire one Home Assistant event with optional event data.\n- `get_automation_config` — Fetch the stored configuration for one Home Assistant automation. Requires an admin access token, and only covers entries stored in the Home Assistant UI-editable config; entries defined in other YAML files return not found.\n- `get_config` — Fetch the Home Assistant instance configuration.\n- `get_error_log` — Fetch the Home Assistant error log for the current session as plain text. Home Assistant serves this only when the instance runs with file logging enabled, so it can report not found on an otherwise healthy instance.\n- `get_history` — Fetch recorded state history for one or more Home Assistant entities over a time period, for answering questions about how a value changed.\n- `get_logbook` — Fetch the Home Assistant logbook: the human-readable timeline of what happened and what triggered it, for diagnosing why something changed.\n- `get_registries` — List Home Assistant entity, device, area, floor, and label registries over the WebSocket API.\n- `get_scene_config` — Fetch the stored configuration for one Home Assistant scene. Requires an admin access token, and only covers entries stored in the Home Assistant UI-editable config; entries defined in other YAML files return not found.\n- `get_script_config` — Fetch the stored configuration for one Home Assistant script. Requires an admin access token, and only covers entries stored in the Home Assistant UI-editable config; entries defined in other YAML files return not found.\n- `get_state` — Fetch the current state for one Home Assistant entity.\n- `list_calendar_events` — List the events on one Home Assistant calendar between a start and end time.\n- `list_calendars` — List the calendar entities exposed by Home Assistant.\n- `list_device_automations` — List the triggers, conditions, and actions supported by one Home Assistant device.\n- `list_events` — List Home Assistant event types currently known by the instance.\n- `list_services` — List Home Assistant service domains and their available services.\n- `list_states` — List all current Home Assistant entity states.\n- `render_template` — Render a Home Assistant template against the connected instance.\n- `save_automation_config` — Create or replace one Home Assistant automation. Posting to an unused id creates the automation. Requires an admin access token, and only covers entries stored in the Home Assistant UI-editable config; entries defined in other YAML files return not found. [write]\n- `save_scene_config` — Create or replace one Home Assistant scene. Posting to an unused id creates the scene. Requires an admin access token, and only covers entries stored in the Home Assistant UI-editable config; entries defined in other YAML files return not found. [write]\n- `save_script_config` — Create or replace one Home Assistant script. Posting to an unused key creates the script. Requires an admin access token, and only covers entries stored in the Home Assistant UI-editable config; entries defined in other YAML files return not found. [write]\n- `search_related` — Find Home Assistant items related to an entity, device, area, automation, or configuration entry.\n- `validate_config` — Validate Home Assistant trigger, condition, and action configurations before storing an automation.\n\n## Safety\n\n- Untagged actions are reads (get / list / search) — safe to run directly.\n- **Actions tagged `[write]` change Home Assistant state — confirm the exact payload and effect with the user before running.**\n- **Actions tagged `[destructive]` remove or overwrite data — always confirm the target and get explicit approval first.**\n\n## First-time setup\n\nThese are **one-time** steps — do not repeat them on every call. Run a step only when a command fails for the matching reason.\n\n- **`oo: command not found`** — install the oo CLI (other platforms: ):\n\n ```bash\n curl -fsSL https://cli.oomol.com/install.sh | bash # macOS / Linux\n ```\n\n ```powershell\n irm https://cli.oomol.com/install.ps1 | iex # Windows PowerShell\n ```\n\n- **Not signed in / authentication error** — sign in to your OOMOL account once:\n\n ```bash\n oo auth login\n ```\n\n- **`scope_missing` / `credential_expired` / `app_not_ready` / `app_not_found`** — Home Assistant is not connected, or the connection expired or lacks a scope. Connect once (auth type: API key) at:\n\n ```text\n https://console.oomol.com/app-connections?provider=home_assistant\n ```\n\n- **HTTP 402 / `OOMOL_INSUFFICIENT_CREDIT`** — billing stop. Recharge at `https://console.oomol.com/billing/token-recharge` before retrying.\n\n## Resources\n\n- Home Assistant homepage: https://www.home-assistant.io\n\nFile v1.0.5:_meta.json\n\n{\n \"ownerId\": \"kn7fzg3sx4xr7ssnc2yyhpndx187yacb\",\n \"slug\": \"oo-home-assistant\",\n \"version\": \"1.0.5\",\n \"publishedAt\": 1789450378262\n}\n\nFile v1.0.5:skill-card.md\n\n## Description:\n\nHome Assistant (home-assistant.io). Use this skill for ANY Home Assistant request: reading, creating, updating, and deleting data through the OOMOL-connected Home Assistant connector.\n\nThis skill is ready for commercial/non-commercial use.\n\n## Publisher:\n\n[oomol](https://clawhub.ai/user/oomol)\n\n### License/Terms of Use:\n\nMIT-0\n\n## Use Case:\n\nExternal users and developers use this skill to inspect Home Assistant schemas, read states and logs, and control or configure connected Home Assistant entities through the oo CLI.\n\n### Deployment Geography for Use:\n\nGlobal\n\n## Known Risks and Mitigations:\n\nRisk: State-changing Home Assistant actions can affect devices, scripts, automations, services, events, or configuration.\n\nMitigation: Confirm the exact payload and expected effect before call_service, execute_script, fire_event, write, or destructive actions, especially for locks, alarms, climate, doors, appliances, and broad automation events.\n\nRisk: Remote installer commands pipe downloaded scripts directly into bash or PowerShell.\n\nMitigation: Avoid running the curl-to-bash or PowerShell iex installer automatically; prefer a verified and pinned installation method for the oo CLI.\n\nRisk: Some configuration actions require admin access and only cover UI-managed Home Assistant entries.\n\nMitigation: Inspect the live action schema before submitting requests, verify administrative scope, and confirm the target automation, scene, or script before creating, replacing, or deleting it.\n\n## Reference(s):\n\n- [ClawHub Skill Page](https://clawhub.ai/oomol/skills/oo-home-assistant)\n- [OOMOL Publisher Profile](https://clawhub.ai/user/oomol)\n- [oo CLI](https://github.com/oomol-lab/oo-cli)\n- [Home Assistant Homepage](https://www.home-assistant.io)\n- [oo CLI Install Guide](https://cli.oomol.com/install-guide.md)\n- [Home Assistant Connection Settings](https://console.oomol.com/app-connections?provider=home_assistant)\n\n## Skill Output:\n\n**Output Type(s):** [Text, Markdown, Shell commands, Configuration, Guidance]\n\n**Output Format:** [Markdown with inline shell commands and JSON payload examples]\n\n**Output Parameters:** [1D]\n\n**Other Properties Related to Output:** [May execute oo CLI commands against the user's connected Home Assistant account when the hosting agent has permission.]\n\n## Skill Version(s):\n\n1.0.5 (source: skill frontmatter and server release metadata)\n\n## Ethical Considerations:\n\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment.\n\nArchive v1.0.3: 3 files, 4138 bytes\n\nFiles: skill-card.md (2231b), SKILL.md (7762b), _meta.json (136b)\n\nFile v1.0.3:SKILL.md\n\n---\nname: oo-home-assistant\ndescription: \"Home Assistant (home-assistant.io). Use this skill for ANY Home Assistant request — reading, creating, updating, and deleting data. Whenever a task involves Home Assistant, use this skill instead of calling the API directly.\"\nallowed-tools: [Bash(oo *)]\nmetadata:\n title: \"Home Assistant\"\n author: \"OOMOL\"\n version: \"1.0.3\"\n services: [\"home_assistant\"]\n icon: \"https://static.oomol.com/logo/third-party/home_assistant.svg\"\n---\n\n# Home Assistant\n\nOperate **Home Assistant** through your OOMOL-connected account. This skill calls the `home_assistant` connector with the [oo CLI](https://github.com/oomol-lab/oo-cli); OOMOL injects credentials server-side, so you never handle raw tokens.\n\n## Running an action\n\nAssume the user has already installed the oo CLI, signed in, and connected Home Assistant. **Do not run `oo auth login` or open the connection URL proactively — just run the action.** Fall back to [First-time setup](#first-time-setup) only when a command actually fails with an auth or connection error.\n\n**1. Inspect the contract** to get the authoritative input/output schema before building a payload:\n\n```bash\noo connector schema \"home_assistant\" --action \"\"\n```\n\n**2. Run the action** with a JSON payload that matches the input schema:\n\n```bash\noo connector run \"home_assistant\" --action \"\" --data '' --json\n```\n\n- `--data` takes a JSON object string or `@path/to/file.json`; omit it to send `{}`.\n- The response is `{ \"data\": ..., \"meta\": { \"executionId\": \"...\" } }`; the execution id lives under `meta.executionId`.\n\nEach action is listed below with a one-line description; actions that change state carry a `[write]` or `[destructive]` tag. Before constructing `--data`, fetch the action's live schema with `oo connector schema` to get its authoritative input fields.\n\n## Available actions\n\n- `call_service` — Call a Home Assistant service to control entities, such as light.turn_on or switch.turn_off.\n- `check_config` — Ask Home Assistant to validate its own configuration files and report errors and warnings. Requires an admin access token.\n- `delete_automation_config` — Delete one Home Assistant automation. Requires an admin access token, and only covers entries stored in the Home Assistant UI-editable config; entries defined in other YAML files return not found. [destructive]\n- `delete_scene_config` — Delete one Home Assistant scene. Requires an admin access token, and only covers entries stored in the Home Assistant UI-editable config; entries defined in other YAML files return not found. [destructive]\n- `delete_script_config` — Delete one Home Assistant script. Requires an admin access token, and only covers entries stored in the Home Assistant UI-editable config; entries defined in other YAML files return not found. [destructive]\n- `execute_script` — Run a Home Assistant script sequence containing service calls, delays, and conditions.\n- `fire_event` — Fire one Home Assistant event with optional event data.\n- `get_automation_config` — Fetch the stored configuration for one Home Assistant automation. Requires an admin access token, and only covers entries stored in the Home Assistant UI-editable config; entries defined in other YAML files return not found.\n- `get_config` — Fetch the Home Assistant instance configuration.\n- `get_error_log` — Fetch the Home Assistant error log for the current session as plain text. Home Assistant serves this only when the instance runs with file logging enabled, so it can report not found on an otherwise healthy instance.\n- `get_history` — Fetch recorded state history for one or more Home Assistant entities over a time period, for answering questions about how a value changed.\n- `get_logbook` — Fetch the Home Assistant logbook: the human-readable timeline of what happened and what triggered it, for diagnosing why something changed.\n- `get_registries` — List Home Assistant entity, device, area, floor, and label registries over the WebSocket API.\n- `get_scene_config` — Fetch the stored configuration for one Home Assistant scene. Requires an admin access token, and only covers entries stored in the Home Assistant UI-editable config; entries defined in other YAML files return not found.\n- `get_script_config` — Fetch the stored configuration for one Home Assistant script. Requires an admin access token, and only covers entries stored in the Home Assistant UI-editable config; entries defined in other YAML files return not found.\n- `get_state` — Fetch the current state for one Home Assistant entity.\n- `list_calendar_events` — List the events on one Home Assistant calendar between a start and end time.\n- `list_calendars` — List the calendar entities exposed by Home Assistant.\n- `list_device_automations` — List the triggers, conditions, and actions supported by one Home Assistant device.\n- `list_events` — List Home Assistant event types currently known by the instance.\n- `list_services` — List Home Assistant service domains and their available services.\n- `list_states` — List all current Home Assistant entity states.\n- `render_template` — Render a Home Assistant template against the connected instance.\n- `save_automation_config` — Create or replace one Home Assistant automation. Posting to an unused id creates the automation. Requires an admin access token, and only covers entries stored in the Home Assistant UI-editable config; entries defined in other YAML files return not found. [write]\n- `save_scene_config` — Create or replace one Home Assistant scene. Posting to an unused id creates the scene. Requires an admin access token, and only covers entries stored in the Home Assistant UI-editable config; entries defined in other YAML files return not found. [write]\n- `save_script_config` — Create or replace one Home Assistant script. Posting to an unused key creates the script. Requires an admin access token, and only covers entries stored in the Home Assistant UI-editable config; entries defined in other YAML files return not found. [write]\n- `search_related` — Find Home Assistant items related to an entity, device, area, automation, or configuration entry.\n- `validate_config` — Validate Home Assistant trigger, condition, and action configurations before storing an automation.\n\n## Safety\n\n- Untagged actions are reads (get / list / search) — safe to run directly.\n- **Actions tagged `[write]` change Home Assistant state — confirm the exact payload and effect with the user before running.**\n- **Actions tagged `[destructive]` remove or overwrite data — always confirm the target and get explicit approval first.**\n\n## First-time setup\n\nThese are **one-time** steps — do not repeat them on every call. Run a step only when a command fails for the matching reason.\n\n- **`oo: command not found`** — install the oo CLI (other platforms: ):\n\n ```bash\n curl -fsSL https://cli.oomol.com/install.sh | bash # macOS / Linux\n ```\n\n ```powershell\n irm https://cli.oomol.com/install.ps1 | iex # Windows PowerShell\n ```\n\n- **Not signed in / authentication error** — sign in to your OOMOL account once:\n\n ```bash\n oo auth login\n ```\n\n- **`scope_missing` / `credential_expired` / `app_not_ready` / `app_not_found`** — Home Assistant is not connected, or the connection expired or lacks a scope. Connect once (auth type: API key) at:\n\n ```text\n https://console.oomol.com/app-connections?provider=home_assistant\n ```\n\n- **HTTP 402 / `OOMOL_INSUFFICIENT_CREDIT`** — billing stop. Recharge at `https://console.oomol.com/billing/token-recharge` before retrying.\n\n## Resources\n\n- Home Assistant homepage: https://www.home-assistant.io\n\nFile v1.0.3:_meta.json\n\n{\n \"ownerId\": \"kn7fzg3sx4xr7ssnc2yyhpndx187yacb\",\n \"slug\": \"oo-home-assistant\",\n \"version\": \"1.0.3\",\n \"publishedAt\": 1786435810389\n}\n\nFile v1.0.3:skill-card.md\n\n## Description:\n\nHome Assistant (home-assistant.io). Use this skill for Home Assistant reading, creating, updating, and deleting tasks through the OOMOL-connected connector instead of calling the API directly.\n\nThis skill is ready for commercial/non-commercial use.\n\n## Publisher:\n\n[oomol](https://clawhub.ai/user/oomol)\n\n### License/Terms of Use:\n\nMIT-0\n\n## Use Case:\n\nExternal users and developers use this skill to inspect Home Assistant state, history, registries, services, calendars, events, templates, and configuration, then perform controlled writes for services, scripts, automations, and scenes.\n\n### Deployment Geography for Use:\n\nGlobal\n\n## Known Risks and Mitigations:\n\nRisk: The skill can control Home Assistant and may create, replace, or delete automations, scenes, and scripts.\n\nMitigation: Use a Home Assistant account whose permissions match the actions the agent should be allowed to perform, and require user confirmation before write or destructive actions.\n\nRisk: Configuration changes could break or misconfigure automations, scenes, or scripts.\n\nMitigation: Inspect live action schemas before payload construction and use Home Assistant validation or configuration checks before storing changes.\n\n## Reference(s):\n\n- [ClawHub Skill Page](https://clawhub.ai/oomol/skills/oo-home-assistant)\n- [OOMOL Publisher Profile](https://clawhub.ai/user/oomol)\n- [Home Assistant](https://www.home-assistant.io)\n- [oo CLI](https://github.com/oomol-lab/oo-cli)\n- [oo CLI Install Guide](https://cli.oomol.com/install-guide.md)\n\n## Skill Output:\n\n**Output Type(s):** [text, markdown, shell commands, configuration, guidance]\n\n**Output Format:** [Markdown with inline shell commands and JSON payloads]\n\n**Output Parameters:** [1D]\n\n**Other Properties Related to Output:** [May return Home Assistant connector responses as JSON and may propose configuration changes for user approval.]\n\n## Skill Version(s):\n\n1.0.3 (source: server evidence and frontmatter)\n\n## Ethical Considerations:\n\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment.\n\nArchive v1.0.2: 3 files, 3418 bytes\n\nFiles: skill-card.md (2447b), SKILL.md (3949b), _meta.json (136b)\n\nFile v1.0.2:SKILL.md\n\n---\nname: oo-home-assistant\ndescription: \"Home Assistant (home-assistant.io). Use this skill for ANY Home Assistant request — searching and reading data. Whenever a task involves Home Assistant, use this skill instead of calling the API directly.\"\nallowed-tools: [Bash(oo *)]\nmetadata:\n title: \"Home Assistant\"\n author: \"OOMOL\"\n version: \"1.0.2\"\n services: [\"home_assistant\"]\n icon: \"https://static.oomol.com/logo/third-party/home_assistant.svg\"\n---\n\n# Home Assistant\n\nOperate **Home Assistant** through your OOMOL-connected account. This skill calls the `home_assistant` connector with the [oo CLI](https://github.com/oomol-lab/oo-cli); OOMOL injects credentials server-side, so you never handle raw tokens.\n\n## Running an action\n\nAssume the user has already installed the oo CLI, signed in, and connected Home Assistant. **Do not run `oo auth login` or open the connection URL proactively — just run the action.** Fall back to [First-time setup](#first-time-setup) only when a command actually fails with an auth or connection error.\n\n**1. Inspect the contract** to get the authoritative input/output schema before building a payload:\n\n```bash\noo connector schema \"home_assistant\" --action \"\"\n```\n\n**2. Run the action** with a JSON payload that matches the input schema:\n\n```bash\noo connector run \"home_assistant\" --action \"\" --data '' --json\n```\n\n- `--data` takes a JSON object string or `@path/to/file.json`; omit it to send `{}`.\n- The response is `{ \"data\": ..., \"meta\": { \"executionId\": \"...\" } }`; the execution id lives under `meta.executionId`.\n\nEach action is listed below with a one-line description; actions that change state carry a `[write]` or `[destructive]` tag. Before constructing `--data`, fetch the action's live schema with `oo connector schema` to get its authoritative input fields.\n\n## Available actions\n\n- `call_service` — Call a Home Assistant service to control entities, such as light.turn_on or switch.turn_off.\n- `fire_event` — Fire one Home Assistant event with optional event data.\n- `get_config` — Fetch the Home Assistant instance configuration.\n- `get_state` — Fetch the current state for one Home Assistant entity.\n- `list_events` — List Home Assistant event types currently known by the instance.\n- `list_services` — List Home Assistant service domains and their available services.\n- `list_states` — List all current Home Assistant entity states.\n- `render_template` — Render a Home Assistant template against the connected instance.\n\n## Safety\n\n- Untagged actions are reads (get / list / search) — safe to run directly.\n- **Actions tagged `[write]` change Home Assistant state — confirm the exact payload and effect with the user before running.**\n- **Actions tagged `[destructive]` remove or overwrite data — always confirm the target and get explicit approval first.**\n\n## First-time setup\n\nThese are **one-time** steps — do not repeat them on every call. Run a step only when a command fails for the matching reason.\n\n- **`oo: command not found`** — install the oo CLI (other platforms: ):\n\n ```bash\n curl -fsSL https://cli.oomol.com/install.sh | bash # macOS / Linux\n ```\n\n ```powershell\n irm https://cli.oomol.com/install.ps1 | iex # Windows PowerShell\n ```\n\n- **Not signed in / authentication error** — sign in to your OOMOL account once:\n\n ```bash\n oo auth login\n ```\n\n- **`scope_missing` / `credential_expired` / `app_not_ready` / `app_not_found`** — Home Assistant is not connected, or the connection expired or lacks a scope. Connect once (auth type: API key) at:\n\n ```text\n https://console.oomol.com/app-connections?provider=home_assistant\n ```\n\n- **HTTP 402 / `OOMOL_INSUFFICIENT_CREDIT`** — billing stop. Recharge at `https://console.oomol.com/billing/token-recharge` before retrying.\n\n## Resources\n\n- Home Assistant homepage: https://www.home-assistant.io\n\nFile v1.0.2:_meta.json\n\n{\n \"ownerId\": \"kn7fzg3sx4xr7ssnc2yyhpndx187yacb\",\n \"slug\": \"oo-home-assistant\",\n \"version\": \"1.0.2\",\n \"publishedAt\": 1781603869391\n}\n\nFile v1.0.2:skill-card.md\n\n## Description:
\nOperates Home Assistant through the OOMOL home_assistant connector for reading data and running approved actions.
\n\nThis skill is ready for commercial/non-commercial use.
\n\n## Publisher:
\n[oomol](https://clawhub.ai/user/oomol)
\n\n### License/Terms of Use:
\nMIT-0
\n\n\n## Use Case:
\nExternal users and developers use this skill to inspect Home Assistant configuration, entity states, events, services, and templates, and to run user-confirmed service calls or events through an OOMOL-connected account.
\n\n### Deployment Geography for Use:
\nGlobal
\n\n## Known Risks and Mitigations:
\nRisk: The skill can run Home Assistant control actions that change real devices or automations.
\nMitigation: Require explicit user confirmation of the exact action, target entities, payload, and expected effect before running call_service or fire_event.
\nRisk: The skill requires a connected Home Assistant account and should be trusted with sensitive account access.
\nMitigation: Install only if the user trusts OOMOL, use the OOMOL connection flow, and avoid asking for or exposing raw Home Assistant tokens.
\nRisk: Dynamic templates and broad state reads may reveal sensitive details about the connected Home Assistant instance.
\nMitigation: Review requested templates and read scopes before execution, and only return information relevant to the user's request.
\n\n\n## Reference(s):
\n- [ClawHub Skill Page](https://clawhub.ai/oomol/oo-home-assistant)
\n- [Home Assistant Homepage](https://www.home-assistant.io)
\n- [OOMOL oo CLI](https://github.com/oomol-lab/oo-cli)
\n- [OOMOL CLI Install Guide](https://cli.oomol.com/install-guide.md)
\n\n\n## Skill Output:
\n**Output Type(s):** [Text, Shell commands, Configuration, Guidance]
\n**Output Format:** [Markdown with inline bash commands and JSON payloads]
\n**Output Parameters:** [1D]
\n**Other Properties Related to Output:** [May execute oo CLI connector actions that return JSON responses with data and an execution id.]
\n\n## Skill Version(s):
\n1.0.2 (source: server evidence release and SKILL.md metadata)
\n\n## Ethical Considerations:
\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment.
\n\nArchive v1.0.1: 3 files, 3321 bytes\n\nFiles: skill-card.md (2316b), SKILL.md (3878b), _meta.json (136b)\n\nFile v1.0.1:SKILL.md\n\n---\nname: oo-home-assistant\ndescription: \"Home Assistant (home-assistant.io). Use this skill for ANY Home Assistant request — searching and reading data. Whenever a task involves Home Assistant, use this skill instead of calling the API directly.\"\nallowed-tools: [Bash(oo *)]\nmetadata:\n title: \"Home Assistant\"\n author: \"OOMOL\"\n version: \"1.0.1\"\n services: [\"home_assistant\"]\n---\n\n# Home Assistant\n\nOperate **Home Assistant** through your OOMOL-connected account. This skill calls the `home_assistant` connector with the [oo CLI](https://github.com/oomol-lab/oo-cli); OOMOL injects credentials server-side, so you never handle raw tokens.\n\n## Running an action\n\nAssume the user has already installed the oo CLI, signed in, and connected Home Assistant. **Do not run `oo auth login` or open the connection URL proactively — just run the action.** Fall back to [First-time setup](#first-time-setup) only when a command actually fails with an auth or connection error.\n\n**1. Inspect the contract** to get the authoritative input/output schema before building a payload:\n\n```bash\noo connector schema \"home_assistant\" --action \"\"\n```\n\n**2. Run the action** with a JSON payload that matches the input schema:\n\n```bash\noo connector run \"home_assistant\" --action \"\" --data '' --json\n```\n\n- `--data` takes a JSON object string or `@path/to/file.json`; omit it to send `{}`.\n- The response is `{ \"data\": ..., \"meta\": { \"executionId\": \"...\" } }`; the execution id lives under `meta.executionId`.\n\nEach action is listed below with a one-line description; actions that change state carry a `[write]` or `[destructive]` tag. Before constructing `--data`, fetch the action's live schema with `oo connector schema` to get its authoritative input fields.\n\n## Available actions\n\n- `call_service` — Call a Home Assistant service to control entities, such as light.turn_on or switch.turn_off.\n- `fire_event` — Fire one Home Assistant event with optional event data.\n- `get_config` — Fetch the Home Assistant instance configuration.\n- `get_state` — Fetch the current state for one Home Assistant entity.\n- `list_events` — List Home Assistant event types currently known by the instance.\n- `list_services` — List Home Assistant service domains and their available services.\n- `list_states` — List all current Home Assistant entity states.\n- `render_template` — Render a Home Assistant template against the connected instance.\n\n## Safety\n\n- Untagged actions are reads (get / list / search) — safe to run directly.\n- **Actions tagged `[write]` change Home Assistant state — confirm the exact payload and effect with the user before running.**\n- **Actions tagged `[destructive]` remove or overwrite data — always confirm the target and get explicit approval first.**\n\n## First-time setup\n\nThese are **one-time** steps — do not repeat them on every call. Run a step only when a command fails for the matching reason.\n\n- **`oo: command not found`** — install the oo CLI (other platforms: ):\n\n ```bash\n curl -fsSL https://cli.oomol.com/install.sh | bash # macOS / Linux\n ```\n\n ```powershell\n irm https://cli.oomol.com/install.ps1 | iex # Windows PowerShell\n ```\n\n- **Not signed in / authentication error** — sign in to your OOMOL account once:\n\n ```bash\n oo auth login\n ```\n\n- **`scope_missing` / `credential_expired` / `app_not_ready` / `app_not_found`** — Home Assistant is not connected, or the connection expired or lacks a scope. Connect once (auth type: API key) at:\n\n ```text\n https://console.oomol.com/app-connections?provider=home_assistant\n ```\n\n- **HTTP 402 / `OOMOL_INSUFFICIENT_CREDIT`** — billing stop. Recharge at `https://console.oomol.com/billing/token-recharge` before retrying.\n\n## Resources\n\n- Home Assistant homepage: https://www.home-assistant.io\n\nFile v1.0.1:_meta.json\n\n{\n \"ownerId\": \"kn7fzg3sx4xr7ssnc2yyhpndx187yacb\",\n \"slug\": \"oo-home-assistant\",\n \"version\": \"1.0.1\",\n \"publishedAt\": 1781000113507\n}\n\nFile v1.0.1:skill-card.md\n\n## Description:
\nHelps an agent operate a connected Home Assistant instance through OOMOL, including reading configuration and entity state, calling services, firing events, and rendering templates.
\n\nThis skill is ready for commercial/non-commercial use.
\n\n## Publisher:
\n[oomol](https://clawhub.ai/user/oomol)
\n\n### License/Terms of Use:
\nMIT-0
\n\n\n## Use Case:
\nExternal users and developers use this skill to let an agent inspect and control a Home Assistant instance through the OOMOL Home Assistant connector.
\n\n### Deployment Geography for Use:
\nGlobal
\n\n## Known Risks and Mitigations:
\nRisk: The skill can change real Home Assistant devices or automations through service calls and events.
\nMitigation: Require the agent to show the exact target, action, and payload before any state-changing request.
\nRisk: The security review says the artifact understates and mislabels actions that can change Home Assistant state.
\nMitigation: Treat call_service and fire_event as write actions even when they are not tagged that way in the artifact.
\nRisk: The skill requires access to the user's Home Assistant connection through OOMOL.
\nMitigation: Install only when the user accepts that connector access and avoid exposing raw credentials in prompts or outputs.
\n\n\n## Reference(s):
\n- [ClawHub Skill Page](https://clawhub.ai/oomol/oo-home-assistant)
\n- [OOMOL Publisher Profile](https://clawhub.ai/user/oomol)
\n- [Home Assistant Homepage](https://www.home-assistant.io)
\n- [oo CLI](https://github.com/oomol-lab/oo-cli)
\n\n\n## Skill Output:
\n**Output Type(s):** [text, markdown, shell commands, configuration, guidance]
\n**Output Format:** [Markdown with inline shell commands and JSON payloads]
\n**Output Parameters:** [1D]
\n**Other Properties Related to Output:** [May trigger OOMOL connector calls that return JSON from Home Assistant.]
\n\n## Skill Version(s):
\n1.0.1 (source: frontmatter and server release metadata)
\n\n## Ethical Considerations:
\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment.
\n\nArchive v1.0.0: 11 files, 7357 bytes\n\nFiles: actions/call_service.md (689b), actions/fire_event.md (642b), actions/get_config.md (635b), actions/get_state.md (636b), actions/list_events.md (656b), actions/list_services.md (667b), actions/list_states.md (638b), actions/render_template.md (676b), skill-card.md (2324b), SKILL.md (4124b), _meta.json (136b)\n\nFile v1.0.0:SKILL.md\n\n---\nname: oo-home-assistant\ndescription: \"Home Assistant (home-assistant.io). Use this skill for ANY Home Assistant request — searching and reading data. Whenever a task involves Home Assistant, use this skill instead of calling the API directly.\"\nallowed-tools: [Bash(oo *)]\nmetadata:\n title: \"Home Assistant\"\n author: \"OOMOL\"\n version: \"1.0.0\"\n service: \"home_assistant\"\n categories: \"Productivity\"\n homepage: \"https://www.home-assistant.io\"\n---\n\n# Home Assistant\n\nOperate **Home Assistant** through your OOMOL-connected account. This skill calls the `home_assistant` connector with the [oo CLI](https://github.com/oomol-lab/oo-cli); OOMOL injects credentials server-side, so you never handle raw tokens.\n\nCategory: Productivity. Exposes 8 action(s).\n\n## Running an action\n\nAssume the user has already installed the oo CLI, signed in, and connected Home Assistant. **Do not run `oo auth login` or open the connection URL proactively — just run the action.** Fall back to [First-time setup](#first-time-setup) only when a command actually fails with an auth or connection error.\n\n**1. Inspect the contract** to get the authoritative input/output schema before building a payload:\n\n```bash\noo connector schema \"home_assistant\" --action \"\"\n```\n\n**2. Run the action** with a JSON payload that matches the input schema:\n\n```bash\noo connector run \"home_assistant\" --action \"\" --data '' --json\n```\n\n- `--data` takes a JSON object string or `@path/to/file.json`; omit it to send `{}`.\n- The response is `{ \"data\": ..., \"meta\": { \"executionId\": \"...\" } }`; the execution id lives under `meta.executionId`.\n\nEach action below links to a reference file with its purpose and exact commands. Read the linked file, then fetch the live schema with `oo connector schema` before constructing `--data`.\n\n## Available actions\n\n- [`call_service`](actions/call_service.md) — Call a Home Assistant service to control entities, such as light.turn_on or switch.turn_off.\n- [`fire_event`](actions/fire_event.md) — Fire one Home Assistant event with optional event data.\n- [`get_config`](actions/get_config.md) — Fetch the Home Assistant instance configuration.\n- [`get_state`](actions/get_state.md) — Fetch the current state for one Home Assistant entity.\n- [`list_events`](actions/list_events.md) — List Home Assistant event types currently known by the instance.\n- [`list_services`](actions/list_services.md) — List Home Assistant service domains and their available services.\n- [`list_states`](actions/list_states.md) — List all current Home Assistant entity states.\n- [`render_template`](actions/render_template.md) — Render a Home Assistant template against the connected instance.\n\n## Safety\n\n- Read actions (get / list / search) are safe to run directly.\n- **Create, update, send, or post actions change Home Assistant state — confirm the exact payload and effect with the user before running.**\n- **Delete or remove actions are destructive — always confirm the target and get explicit approval first.**\n\n## First-time setup\n\nThese are **one-time** steps — do not repeat them on every call. Run a step only when a command fails for the matching reason.\n\n- **`oo: command not found`** — install the oo CLI (other platforms: ):\n\n ```bash\n curl -fsSL https://cli.oomol.com/install.sh | bash # macOS / Linux\n ```\n\n ```powershell\n irm https://cli.oomol.com/install.ps1 | iex # Windows PowerShell\n ```\n\n- **Not signed in / authentication error** — sign in to your OOMOL account once:\n\n ```bash\n oo auth login\n ```\n\n- **`scope_missing` / `credential_expired` / `app_not_ready` / `app_not_found`** — Home Assistant is not connected, or the connection expired or lacks a scope. Connect once (auth type: API key) at:\n\n ```text\n https://console.oomol.com/app-connections?provider=home_assistant\n ```\n\n- **HTTP 402 / `OOMOL_INSUFFICIENT_CREDIT`** — billing stop. Recharge at `https://console.oomol.com/billing/token-recharge` before retrying.\n\n## Resources\n\n- Home Assistant homepage: https://www.home-assistant.io\n\nFile v1.0.0:_meta.json\n\n{\n \"ownerId\": \"kn7fzg3sx4xr7ssnc2yyhpndx187yacb\",\n \"slug\": \"oo-home-assistant\",\n \"version\": \"1.0.0\",\n \"publishedAt\": 1780502403656\n}\n\nFile v1.0.0:actions/call_service.md\n\n# Home Assistant · `call_service`\n\nCall a Home Assistant service to control entities, such as light.turn_on or switch.turn_off.\n\n- **Service**: `home_assistant`\n- **Action**: `call_service`\n- **Action id**: `home_assistant.call_service`\n\n## Inspect the schema\n\nAlways fetch the authoritative input/output schema before building a payload — fields and defaults can change upstream:\n\n```bash\noo connector schema \"home_assistant\" --action \"call_service\"\n```\n\n## Run\n\n```bash\noo connector run \"home_assistant\" --action \"call_service\" --data '{}' --json\n```\n\nReplace `{}` with a JSON object that matches the input schema. The response is `{ \"data\": ..., \"meta\": { \"executionId\": \"...\" } }`.\n\nFile v1.0.0:actions/fire_event.md\n\n# Home Assistant · `fire_event`\n\nFire one Home Assistant event with optional event data.\n\n- **Service**: `home_assistant`\n- **Action**: `fire_event`\n- **Action id**: `home_assistant.fire_event`\n\n## Inspect the schema\n\nAlways fetch the authoritative input/output schema before building a payload — fields and defaults can change upstream:\n\n```bash\noo connector schema \"home_assistant\" --action \"fire_event\"\n```\n\n## Run\n\n```bash\noo connector run \"home_assistant\" --action \"fire_event\" --data '{}' --json\n```\n\nReplace `{}` with a JSON object that matches the input schema. The response is `{ \"data\": ..., \"meta\": { \"executionId\": \"...\" } }`.\n\nFile v1.0.0:actions/get_config.md\n\n# Home Assistant · `get_config`\n\nFetch the Home Assistant instance configuration.\n\n- **Service**: `home_assistant`\n- **Action**: `get_config`\n- **Action id**: `home_assistant.get_config`\n\n## Inspect the schema\n\nAlways fetch the authoritative input/output schema before building a payload — fields and defaults can change upstream:\n\n```bash\noo connector schema \"home_assistant\" --action \"get_config\"\n```\n\n## Run\n\n```bash\noo connector run \"home_assistant\" --action \"get_config\" --data '{}' --json\n```\n\nReplace `{}` with a JSON object that matches the input schema. The response is `{ \"data\": ..., \"meta\": { \"executionId\": \"...\" } }`.\n\nFile v1.0.0:actions/get_state.md\n\n# Home Assistant · `get_state`\n\nFetch the current state for one Home Assistant entity.\n\n- **Service**: `home_assistant`\n- **Action**: `get_state`\n- **Action id**: `home_assistant.get_state`\n\n## Inspect the schema\n\nAlways fetch the authoritative input/output schema before building a payload — fields and defaults can change upstream:\n\n```bash\noo connector schema \"home_assistant\" --action \"get_state\"\n```\n\n## Run\n\n```bash\noo connector run \"home_assistant\" --action \"get_state\" --data '{}' --json\n```\n\nReplace `{}` with a JSON object that matches the input schema. The response is `{ \"data\": ..., \"meta\": { \"executionId\": \"...\" } }`.\n\nFile v1.0.0:actions/list_events.md\n\n# Home Assistant · `list_events`\n\nList Home Assistant event types currently known by the instance.\n\n- **Service**: `home_assistant`\n- **Action**: `list_events`\n- **Action id**: `home_assistant.list_events`\n\n## Inspect the schema\n\nAlways fetch the authoritative input/output schema before building a payload — fields and defaults can change upstream:\n\n```bash\noo connector schema \"home_assistant\" --action \"list_events\"\n```\n\n## Run\n\n```bash\noo connector run \"home_assistant\" --action \"list_events\" --data '{}' --json\n```\n\nReplace `{}` with a JSON object that matches the input schema. The response is `{ \"data\": ..., \"meta\": { \"executionId\": \"...\" } }`.\n\nFile v1.0.0:actions/list_services.md\n\n# Home Assistant · `list_services`\n\nList Home Assistant service domains and their available services.\n\n- **Service**: `home_assistant`\n- **Action**: `list_services`\n- **Action id**: `home_assistant.list_services`\n\n## Inspect the schema\n\nAlways fetch the authoritative input/output schema before building a payload — fields and defaults can change upstream:\n\n```bash\noo connector schema \"home_assistant\" --action \"list_services\"\n```\n\n## Run\n\n```bash\noo connector run \"home_assistant\" --action \"list_services\" --data '{}' --json\n```\n\nReplace `{}` with a JSON object that matches the input schema. The response is `{ \"data\": ..., \"meta\": { \"executionId\": \"...\" } }`.\n\nFile v1.0.0:actions/list_states.md\n\n# Home Assistant · `list_states`\n\nList all current Home Assistant entity states.\n\n- **Service**: `home_assistant`\n- **Action**: `list_states`\n- **Action id**: `home_assistant.list_states`\n\n## Inspect the schema\n\nAlways fetch the authoritative input/output schema before building a payload — fields and defaults can change upstream:\n\n```bash\noo connector schema \"home_assistant\" --action \"list_states\"\n```\n\n## Run\n\n```bash\noo connector run \"home_assistant\" --action \"list_states\" --data '{}' --json\n```\n\nReplace `{}` with a JSON object that matches the input schema. The response is `{ \"data\": ..., \"meta\": { \"executionId\": \"...\" } }`.\n\nFile v1.0.0:actions/render_template.md\n\n# Home Assistant · `render_template`\n\nRender a Home Assistant template against the connected instance.\n\n- **Service**: `home_assistant`\n- **Action**: `render_template`\n- **Action id**: `home_assistant.render_template`\n\n## Inspect the schema\n\nAlways fetch the authoritative input/output schema before building a payload — fields and defaults can change upstream:\n\n```bash\noo connector schema \"home_assistant\" --action \"render_template\"\n```\n\n## Run\n\n```bash\noo connector run \"home_assistant\" --action \"render_template\" --data '{}' --json\n```\n\nReplace `{}` with a JSON object that matches the input schema. The response is `{ \"data\": ..., \"meta\": { \"executionId\": \"...\" } }`.\n\nFile v1.0.0:skill-card.md\n\n## Description:
\nConnects an agent to Home Assistant through OOMOL's home_assistant connector to inspect configuration, states, events, and services, render templates, and run confirmed control actions.
\n\nThis skill is ready for commercial/non-commercial use.
\n\n## Publisher:
\n[oomol](https://clawhub.ai/user/oomol)
\n\n### License/Terms of Use:
\nMIT-0
\n\n\n## Use Case:
\nExternal users and developers use this skill to inspect a connected Home Assistant instance and operate its entities through the OOMOL home_assistant connector. It supports configuration, state, event, service, template, and controlled state-changing workflows when the user has connected an appropriate Home Assistant account.
\n\n### Deployment Geography for Use:
\nGlobal
\n\n## Known Risks and Mitigations:
\nRisk: The skill can control Home Assistant devices and fire events, even though its summary emphasizes read and search tasks.
\nMitigation: Require explicit user confirmation before service calls, event firing, or any other state-changing action.
\nRisk: A connected Home Assistant account may have access to sensitive devices such as locks, alarms, doors, or appliances.
\nMitigation: Use an OOMOL/Home Assistant account with permissions the user is comfortable granting, and review the target entity, service, and payload before execution.
\n\n\n## Reference(s):
\n- [Home Assistant homepage](https://www.home-assistant.io)
\n- [oo CLI](https://github.com/oomol-lab/oo-cli)
\n- [ClawHub skill page](https://clawhub.ai/oomol/oo-home-assistant)
\n\n\n## Skill Output:
\n**Output Type(s):** [text, markdown, shell commands, configuration, guidance]
\n**Output Format:** [Markdown with inline shell commands and JSON payload examples]
\n**Output Parameters:** [1D]
\n**Other Properties Related to Output:** [Commands call the OOMOL oo CLI and return JSON responses from the connected Home Assistant instance.]
\n\n## Skill Version(s):
\n1.0.0 (source: frontmatter and server evidence)
\n\n## Ethical Considerations:
\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment.
","readmeExcerpt":"Skill: Home Assistant Owner: oomol Summary: Home Assistant (home-assistant.io). Use this skill for ANY Home Assistant request — reading, creating, updating, and deleting data. Whenever a task involves Home Assistant, use this skill instead of calling the API directly. Tags: latest:1.0.6 Version history: v1.0.6 | 2026-09-20T03:13:13.415Z | user - Operates Home Assistant through the OOMOL home_assistant connector using","codeSnippets":[],"executableExamples":[{"language":"bash","snippet":"oo connector schema \"home_assistant\" --action \"\""},{"language":"bash","snippet":"oo connector run \"home_assistant\" --action \"\" --data '' --json"},{"language":"bash","snippet":"curl -fsSL https://cli.oomol.com/install.sh | bash # macOS / Linux"},{"language":"bash","snippet":"curl -fsSL https://cli.oomol.com/install.sh | bash # macOS / Linux"},{"language":"powershell","snippet":"irm https://cli.oomol.com/install.ps1 | iex # Windows PowerShell"},{"language":"bash","snippet":"oo auth login"}],"parameters":null,"dependencies":[],"permissions":[],"extractedFiles":[{"path":"SKILL.md","content":"---\nname: oo-home-assistant\ndescription: \"Home Assistant (home-assistant.io). Use this skill for ANY Home Assistant request — reading, creating, updating, and deleting data. Whenever a task involves Home Assistant, use this skill instead of calling the API directly.\"\nallowed-tools: [Bash(oo *)]\nmetadata:\n title: \"Home Assistant\"\n author: \"OOMOL\"\n version: \"1.0.6\"\n services: [\"home_assistant\"]\n icon: \"https://static.oomol.com/logo/third-party/home_assistant.svg\"\n---\n\n# Home Assistant\n\nOperate **Home Assistant** through your OOMOL-connected account. This skill calls the `home_assistant` connector with the [oo CLI](https://github.com/oomol-lab/oo-cli); OOMOL injects credentials server-side, so you never handle raw tokens.\n\n## Running an action\n\nAssume the user has already installed the oo CLI, signed in, and connected Home Assistant. **Do not run `oo auth login` or open the connection URL proactively — just run the action.** Fall back to [First-time setup](#first-time-setup) only when a command actually fails with an auth or connection error.\n\n**1. Inspect the contract** to get the authoritative input/output schema before building a payload:\n\n```bash\noo connector schema \"home_assistant\" --action \"\"\n```\n\n**2. Run the action** with a JSON payload that matches the input schema:\n\n```bash\noo connector run \"home_assistant\" --action \"\" --data '' --json\n```\n\n- `--data` takes a JSON object string or `@path/to/file.json`; omit it to send `{}`.\n- The response is `{ \"data\": ..., \"meta\": { \"executionId\": \"...\" } }`; the execution id lives under `meta.executionId`.\n\nEach action is listed below with a one-line description; actions that change state carry a `[write]` or `[destructive]` tag. Before constructing `--data`, fetch the action's live schema with `oo connector schema` to get its authoritative input fields.\n\n## Available actions\n\n- `call_service` — Call a Home Assistant service to control entities, such as light.turn_on or switch.turn_off. [destructive]\n- `check_config` — Ask Home Assistant to validate its own configuration files and report errors and warnings. Requires an admin access token.\n- `delete_automation_config` — Delete one Home Assistant automation. Requires an admin access token, and only covers entries stored in the Home Assistant UI-editable config; entries defined in other YAML files return not found. [destructive]\n- `delete_scene_config` — Delete one Home Assistant scene. Requires an admin access token, and only covers entries stored in the Home Assistant UI-editable config; entries defined in other YAML files return not found. [destructive]\n- `delete_script_config` — Delete one Home Assistant script. Requires an admin access token, and only covers entries stored in the Home Assistant UI-editable config; entries defined in other YAML files return not found. [destructive]\n- `execute_script` — Run a Home Assistant script sequence containing service calls, delays, and conditions. [write]\n- `fire_event` — Fir"},{"path":"_meta.json","content":"{\n \"ownerId\": \"kn7fzg3sx4xr7ssnc2yyhpndx187yacb\",\n \"slug\": \"oo-home-assistant\",\n \"version\": \"1.0.6\",\n \"publishedAt\": 1789873993415\n}"},{"path":"skill-card.md","content":"## Description:\n\nHome Assistant (home-assistant.io). Use this skill for Home Assistant requests involving reading, creating, updating, and deleting data through the OOMOL-connected Home Assistant connector.\n\nThis skill is ready for commercial/non-commercial use.\n\n## Publisher:\n\n[oomol](https://clawhub.ai/user/oomol)\n\n### License/Terms of Use:\n\nMIT-0\n\n## Use Case:\n\nExternal users and developers use this skill to inspect and operate a connected Home Assistant instance through the OOMOL `home_assistant` connector. It supports reading entity state and configuration, running service calls and scripts, firing events, and managing UI-editable automations, scenes, and scripts.\n\n### Deployment Geography for Use:\n\nGlobal\n\n## Known Risks and Mitigations:\n\nRisk: The skill can control Home Assistant devices and make state-changing or destructive configuration changes.\n\nMitigation: Require explicit approval for write and destructive actions, confirm the exact target and payload, and connect Home Assistant with the minimum scopes needed.\n\nRisk: Fallback setup includes remote installer scripts that may be executed directly in a shell.\n\nMitigation: Prefer installing the oo CLI through a verified package or reviewed installer before using the skill.\n\n## Reference(s):\n\n- [Home Assistant homepage](https://www.home-assistant.io)\n- [oo CLI](https://github.com/oomol-lab/oo-cli)\n- [oo CLI install guide](https://cli.oomol.com/install-guide.md)\n- [ClawHub skill page](https://clawhub.ai/oomol/skills/oo-home-assistant)\n- [OOMOL publisher profile](https://clawhub.ai/user/oomol)\n\n## Skill Output:\n\n**Output Type(s):** [Shell commands, Configuration, Guidance, Text]\n\n**Output Format:** [Markdown with inline shell commands and JSON payload examples]\n\n**Output Parameters:** [1D]\n\n**Other Properties Related to Output:** [Uses live connector schemas before constructing action payloads.]\n\n## Skill Version(s):\n\n1.0.6 (source: server release metadata and SKILL.md frontmatter)\n\n## Ethical Considerations:\n\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment."}],"languages":[],"docsSourceLabel":"CLAWHUB","editorialOverview":null,"editorialQuality":{"score":100,"threshold":65,"status":"thin","wordCount":1559,"uniquenessScore":40,"reasons":["uniqueness-below-45"]}},"media":{"evidence":{"source":"no-media","verified":false,"confidence":"low","updatedAt":"2026-10-10T15:12:31.885Z","emptyReason":"No screenshots, media assets, or demo links are available."},"primaryImageUrl":null,"mediaAssetCount":0,"assets":[],"demoUrl":null},"ownerResources":{"evidence":{"source":"unclaimed","verified":false,"confidence":"low","updatedAt":"2026-10-10T15:12:31.885Z","emptyReason":"This page has not been claimed by the agent owner."},"hasCustomPage":false,"customPageUpdatedAt":null,"customLinks":[],"structuredLinks":{"docsUrl":null,"demoUrl":null,"supportUrl":null,"pricingUrl":null,"statusUrl":null},"customPage":null},"relatedAgents":{"evidence":{"source":"protocol-neighbors","verified":false,"confidence":"medium","updatedAt":"2026-10-10T17:35:38.972Z","emptyReason":null},"items":[{"id":"8ebccd8e-3863-4187-8355-c3f14e1f9edf","entityType":"agent","canonicalPath":"/agent/iofficeai-aionui","slug":"iofficeai-aionui","name":"AionUi","description":"Free, local, open-source 24/7 Cowork app and OpenClaw for Gemini CLI, Claude Code, Codex, OpenCode, Qwen Code, Goose CLI, Auggie, and more | 🌟 Star if you like it!","url":"https://github.com/iOfficeAI/AionUi","homepage":"https://www.aionui.com","source":"GITHUB_REPOS","protocols":["MCP","OPENCLAW"],"capabilities":[],"safetyScore":100,"overallRank":70,"updatedAt":"2026-10-09T19:11:12.944Z","createdAt":"2026-02-25T03:38:16.584Z","downloads":null},{"id":"b917f68a-ebff-438e-84f8-3f4b2494c0bc","entityType":"agent","canonicalPath":"/agent/activepieces-activepieces","slug":"activepieces-activepieces","name":"activepieces","description":"AI Agents & MCPs & AI Workflow Automation • (~400 MCP servers for AI agents) • AI Automation / AI Agent with MCPs • AI Workflows & AI Agents • MCPs for AI Agents","url":"https://github.com/activepieces/activepieces","homepage":"https://www.activepieces.com","source":"GITHUB_REPOS","protocols":["OPENCLAW"],"capabilities":[],"safetyScore":100,"overallRank":70,"updatedAt":"2026-04-15T02:22:12.426Z","createdAt":"2026-02-25T03:38:12.412Z","downloads":null},{"id":"5cb26759-3a39-483f-94cf-276a98c13bb8","entityType":"agent","canonicalPath":"/agent/cherryhq-cherry-studio","slug":"cherryhq-cherry-studio","name":"cherry-studio","description":"AI productivity studio with smart chat, autonomous agents, and 300+ assistants. Unified access to frontier LLMs","url":"https://github.com/CherryHQ/cherry-studio","homepage":"https://cherry-ai.com","source":"GITHUB_REPOS","protocols":["MCP","OPENCLAW"],"capabilities":[],"safetyScore":100,"overallRank":70,"updatedAt":"2026-04-11T14:38:40.986Z","createdAt":"2026-02-25T03:38:19.379Z","downloads":null},{"id":"6f6582d0-5d76-4f0f-b81d-86520247950b","entityType":"agent","canonicalPath":"/agent/copilotkit-copilotkit","slug":"copilotkit-copilotkit","name":"CopilotKit","description":"The Frontend for Agents & Generative UI. React + Angular","url":"https://github.com/CopilotKit/CopilotKit","homepage":"https://docs.copilotkit.ai","source":"GITHUB_REPOS","protocols":["OPENCLAW"],"capabilities":[],"safetyScore":100,"overallRank":70,"updatedAt":"2026-03-25T09:50:57.846Z","createdAt":"2026-02-25T03:39:14.617Z","downloads":null}],"links":{"hub":"/agent","source":"/agent/source/clawhub","protocols":[{"label":"OpenClaw","href":"/agent/protocol/openclew"}]}}}