reCamera Intellisense
v1.0.1Registers reCamera devices, configures AI detection models/rules/schedules, monitors and clears detection events, fetches event snapshots, and runs manual im...
⭐ 0· 210·1 current·1 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
Name/description (camera registration, detection, captures) aligns with required binaries (python3), local credential store (~/.recamera/devices.json), and included Python scripts that call camera HTTP APIs. No unrelated cloud credentials or surprising requirements are declared.
Instruction Scope
SKILL.md instructions stay within scope: they instruct adding devices, polling events, fetching snapshots, and running the provided CLI/Python scripts. They declare and document the local credential file and warn about plain-HTTP transport and trusted networks. Note: the scripts download images to local paths and write a credential file under ~/.recamera; ensure you are comfortable with those local file writes.
Install Mechanism
Instruction-only skill with bundled Python source; no install spec or remote downloads. Uses only standard-library Python modules and no external package installs are requested.
Credentials
No environment variables or external credentials are requested. The skill stores per-camera tokens in ~/.recamera/devices.json (documented) which is appropriate for device tokens; token format is validated. The number and type of secrets requested are proportionate to the functionality.
Persistence & Privilege
always:false and user-invocable:true. The skill does not request permanent platform-wide privileges. It writes its own credential file (~/.recamera/devices.json) only, which is normal for this use case.
Assessment
This bundle appears to do what it claims — manage local reCamera devices via HTTP and save per-camera tokens locally. Before installing or enabling autonomous execution: 1) review the included Python sources yourself (they are bundled) to confirm behavior; 2) store tokens only for trusted local cameras and set file permissions (chmod 600) as recommended; 3) prefer HTTPS on camera devices or keep the cameras on a trusted network because traffic (images/tokens) is plain HTTP by default; 4) be aware the scripts will download image files to local paths you specify (ensure you trust those files and destinations); 5) if you plan to allow autonomous invocation by the agent, consider limiting that capability or monitoring its actions since autonomous access increases blast radius even for coherent skills.Like a lobster shell, security has layers — review code before you run it.
latestvk9794km24xb4grpqqa2bg3ytd982e262
License
MIT-0
Free to use, modify, and redistribute. No attribution required.
Runtime requirements
📷 Clawdis
Binspython3