Skill flagged — suspicious patterns detected

ClawHub Security flagged this skill as suspicious. Review the scan results before using.

Smart Home Assistant

v1.0.0

Monitor and analyze Home Assistant energy consumption. Use when the user asks about power usage, energy monitoring, consumption by room/area, or wants to gen...

1· 39·0 current·0 all-time
byPeter Lum@liverock
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
Capability signals
Requires OAuth token
These labels describe what authority the skill may exercise. They are separate from suspicious or malicious moderation verdicts.
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Suspicious
high confidence
Purpose & Capability
Name/description, SKILL.md, and the included Python modules all align: the skill fetches states/registries from Home Assistant, analyzes power usage, groups by area, and produces summaries, tables, and draft automation JSON. The requested config paths (home_assistant.url, home_assistant.token) match the stated purpose.
Instruction Scope
Runtime instructions and code remain within the stated read-only energy-analysis scope: they fetch /api/states, device and area registries, filter power entities, analyze and format outputs. The SKILL.md explicitly disallows direct device control and the code does not call HA services to change state. It does request a long-lived token to query Home Assistant, which is necessary for the functionality.
!
Install Mechanism
There is no install spec despite including Python code that imports third-party libraries (httpx and yaml). The registry only requires python3, but does not ensure httpx and PyYAML are available — this is a missing/incorrect install descriptor and will cause runtime failures or hidden ad-hoc installs depending on the host environment. No remote downloads or obviously malicious install URLs are present, but the lack of declared dependencies is a practical risk and incoherence.
!
Credentials
The skill requires a Home Assistant long-lived access token (referenced in skill.yaml as ${HA_TOKEN} and resolved by config._resolve_env_vars), but the top-level registry metadata lists no required env vars or primary credential. This mismatch means the skill silently requires a sensitive credential that is not advertised in metadata. The request is otherwise proportionate to the purpose (HA token is needed to read states/registries) — the problem is the metadata omission.
Persistence & Privilege
The skill is not always-enabled and does not write to other skills or system-wide settings. It performs network requests only to the configured Home Assistant URL and returns draft automation payloads for manual review. No elevated persistence or system modifications are requested.
What to consider before installing
This skill appears to do what it says (read Home Assistant, analyze energy usage, and produce draft automations), but there are two practical inconsistencies you should address before installing or running it: - Missing dependency/install information: The code imports httpx and yaml (PyYAML) but the registry/install metadata only declares python3 and provides no install script. Ensure the runtime environment has httpx and PyYAML installed (or ask the publisher to include an install spec). Without them the skill will fail or someone may attempt to install dependencies ad-hoc. - Undeclared credential requirement: The skill expects a long-lived Home Assistant token (HA_TOKEN referenced in skill.yaml and SKILL.md) but the registry metadata does not advertise any required env vars or primary credential. Treat the HA_TOKEN as sensitive: provide a scoped/limited token if possible, use a local/private HA endpoint, and rotate or revoke the token after testing. Review the generated automation JSON carefully before applying it in Home Assistant. Additional practical checks: - Confirm the HA URL you supply is only reachable by systems you trust (local network vs public internet). - Review the code (included) yourself to verify there are no exfiltration calls to external endpoints — the code only calls the configured HA URL; no other network destinations are present. - Ask the publisher to fix metadata (declare HA_TOKEN) and provide an explicit install/requirements file (requirements.txt or install spec) so the runtime behavior is predictable. If the above fixes are made (declare env/credentials and add dependency install instructions), the skill would be coherent and appropriate for the stated purpose. Until then the metadata/install mismatches make this risky to deploy without extra verification.

Like a lobster shell, security has layers — review code before you run it.

latestvk97emx52vzkx0e376gdwx9ssyn84d9ad

License

MIT-0
Free to use, modify, and redistribute. No attribution required.

Runtime requirements

🔌 Clawdis
Binspython3
Confighome_assistant.url, home_assistant.token

Comments