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

How to make a second style edition of a release video with Motion Video Skill

Re-render an existing release video in the glass keynote style without touching the first edition.

  • Content
  • Intermediate
  • 90 minutes
  • From the README
  • Claude Code
  • Codex
  • Cursor
  • Gemini CLI

Who it is forA creator who already made a comic-style release video and wants a calmer premium cut of the same release.

The problemA restyle could overwrite the first edition, and it is unclear how to keep both cuts.

The outcomeA new project directory with a glass keynote edition, while the original comic edition stays intact.

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

  1. Install the skill with npx skills add bestagentkits/motion-video-skill.
  2. Read the glass keynote style reference at skills/motion-video/references/style-glass-keynote.md.
  3. Create a new project directory with mkdir -p assets/videos/my-video, using a name different from the first edition.
  4. Ask your agent to rebuild the video from the same script in the glass keynote style.
  5. Compare the two renders and confirm the first edition's files are unchanged.

Prompt for your agent

Using the motion-video skill from bestagentkits/motion-video-skill, create a glass keynote edition of <release name> in a new project directory named <new-project-name>, leaving the existing comic edition untouched. Expected output is a rendered 1920×1080 30 fps video in the new directory. Verify that the original project directory has no changed files.

Caveat. The README notes the 144 s glass keynote edition exists, but its working project is not bundled, so you rebuild it from your own script.

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