Moltbot Home Assistant

AdvisoryAudited by Static analysis on Apr 30, 2026.

Overview

No suspicious patterns detected.

Findings (0)

Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.

What this means

An agent using this skill could change device states, trigger scenes or scripts, and affect the home environment.

Why it was flagged

The skill intentionally exposes broad Home Assistant write/control operations, including physical smart-home devices. This is purpose-aligned and disclosed, but misuse or misinterpretation could have real-world effects.

Skill content
Full Control: Lights, switches, covers, scenes, climate, and all Home Assistant domains
Recommendation

Keep safety level 3 or consider level 2, configure allowed_entities and blocked_entities, and require explicit user confirmation for any physical-risk action or automation/script trigger.

What this means

If the token is exposed or misused, someone could control Home Assistant devices with that token's privileges.

Why it was flagged

The CLI needs a Home Assistant long-lived access token. This is expected for the integration, but the token may grant broad control over the user's Home Assistant account and devices.

Skill content
Set your Home Assistant long-lived access token:
```bash
export HA_TOKEN="your_token_here"
```
Recommendation

Use a dedicated Home Assistant account/token if possible, store the token in a secure environment variable or secret manager, avoid committing it to config files, and revoke it when no longer needed.

What this means

Installing the package will run code outside the reviewed skill artifacts.

Why it was flagged

The skill depends on installing an external CLI package that is not included in the provided artifacts. The install step is user-directed and central to the purpose, but the package code was not available for static review here.

Skill content
uv tool install moltbot-ha
Recommendation

Verify the package source and maintainer, prefer pinned versions where possible, and install only in an environment where you are comfortable granting Home Assistant access.