launch-review
Skill16 starsChanged 47 days agoMITView on GitHub
Tool manual under launch-film (measuring a render and studying a reference film). Review a rendered launch film like a demanding creative director, then drive the v1 to v2 loop. Measures rhythm, static runs, cuts against the beat grid, loudness, true peak and voice pace with a script, then applies an eye checklist for continuity at every cut, legibility, brand, real UI, claims and differentiation. Writes a gap list and a scorecard; nothing ships on numbers alone. Use on every render, and on a reference film to learn from it, for "review the video", "check the film", "what is wrong with this cut", "study this reference".
4 other projects use a version of this.
Adopted by
Most recently taken up by
- runbooklabhq/indie-launch-skills-litetheir own version, first seen Oct 25, 2026
- kritikosgns-web/indie-launch-skills-litetheir own version, first seen Oct 20, 2026
- 2104178150-ai/megaphonetheir own version, first seen Oct 20, 2026
- anthropics/claude-for-legaltheir own version, first seen May 15, 2026
Other versions4 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 4
- anthropics/claude-for-legal★ 9.5ksame name
- 2104178150-ai/megaphone★ 5same name
- kritikosgns-web/indie-launch-skills-lite★ 0same name
- runbooklabhq/indie-launch-skills-lite★ 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 repository11 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- launch-brandSkill
- launch-filmSkill
- launch-mixSkill
- launch-motionSkill
- launch-scoreSkill
- launch-soundSkill
- launch-storySkill
- launch-voiceSkill
- launch-worldSkill
The file
We split this skill into the rules it gives an agent
1 rule. 0 are common, 0 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 4 edited versions we read keep these.
0
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 22
Read filmstrip.jpg top to bottom as time.
“Common” is measured: kept by at least 6 in 10 of the 4 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Launch review
Tool manual under
launch-film. Start atskills/launch-film/SKILL.md: it holds the core, the hook-plus-body template and the lessons. Where this page differs,launch-filmwins.
The standard for motion: supreme motion with room to breathe, clean type, fast, on brand, and different from what everyone ships. An early cut can pass every number and still read as basic, so this skill leads with the eye and uses numbers to point at problems.
1. Measure
python3 skills/launch-review/scripts/review.py film/renders/<hook>.mp4 film/review/<hook>-v1 --bpm 120 --words <words.json>Writes report.md (pass or warn per target), filmstrip.jpg (2 fps) and contact.jpg (12 frames). The same script studies a reference: skills/launch-review/scripts/study_reference.sh <url> <out-dir> <bpm> downloads it, grids it, transcribes it and runs the report. Keep the notes; never commit third-party video.
2. Look
Read filmstrip.jpg top to bottom as time. Then check the pair of frames around every cut and transition (npx -y hyperframes@0.8.77 snapshot --at <cut-0.1>,<cut+0.2> --describe false in film/ after building that hook).
| Area | Pass when |
| Continuity | no scene settles before its cut; the outgoing element is still moving and the incoming one arrives in motion |
| One world | transitions come from your brand's world (a material, a motif, the logo, the product), not a stock crossfade, blur-crossfade, zoom-through, push-slide or flash |
| Scale range | at least 1 macro moment (a UI element or typed text filling the frame) and 1 wide system moment |
| Legibility | every word readable at phone size for at least 0.6 s; nothing under 28 px at 1080p except UI detail that is not meant to be read |
| Breathing room | 1 idea per frame; empty space is intentional; nothing touches the frame edge by accident |
| Brand | only the roles in brand/brand.json; the display font; accent on grounds and single elements, not long type; the logo as on the site |
| Real product | UI comes from real screenshots or recordings; any mock UI is labelled as sample |
| Claims | every number is true and provable; the owner has cleared it for public use |
| Sound | every weighted event has a sound from the palette; the logo lands in near silence with its sting; the voice is intelligible over the bed |
3. Differentiation audit
Answer in writing:
- Logo swap: could a competitor put their logo on this film without changing anything else? If yes, it fails.
- Stock moves: list every move that also appears in the HyperFrames catalog defaults or in the reference films. Each one must be turned into your brand's version or cut.
- Signature count: at least 2 of your signatures (your world transition, glass over motion, the logo build, the sonic logo, a product-specific morph) carry a key moment.
4. Gap list and v2
Write gaps.md beside the report: every problem as "at mm:ss, what is wrong, why it matters, the fix". Order by impact on the viewer. Fix, re-render, run steps 1 to 3 again into a -v2 folder, and deliver both versions with the gap list so the owner sees what changed.
Scorecard
Score 1 to 5 each: hook (first 2 s), continuity, rhythm, typography, product clarity, brand, sound, differentiation. Ship at 4 or above everywhere; anything at 3 goes back into the gap list. The owner's taste overrides the scorecard: ask what read wrong rather than guessing.
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.