DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to turn a talking-head video into a captioned TikTok with Ffmpeg Skill

One render command crops to 9:16, burns in your cue text and normalizes loudness for TikTok.

  • Content
  • Intermediate
  • 30 minutes
  • From the README
  • Claude Code
  • Cursor
  • Codex

Who it is forA creator with a talking-head recording and a text file of caption cues, who wants a finished TikTok without learning FFmpeg.

The problemCaptioning, reframing, loudness and platform export are separate steps, and the caption text has to sit clear of the app's own UI.

The outcomeA TikTok-ready file with popped captions above the description bar, around -14 LUFS, plus a check report written by the skill.

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

  1. Install the skill with npx ffmpeg-skill and confirm the tools are usable with npx ffmpeg-skill doctor.
  2. Write your caption lines into a cues file, one cue per line, with the text as you want it burned in.
  3. Run python3 $S/render.py talk.mp4 --template tiktok --cues cues.txt, after setting S to the skill's scripts folder.
  4. Find the output next to the input, or use -o to choose another folder, and confirm the check.py result for TikTok.

Prompt for your agent

Using the ffmpeg-skill repo, render <talk video> with the tiktok template and the cues file <cues.txt>. Expected output: a 9:16 TikTok MP4 with captions and a platform check written next to it. Verify the check result and the output resolution before reporting success.

Caveat. The cue text is burned in exactly as written, so the wording and line breaks are your responsibility.

Share: 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