promo-reel
Skill0 starsChanged 6 days agoMITView on GitHub
Turn a short brief into a branded vertical promo video (15 or 30 sec, 1080x1920) with the Motion Plus Remotion template. Use for campaign, offer, product or bonus promo videos, Reels, Shorts and TikToks.
- Installs packages
In this repository6 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- cartoon-studioSkill
- motion-designSkill
- review-loopSkill
- talking-head-editSkill
- word-captionsSkill
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 0 are distinctive, and 4 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 12
Read studio/brands/<brand>.json before writing anything.
- Very specific: line 17
If the brand does not exist, create studio/brands/<id>.json with the same shape and register it in studio/brands/index.ts.
- Very specific: line 42
Check every on-screen string and the voiceover script against bannedPhrases.
- Very specific: line 51
If Remotion cannot download Chrome, set REMOTION_CHROME=/path/to/chrome-headless-shell.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Promo Reel
Builds a vertical promo from studio/briefs/<name>.json plus a brand preset in studio/brands/.
Scenes: Hook → Offer (animated number) → Points → CTA, over an ambient branded background.
1. Load the brand
Read studio/brands/<brand>.json before writing anything. Every brand has:
colors,locale(e.g.en,tr),cta,ctaLead, optionalmascot(path understudio/public/)bannedPhrases: never put these on screen or in a voiceoverrules: house rules for this client; treat them as hard requirements
If the brand does not exist, create studio/brands/<id>.json with the same shape and register it in studio/brands/index.ts.
2. Write the brief
{
"brand": "demo",
"duration": 15,
"hook": "Write a brief get a video",
"offer": { "label": "Render time", "value": 15, "prefix": "", "suffix": " sec" },
"points": ["Brand presets", "Word-timed captions", "Built-in quality check"],
"cta": "optional override of brand.cta",
"ctaLead": "optional override of brand.ctaLead",
"terms": "small print, quoted exactly as the client wrote it",
"useMascot": true,
"voice": "audio/voice.mp3",
"music": "audio/music.mp3",
"musicVolume": 0.18,
"captions": [],
"emphasize": ["15"]
}Rules:
- Hook: max 6 words, a promise or a question. It is visible on frame 0 (the first frame is the cover on mobile).
- Points: 2-4 items, max ~5 words each.
- Numbers, prices, percentages and terms come from the client's source text, never invented. If the user gives tiers, use the example they ask for.
- Check every on-screen string and the voiceover script against
bannedPhrases. - Audio files go in
studio/public/audio/. For word-timed captions of a voiceover, use theword-captionsskill and paste the result intocaptions.
3. Render
cd studio && npm install # first time only
bash ../scripts/render.sh briefs/<name>.jsonFor both cuts of a campaign, make <name>-15.json and <name>-30.json; the template scales every scene to duration.
If Remotion cannot download Chrome, set REMOTION_CHROME=/path/to/chrome-headless-shell.
4. Review before delivering
render.sh runs scripts/check_export.sh, which prints size/fps/duration and writes a contact sheet, a phone-size sheet and the first frame to studio/out/review/. Open them and run the review-loop skill. Deliver only 1080x1920, 30 fps.
Changing the look
Scenes live in studio/src/scenes/. Follow the motion-design skill: ease-out entrances, ease-in exits, one accent color, primary + secondary + ambient motion layers, no linear movement.
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.

