Who it is forA course creator or small product owner launching a new cohort or offer who needs a video without editing software.
The problemProducing a launch video normally means editing tools, motion design skills and a lot of time.
The outcomeA 30 to 45 second launch video rendered from code, with on-brand colours and fonts and text taken from facts you approved.
What you need first
- Claude Code, with Opus 5.5 selected via /model
- Install the skills with npx skills add charlie947/motion-graphics-skills
- Run brand-intake first so brand.md and MOTION.md exist
- For MP4 export: HyperFrames (npx skills add heygen-com/hyperframes) or ffmpeg plus Chrome
- For reel-export and loop-cover measuring: ffmpeg, ffprobe and Python 3 as listed in the README
Steps
- Run
npx skills add charlie947/motion-graphics-skills - Open Claude Code, pick Opus 5.5 with
/model, and runbrand-intakefirst - Say: "Make a launch video for my new cohort." Replace the example with your own offer details
- Check the draft against your approved facts list and ask for edits such as "Slow down the second scene."
- Export to MP4 with HyperFrames, after running
npx skills add heygen-com/hyperframes
Prompt for your agent
Using the charlie947/motion-graphics-skills repo in Claude Code, run the launch-video skill for <product or cohort name> using only the facts in <facts file>. Expected output: a 30 to 45 second launch video in the brand defined in brand.md. Verify that every name, date and number on screen matches the facts file.
Caveat. The skills need Claude Code on Opus 5.5 and a brand setup first, so a non-developer will still need to install Claude Code before running them.
Every Monday: the 5 hottest repos and exactly how to use them. Free, one email a week, 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