video-debug

name	video-debug
description	Use when the user references a video, screencast, screen recording, or any path ending in .mp4, .mov, .webm, .mkv, or .gif — especially when asking to debug a UI bug, visual glitch, or reproduction recording. Extracts key frames via ffmpeg scene detection so the agent can visually inspect what went wrong.
allowed-tools	["Bash","Read"]

Video Debug Protocol

When the user provides a path to a video file (.mp4, .mov, .webm, .mkv, or .gif), follow this protocol.

Step 1: Extract frames

Run the extractor against the video path the user gave you:

bash scripts/extract.sh <video-path>

The script will:

1. Verify ffmpeg is installed, and if not, offer to install it (you may need to relay a [y/N] prompt to the user).
2. Probe the video's duration, resolution, and estimated scene-change count.
3. Decide whether the video is "small enough to process directly" or "large enough to need a strategy."

Step 2: Handle large videos

If extract.sh exits with code 10, the video is large (currently: duration > 60 seconds). The script will have printed a single JSON line to stdout with this shape:

{"large": true,