Who it is forA creator or editor with a long interview recording who needs a short vertical clip for Instagram Reels and has no time to edit by hand.
The problemManual trimming, reframing and export for a vertical social clip takes time, and the result is easy to get wrong on duration or aspect ratio.
The outcomeA Reels-ready MP4 that is about 60 seconds, 1080x1920, with a probe and a contact sheet the agent has checked.
What you need first
- ffmpeg and ffprobe on your PATH (run `npx ffmpeg-skill doctor` to check)
- python3 on your PATH (on Windows, `python` or the `py` launcher may be needed instead)
- Node.js, for `npx ffmpeg-skill`
- A coding agent such as Claude Code, Cursor or Codex, or any MCP client
Steps
- Install the skill with
npx ffmpeg-skilland check the machine withnpx ffmpeg-skill doctor. - Set
S=~/.claude/skills/ffmpeg-skill/scripts, then measure the source withpython3 $S/probe.py input.mp4 --compact. - Keep the chosen parts with
python3 $S/cut.py input.mp4 --segments 0:45-3:10,5:00-6:30. (inferred, check the README) - Preview the fit with
python3 $S/fit.py input.mp4 --duration 60 --aspect 9:16 --dry-run, then run it without--dry-runusing--fit crop. - Export with
python3 $S/export.py input.mp4 --preset reels --jsonand check the result withcheck.py --platform reels.
Prompt for your agent
Using the ffmpeg-skill repo, take <interview file> and keep 0:45-3:10 and 5:00-6:30, make it exactly 60 seconds at 9:16 for Reels, and export it. Expected output: a Reels MP4 of about 60 seconds at 1080x1920. Verify the duration and resolution with probe.py before you report it done.
Caveat. The segment times and the 60-second target are your choices, and the skill does not decide which parts of the interview are worth keeping.
Get 5 new use cases every morning. Free, one short email, unsubscribe anytime.
Get them freeShare: X LinkedIn Hacker News Email Copy link
Disclaimer
Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page