screen-recorderlisted

Records short videos of specific page sections using Playwright's `recordVideo` API, plays scripted interactions (hover, click, focus, scroll, keypress), crops the output to a target element via `ffmpeg`, and saves a `.webm` (or `.mp4` / `.gif`) artifact to `.agent/recordings/`. Use when a still screenshot cannot prove the change — verifying a View Transition, a Motion `layout` morph, a hover stagger, a scroll-driven timeline, an `@starting-style` entry, or any multi-frame interaction. Called by the `animations` skill to validate a generated animation, by the `ux` skill to capture an interaction the reviewer cannot read from code, and by the `reviewer` agent to attach evidence to PR comments on motion-heavy diffs. Triggers on "record this interaction", "capture this animation", "video of this section", "validate the transition visually", "screen recording", "/screen-recorder".
mthines/agent-skills · ★ 4 · Web & Frontend · score 83

Install: claude install-skill mthines/agent-skills

# Screen Recorder Produces a short `.webm` clip of a specific page section so an agent — or a reviewer reading a PR — can see motion that a static screenshot hides. Not a test suite, not a permanent fixture: every recording is a throwaway artifact written to `.agent/recordings/` for one-shot visual review. > **This `SKILL.md` is a thin index.** Detailed rules live in > [`rules/*.md`](./rules) and load on demand. Literal Playwright and > `ffmpeg` boilerplate the skill emits lives in > [`templates/*.md`](./templates). Do not preload everything — load only > what the current phase asks for. --- ## When to use Reach for this skill when **any** of the following is true: - A diff changes animation, transition, or interactive motion code (`@keyframes`, `transition`, `View Transitions`, Motion `layout`, `@starting-style`, scroll-driven timelines). - A still screenshot would not falsify the bug or feature claim — the proof requires at least two frames. - A reviewer asks "what does this look like?" on a PR whose answer is a moving image, not a description. - The `animations` skill has produced an animation and wants visual evidence it hits 60 fps and respects `prefers-reduced-motion`. - The `ux` skill flagged a flow (drag, focus ring, hover reveal, expanding nav, modal entrance) where the asserted UX claim is about timing, not layout. Do **not** reach for this skill when: - A static screenshot is sufficient — use the `visual-test` agent. - The task is to author a