Skill flagged — suspicious patterns detected
ClawHub Security flagged this skill as suspicious. Review the scan results before using.
HA Skill
v1.0.0Control Home Assistant entities via REST API. Use when the user asks to control lights, climate, switches, or other HA entities. Supports climate (thermostat...
⭐ 0· 45·0 current·0 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
Capability signals
These labels describe what authority the skill may exercise. They are separate from suspicious or malicious moderation verdicts.
OpenClaw
Suspicious
medium confidencePurpose & Capability
Name/description align with the included scripts: the skill uses curl + jq to call the Home Assistant REST API and implements climate, light, switch, and sensor actions, which is coherent with the claimed purpose. However, the SKILL/README expect credentials in ~/.openclaw/credentials/homeassistant.json but the registry metadata declares no required config paths or credentials — that's an omission/inconsistency.
Instruction Scope
Runtime instructions and the scripts read a long-lived HA access token from ~/.openclaw/credentials/homeassistant.json and make API calls to the configured URL. Reading that credentials file is within the skill's stated purpose (it needs a token), but the file path is not declared in the registry metadata. The SKILL.md also documents a scripts/service.sh helper and shows examples using it, but no scripts/service.sh exists in the package — a mismatch that could break functionality or indicate sloppy packaging.
Install Mechanism
No install spec (instruction-only) so nothing will be downloaded/executed at install time — lower risk. However the package includes shell scripts that will run locally when invoked; there is no automated installer but the presence of code files means review before use is prudent.
Credentials
The skill requests no environment variables in metadata but all scripts read a credentials file containing a long‑lived HA access token. That credential access is necessary for the stated purpose, but the registry should have declared the config path/credential requirement. Additionally, climate.sh uses bc for numeric comparison but 'bc' is not listed in required binaries — a missing dependency.
Persistence & Privilege
always is false and there is no install process that requests persistent system-wide privileges. The skill will only run when invoked and uses the user's credentials file; autonomous invocation is allowed (default) but not combined here with other high-privilege flags.
What to consider before installing
This skill appears to implement Home Assistant REST control and will read a long‑lived access token from ~/.openclaw/credentials/homeassistant.json and then call your HA API. Before installing or enabling it: 1) inspect or create the credentials file yourself (do not paste tokens into untrusted places) and be aware the token grants full control per HA permissions — treat it like a password and rotate it if needed; 2) note mismatches: the SKILL.md references scripts/service.sh which is missing, and climate.sh uses 'bc' but required binaries list only curl and jq — the package may be incomplete or poorly maintained; 3) ask the publisher for a homepage or source repo and for corrected metadata (declare config path and required binaries) or prefer a skill from a trusted source; 4) if you proceed, run in a safe environment (or on a non-critical HA instance) and limit token scope where possible. If the publisher provides an updated package (includes service.sh, declares the credentials file in metadata, and adds 'bc' to required binaries), my confidence that the package is coherent would increase.Like a lobster shell, security has layers — review code before you run it.
latestvk973r2wq7q9kq6sy89q51zq1nx84e3yb
License
MIT-0
Free to use, modify, and redistribute. No attribution required.
Runtime requirements
🏠 Clawdis
Binscurl, jq