Camsnap

ReviewAudited by ClawScan on May 1, 2026.

Overview

Camsnap’s artifacts are coherent for a camera-capture CLI skill, with expected but privacy-sensitive camera credential and media access to handle carefully.

Before installing, confirm you trust the Homebrew source, configure only cameras you are allowed to access, protect camera credentials and saved clips, and review any `watch --action` command before running it.

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.

What this means

Anyone using the configured skill may be able to capture images or clips from configured cameras, depending on how the agent is used.

Why it was flagged

The skill expects camera connection details and credentials so it can access camera streams. This is purpose-aligned, but it grants access to sensitive live camera views and may store credentials locally.

Skill content
Config file: `~/.config/camsnap/config.yaml`
- Add camera: `camsnap add --name kitchen --host 192.168.0.10 --user user --pass pass`
Recommendation

Use least-privilege camera accounts, protect the config file, avoid sharing captured media unintentionally, and avoid putting real passwords into command history if the tool offers a safer prompt or config method.

What this means

A poorly chosen motion action could run longer than intended or trigger unwanted follow-up behavior when motion is detected.

Why it was flagged

The documented motion-watch workflow includes an open-ended action hook. This appears related to the stated motion-event purpose, but the artifact does not define the action’s limits.

Skill content
Motion watch: `camsnap watch kitchen --threshold 0.2 --action '...'`
Recommendation

Only use explicit, reviewed actions, prefer harmless test actions first, and avoid letting the agent invent or run destructive actions without approval.

What this means

Installing the skill depends on a third-party package source for the actual camera-capture binary.

Why it was flagged

The runnable implementation is installed from an external Homebrew tap. This is normal for a CLI-based skill, but users must trust that package source.

Skill content
brew | formula: steipete/tap/camsnap | creates binaries: camsnap
Recommendation

Install only if you trust the Homebrew tap and Camsnap project, and verify the installed binary and dependencies such as `ffmpeg` are expected.