make-product-video
Skill4 starsChanged 4 months agoMITView on GitHub
Make a narrated product video from a working app, such as a demo, walkthrough, sizzle reel, launch video or feature announcement. Picture comes from agent-browser recordings or Remotion; voiceover (Eleven v4), music and sound effects come from the ElevenLabs CLI. Covers three styles, v4 voice direction, mixing and delivery.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- aintoniodev/autoskillingtheir own version, first seen Aug 29, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- aintoniodev/autoskilling★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository5 other files it gives its agents.
- AGENTS.mdAGENTS.md
- analyze-video-editingSkill
- find-brollSkill
- record-agent-browser-demoSkill
- video-editingSkill
The file
Files
Make a product video
This skill helps produce narrated product videos. It leans on two other skills:
record-agent-browser-demo(this repository) for recording real UI with theagent-browserCLI.video-editing(this repository) for contact sheets, the Remotion starter (video_workbench.py init-motion) and validating the final file (video_workbench.py validate).
Styles
There are three. They differ in where the picture comes from, how long they run, and what drives the timing.
| Style | What the viewer sees | Typical length | Picture source | Timing follows |
| Walkthrough | Whole real screens, flows played start to finish, a title card per act | 2 to 6 minutes | Screen recordings of the running app | Each recorded segment is sped up or held to fit its narration line |
| Sizzle reel | Real screens inside a designed frame, camera moves, a few title lines | 60 to 90 seconds | Screen recordings composited in Remotion | Scenes sit on the music's phrases; voice lines are placed in them |
| Element film | One thing at a time, centered on a plain background: a line of text or a single UI element lifted out of the product | 20 to 60 seconds | The element rebuilt as React/SVG in Remotion | Every animation is keyed to a word in the voiceover |
references/styles.md describes how each one is built.
Order of work
- One sentence. What the viewer should believe afterwards, and who the viewer is.
- Script. About 150 to 160 spoken words per minute. Share it with the user.
- Silent cut. Picture only: a rough Remotion render, or a contact sheet of recorded takes for a walkthrough. A sizzle reel also gets a draft music cue here, since its scenes cut on the music's phrases.
- Voice sample. 15 to 20 seconds of the script in the chosen voice, for the user to hear.
- Voiceover.
scripts/voiceover.pygenerates it and checks it against the script by transcription. - Re-time the picture to the voiceover.
- Music at the final length.
- Mix and master with
scripts/mix.py. - Deliver the master and any smaller copies the destination needs.
Agents can't hear the result. The user's ears are the check on voice, music and effects, so send them the voice sample and the first full mix.
Voice
Voiceover uses eleven_v4. v4 has no speed setting and no SSML; pace, pauses and delivery are written into the text as tags. references/voice-music-sfx.md covers tags, music and sound effects.
Timing
Timings come from the generated audio. voiceover.py writes each clip's length to manifest.json and its word times to <id>.words.json. Keep scene times, clip start times and the total length in one timeline file, and generate both the picture's timing and the mix file from it.
Scripts
Plain Python 3, in this skill's scripts/ folder. They need ffmpeg; voiceover.py also needs the elevenlabs CLI, logged in. Each docstring describes its input file.
python3 scripts/voiceover.py vo.json vo/ # generate, transcribe, check, write word timings
python3 scripts/mix.py mix mix.json # stems and premix
python3 scripts/mix.py master mix.json picture.mp4 output/film.mp4 # loudness, limiter, mux
python3 scripts/fit_size.py output/film.mp4 output/film-10mb.mp4 --mb 10 # a copy under a size limitreferences/mix-and-delivery.md has starting levels, validation and file sizes.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

