ReefBeat

Control and monitor Red Sea ReefBeat aquarium equipment directly over the local HTTP API — no cloud required. Supports ALL actions on ALL devices — ReefLED G...

This skill is internally consistent with its purpose, but be aware of what it does: it will scan your local subnet and send HTTP requests to devices it finds. That is necessary to discover and control ReefBeat hardware, but could trigger network monitoring or affect devices you do not own. Before installing/running: 1) run discovery with an explicit subnet instead of letting it infer your interface if you are on a multi-network host; 2) avoid issuing commands like POST /firmware, POST /reset, or POST /resume unless you intend the change (these endpoints can reset or update devices); 3) use the tool only on trusted private networks and target only devices you control; 4) if you need additional assurance, inspect the script locally (scripts/reefbeat.py) — it performs only local HTTP probes and does not exfiltrate data to external services.

Type: OpenClaw Skill Name: reefbeat Version: 1.0.3 The skill provides a CLI for local control of Red Sea ReefBeat aquarium hardware. The script `scripts/reefbeat.py` implements a network discovery feature that performs multi-threaded HTTP probing across the local subnet, which is a risky capability. Additionally, the script allows for arbitrary HTTP requests (GET/POST/PUT/DELETE) to be sent to any endpoint on a target IP, creating a potential for SSRF or unauthorized device manipulation if the agent is misdirected. While these functions are aligned with the stated purpose of device management, they constitute high-risk network behaviors according to the analysis criteria.