Who it is forA video editor or developer who has a motion video project and needs proof the music and speech levels are right before publishing.
The problemMusic that drifts off the beat or sits too loud under speech is easy to miss when watching a render.
The outcomeReports showing splice lag per segment, music level under speech versus the gaps, and the beat grid used.
What you need first
- Node.js 20+
- Python 3.10+ with numpy and scipy
- ffmpeg and ffprobe on PATH
- The multix CLI, authenticated with a Gemini key and an ElevenLabs key
- npx --yes [email protected] (no install step needed)
Steps
- Install the skill with
npx skills add bestagentkits/motion-video-skill. - Install the Python requirements, numpy and scipy, and confirm ffmpeg and ffprobe are on PATH.
- Run
python skills/motion-video/scripts/verify-arrangement.pyon the project and read the per-segment splice lag; it exits 1 on drift. (inferred, check the README) - Run
python skills/motion-video/scripts/measure-mix-balance.pyon the project and check music sits about 4 to 6 dB under speech. (inferred, check the README) - Run
python -m unittest discover -s skills/motion-video/scripts/teststo confirm the checker itself passes.
Prompt for your agent
Using the motion-video skill from bestagentkits/motion-video-skill, run verify-arrangement.py and measure-mix-balance.py on the project at <project-path> and report each music segment's splice lag and the music-to-speech level difference. Expected output is a short pass or fail report. Verify that every segment is within ±2 ms of its target beat and that music is about 4 to 6 dB under speech.
Caveat. The README does not document the command-line arguments for the Python scripts, so check each script's usage before running it on a real project.
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