agentleFS
Sign inStart free
sonichisonichi/sutando/skills/screen-record/SKILL.md

screen-record

Skill396 starsChanged 6 months agoMITView on GitHub

Start or stop a screen recording of the Mac via ffmpeg. Use when the user asks to record/capture their screen to a video file (a demo, a repro, a walkthrough) — not for a single still screenshot (use macos-tools screen capture for that).

  • Installs packages

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. Distinctive:

    Start and stop screen recording using ffmpeg.

    line 8
  2. Very specific:

    If argument is start:

    line 19

≈ “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

Screen Record

Start and stop screen recording using ffmpeg.

Usage: /screen-record start or /screen-record stop

When to use

The user asks to record the screen to a video over time (demo, bug repro, walkthrough). For a single still frame, use the screen-capture path instead.

On activation

If argument is start:

python3 skills/screen-record/scripts/record.py start

If argument is stop:

python3 skills/screen-record/scripts/record.py stop

Output & failure modes

  • Done = a .mov written by record.py to /tmp/sutando-recording-<ts>.mov (it prints the path on stop).
  • start while already recording → the script no-ops and returns the existing pid + path; a stale PID file (previous run crashed) is detected and cleared, so it self-heals rather than wedging; stop with nothing running → no-op.
  • ffmpeg missing at /opt/homebrew/bin/ffmpeg (hardcoded in three places — record.py:59 device-listing, :152 the recording call, :204 the audio check. Apple Silicon brew prefix; on an Intel Mac brew install ffmpeg lands in /usr/local and the skill stays broken until all three are fixed — patching only the recording call still fails at device-listing before recording starts). No frames / black video → the invoking terminal lacks macOS Screen Recording permission (same grant the screen-capture server uses).

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.

Check your setup, free