agentleFS
lordmaculordmacu/nexo-rs/skills/rtsp-snapshot/SKILL.md

RTSP Snapshot

Skill8 starsChanged 7 months agoApache-2.0View on GitHub

Capture JPG frames or short MP4 clips from RTSP/HTTP IP cameras via ffmpeg.

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 1 is distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Use to grab stills or short clips from IP security cameras (RTSP, HTTP HLS) so Kate can report what is happening in a scene or store …

    line 11
  2. Distinctive:

    Prefer TCP transport to avoid packet loss over Wi-Fi/VPN

    line 49

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

RTSP Snapshot

Use to grab stills or short clips from IP security cameras (RTSP, HTTP HLS) so Kate can report what is happening in a scene or store evidence. All output stays under a sandbox dir (RTSP_SNAPSHOT_OUTPUT_ROOT, default $TMPDIR).

Use when

  • "take a snapshot from the garage camera"
  • "record 30s from the doorbell now"
  • "is there motion? capture and send me a snapshot"

Do not use when

  • The camera is not reachable over LAN/public RTSP/HTTP URL
  • Necesitas streaming continuo o WebRTC
  • Clips > 5 minutes (hard cap by design)

Tools

status

ffmpeg bin + sandbox + limits.

snapshot { url, output_path, transport?, width? }

  • url — rtsp://user:pass@host/stream, rtsps://, http://, https:// (NO file://, NO concat:)
  • output_path — must stay under the sandbox root; .jpg recommended
  • transport — tcp (default, estable sobre NAT) o udp
  • width — resize manteniendo aspecto

Returns {url, output_path, bytes, transport}.

clip { url, output_path, duration_secs, transport? }

  • duration_secs 1..=300
  • Uses stream copy (no re-encode) — very fast

Returns {url, output_path, bytes, duration_secs, transport}.

Execution guidance

  • Prefer TCP transport to avoid packet loss over Wi-Fi/VPN
  • Credentials are inline in URL (rtsp://user:pass@host/...); store them in 1Password and read them with read_secret when reveal is enabled
  • Output path outside sandbox → -32034 IoError; adjust operator config
  • Unreachable camera → -32032 NonZeroExit with ffmpeg stderr included
  • Motion detection is out of scope here — chain with a vision-enabled pipeline

Pipelines

Snapshot + vision

1. rtsp-snapshot.snapshot { url, output_path: "/sandbox/cam1.jpg" }
2. (futuro) vision-lm.describe { path: "/sandbox/cam1.jpg" }

Clip + transcribe

1. rtsp-snapshot.clip { url, output_path: "/sandbox/ring.mp4", duration_secs: 30 }
2. video-frames.extract_audio { path, output_path: "/sandbox/ring.wav", codec:"wav", mono:true, sample_rate:16000 }
3. openai-whisper.transcribe_file { file_path: "/sandbox/ring.wav" }

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.