Wiz Smart Light Control
Analysis
This skill appears to do what it claims—control local Wiz smart lights—with a few expected cautions around installing an unpinned Python dependency and allowing the agent to change a physical device state.
Findings (3)
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.
Checks for instructions or behavior that redirect the agent, misuse tools, execute unexpected code, cascade across systems, exploit user trust, or continue outside the intended task.
await light.turn_on(PilotBuilder(brightness=255)) ... await light.turn_off() ... await light.turn_on(PilotBuilder(rgb=(red, green, blue), brightness=255))
The script can directly change the state of a local smart light. This is the advertised purpose, but it is still a real-world device action that should be user-directed.
while True:
# Check duration
if duration > 0 and (time.time() - start_time) > duration:Disco mode stops only when duration is greater than zero and elapsed; a zero or negative duration would keep the flashing loop running until interrupted. The default CLI duration is 10 seconds, so this is a usage caution rather than suspicious behavior.
python3 -m venv venv && source venv/bin/activate && pip install -r requirements.txt
The setup flow installs a Python dependency from requirements.txt. That dependency is purpose-aligned, but the requirements file contains an unpinned package name, so the installed version depends on what the package index serves at setup time.
