Camsnap 1.0.0
Analysis
The skill’s instructions match its camera-capture purpose, but users should notice that it installs an external binary, uses camera credentials, and documents an optional motion action hook.
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.
brew | formula: steipete/tap/camsnap | creates binaries: camsnap
The skill relies on installing an external binary from a Homebrew tap; this is expected for a CLI-based camera tool, but users should trust that source before installing.
Motion watch: `camsnap watch kitchen --threshold 0.2 --action '...'`
The documented motion-watch command includes an open-ended action parameter, which could automate follow-up behavior if the user supplies an action.
Checks whether tool use, credentials, dependencies, identity, account access, or inter-agent boundaries are broader than the stated purpose.
Add camera: `camsnap add --name kitchen --host 192.168.0.10 --user user --pass pass`
The setup example uses camera usernames and passwords; this is purpose-aligned for RTSP/ONVIF access, but it grants access to private camera streams.
