browser-use/video-use
browser-use's video-editing skill for coding agents: word-level transcripts become a ~12KB text file the agent cuts against — filler removal, subtitles, color grading — rendered via FFmpeg with self-checks.
**The gist** video-use lets a coding agent edit video by working over text instead of frames: **ElevenLabs Scribe** produces word-level timestamps packed into a **~12KB markdown file**, with PNG filmstrips generated only at decision points. Built-ins cover **filler-word removal**, subtitles, color grading, **30ms audio fades** at cuts, and animation overlays via Remotion or Manim.
**Why it matters** The token economics are the interesting part: the text-first representation sidesteps frame-by-frame analysis the project pegs at tens of millions of tokens, and its **render-then-self-evaluate loop** (max **3 fix iterations**) is a transferable pattern for any agent task with expensive outputs.
**The gist** video-use lets a coding agent edit video by working over text instead of frames: **ElevenLabs Scribe** produces word-level timestamps packed into a **~12KB markdown file**, with PNG filmstrips generated only at decision points. Built-ins cover **filler-word removal**, subtitles, color grading, **30ms audio fades** at cuts, and animation overlays via Remotion or Manim. **Why it matters** The token economics are the interesting part: the text-first representation sidesteps frame-by-frame analysis the project pegs at tens of millions of tokens, and its **render-then-self-evaluate loop** (max **3 fix iterations**) is a transferable pattern for any agent task with expensive outputs. **Watch out** It needs an **ElevenLabs API key** and **FFmpeg**, and install is still clone-and-symlink into your skills directory rather than a package. Cut quality rests on transcription accuracy, so noisy or heavily multi-speaker audio will degrade results.