Home Assistant Master
v1.0.3Home Assistant OS (HAOS) operations skill for OpenClaw agents. Use for read-only audits, diagnostics, automation design/review, dashboard UX planning, voice...
⭐ 0· 982·3 current·3 all-time
by@djasha
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
Name/description (HAOS operations, audits, diagnostics, automation design) match the SKILL.md and reference docs. The skill requests no unrelated binaries, env vars, or configs; it explicitly expects platform-provided runtime access (connector/browser relay/token), which is appropriate for this purpose.
Instruction Scope
Runtime instructions stay on-purpose: emphasize read-only diagnostics, evidence collection (states/history/logs/traces) and only perform writes after explicit multi-step confirmation. The SKILL.md lists allowed vs blocked actions and tiered risk controls; reading potentially sensitive logs is expected for diagnostics and is explicitly constrained by the policy.
Install Mechanism
Instruction-only skill with no install spec and no code files — nothing is downloaded or written to disk by the skill itself, minimizing installation risk.
Credentials
Skill declares no required environment variables or credentials. It documents acceptable runtime access methods and credential handling policies (avoid pasting long-lived secrets, use secret storage), which is proportional to its needs. The platform/host will supply any needed tokens; users should ensure least-privilege tokens are used.
Persistence & Privilege
always:false (default) and no persistent install behavior. disable-model-invocation is false (agent may invoke autonomously) — this is the platform default and not combined with other red flags in this skill.
Assessment
This skill appears coherent and conservative, but it requires the hosting platform to provide access to your Home Assistant instance. Before installing or enabling it: (1) verify the hosting agent/connector is trusted and inspect its connector implementation if possible; (2) do not paste long-lived tokens into chat—use the platform's secret storage or short-lived, least-privilege tokens (read-only tokens for audits); (3) require explicit confirmation for any write actions and prefer two-step confirmation for sensitive changes; (4) audit agent activity and logs after first runs to ensure no unexpected data exfiltration; (5) if you need stronger guarantees, restrict the agent to read-only access or review the platform's permission model before granting runtime write capabilities.Like a lobster shell, security has layers — review code before you run it.
latestvk974yrthqfmwev6s9xe3t1x7ah81dtys
License
MIT-0
Free to use, modify, and redistribute. No attribution required.