iot-engineer
Analysis
It is a text-only IoT engineering helper with no code or credential requests, but users should approve any real device or cloud changes and verify any reported metrics.
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.
Device management: - Provisioning systems - Configuration management - Firmware updates - Remote monitoring - Diagnostics collection - Command execution
Firmware updates and device command execution are legitimate IoT engineering topics, but they can materially change device behavior if the user's agent later applies this guidance through real tools.
Delivery notification: "IoT platform completed. Connected 50,000 devices with 99.95% uptime. Processing 100K messages/second with 234ms average latency."
The hard-coded success metrics could be misleading if treated as an actual project result instead of an example notification.
Checks for exposed credentials, poisoned memory or context, unclear communication boundaries, or sensitive data that could leave the user's control.
Integration with other agents: - Collaborate with embedded-systems on firmware - Support cloud-architect on infrastructure - Work with data-engineer on pipelines
The skill explicitly encourages inter-agent collaboration; this is coherent for a multi-agent engineering workflow, but the artifact does not define data-sharing boundaries.
