agentleFS
Malik1942Malik1942/screen-recording/SKILL.md

screen-recording

Skill2 starsChanged 3 months agoMITView on GitHub

Use when screen-recording a product demo from a script or shot list — a native app in the iOS Simulator, a website in the browser, or a Figma prototype — or when footage needs auto-zoom on interactions and a visible cursor navigating the UI. Also when takes come out contaminated (permission dialogs, wrong language, wrong tab), empty (0 bytes), or mysteriously longer than planned.

4 other projects use a version of this.

Adopted by

Most recently taken up by

  • Other versions4 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 4

    1. github/awesome-copilot★ 41ksame name
    2. vellum-ai/vellum-assistant★ 1.5ksame name
    3. codeonym-org/codeonym-arch-design★ 0same name
    4. codeonym-oss/design-skills★ 0same name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

The file

We split this skill into the rules it gives an agent

1 rule. 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 3 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    No take before staging is complete and one-time dialogs are burned.

    line 27

“Common” is measured: kept by at least 6 in 10 of the 3 edited versions of this file we could read. “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-recording

Script-driven product capture — iOS Simulator, website, or Figma prototype — with auto-zoom and cursor navigation derived from measured interaction times, never hand-guessed. The synthetic cursor comes from the compositor, so it works identically on every surface.

The user's script must specify, per scene: start state, the interaction to show, the payoff to read, and the data that must exist. If it doesn't, get those four fields per scene before capturing anything (the companion product-film skill ships a full fill-in template in its references/writing-the-script.md).

Read references/capture-protocol.md before rolling anything. It has the staging checklist, the per-take protocol, and the derivation rule.

COMPANION for editing/compositing: the product-film skill supplies the downstream tools (diffscan.swift/diffscan2.swift for measuring takes, composite2.swift for rendering zoom + cursor). This skill produces their inputs; capture itself works standalone.

The loop

  1. Parse the user's script → shot list (start state, actions, end state, readable moments). Seed any missing product data first.
  2. Pick the capture surface (protocol §0: simulator / website / Figma proto — each has its drive+record pair) AND the presentation path by form factor: portrait/phone content → mobile path (mockup, dot cursor); landscape/desktop content → desktop path (FILL=1 full-bleed, arrow cursor, capture must be canvas-aspect 16:9). Stage it: sim = locale+status-bar+privacy+burned dialogs; web = logged in, banners dismissed, viewport sized to the aspect; proto = presentation mode, Fit zoom.
  3. Per scene: dry-run for coordinates → roll detached to a durable dir → drive with deliberate pacing → SIGINT → verify the end frame.
  4. Measure with product-film's diffscan (mobile) / diffscan2 (desktop) → real interaction times.
  5. python3 scripts/autoplan.py taps.json (add --desktop on the desktop path) → composite2 camera plan + cursor/ripple args (zoom punches arrive 0.3s before each tap; cues complete before the UI transition).

Non-negotiables

  • No take before staging is complete and one-time dialogs are burned.
  • Dry-run before every recorded flow; verify field focus before typing.
  • Desktop/web film takes: sckrecord (ScreenCaptureKit) only — never screencapture -v — with the mandatory pre-roll health gate (protocol §0).
  • One pointer contract per film (synthetic arrow OR recorded cursor), decided before roll 1 and honored in every take and recapture; same stage (window, region, scale, recorder) for every act.
  • The recorded viewport must contain every payoff the script promises — verified on a dry-run still of the end state, before rolling.
  • Record to durable storage; a take without a verified end frame isn't done.
  • Trim only from measured times — tap latency makes plans fiction.
  • A contaminated take (dialog, toast, wrong state) is discarded and re-rolled, never rescued in the edit.
  • Pass the udid explicitly on every drive command when more than one simulator exists.

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.