Commercial Motion Film

Business motion film

by echris6 · MIT license · ★ 665 on GitHub

Business motion film cover

Plan, build and quality-check a premium short commercial for a real business (roofing, property, ecommerce, B2B software) using AI-generated footage, code-built motion (HTML/GSAP), selective Three.js and an independent-critic "Gauntlet"…

---
name: business-motion-film
description: Plan, build and quality-check a premium short commercial for a real business (roofing, property, ecommerce, B2B software) using AI-generated footage, code-built motion (HTML/GSAP), selective Three.js and an independent-critic "Gauntlet" loop. Use when asked to make a launch-style / SaaS-style video, business ad, explainer, sample reel or pitch video, or to review and improve one. Encodes motion principles distilled from 28 professional launch films, a quality bar, audio rules and a business-offer playbook.
---

# Business motion film

Make short (15–40s) commercials that look like premium SaaS launch films but sell a real business outcome: explain a service, earn a quote request, follow up on a quote, or refresh an ad. The visuals can be ambitious; the claims must be true.

Read only the reference file your current step needs:

| Step | Read |
|---|---|
| Choosing a vertical, offer, pilot scope, pricing anchors | `references/business-offers.md` |
| Storyboarding and motion design | `references/motion-grammar.md`, then `references/launch-film-notes.md` for concrete moments |
| Building 3D components | `references/three-js-patterns.md`, `templates/component-lab.html`, `templates/projected-overlays.js` |
| A 3D product hero that must move like the real thing (unfolds, closes, reveals) | `references/product-hero-realism.md` |
| Any review round | `references/gauntlet.md`, `references/critic-prompts.md`, `references/quality-bar.md` |

Overview

Make short (15–40s) commercials that look like premium SaaS launch films but sell a real business outcome: explain a service, earn a quote request, follow up on a quote, or refresh an ad. The visuals can be ambitious; the claims must be true.

Manual install (npx, ZIP)
Claude Codenpx skills add echris6/motion-video-kit --skill business-motion-film -g -a claude-code
Claude Code (manual)mkdir -p ~/.claude/skills && curl -sL https://codeload.github.com/echris6/motion-video-kit/tar.gz/255562b04b1e \ | tar -xz -C ~/.claude/skills --strip-components=1 motion-video-kit-255562b04b1e/business-motion-film
Windows (PowerShell)New-Item -ItemType Directory -Force "$HOME\.claude\skills" | Out-Null; Invoke-WebRequest "https://m.agentalley.io/zip/9662bae5da3dc01e5ab7/business-motion-film.zip" -OutFile "$env:TEMP\business-motion-film.zip"; Expand-Archive "$env:TEMP\business-motion-film.zip" -DestinationPath "$HOME\.claude\skills" -Force
Claude.ai / desktopDownload the ZIP and upload it under Settings → Capabilities → Skills.
Codex, Cursor, other agentsPoint them at SKILL.md. The other files are plain text.

Connects with Agent Alley MCP · agentalley.io/mcp

Files included

  • SKILL.md6.9 KB
  • references/11 files · 60.0 KB
  • scripts/7 files · 14.2 KB
  • templates/2 files · 7.1 KB
Read the files here
echris6/255562b21 files
SKILL.md
Show the full text71 lines

Business motion film

Make short (15–40s) commercials that look like premium SaaS launch films but sell a real business outcome: explain a service, earn a quote request, follow up on a quote, or refresh an ad. The visuals can be ambitious; the claims must be true.

Read only the reference file your current step needs:

Step Read
Choosing a vertical, offer, pilot scope, pricing anchors references/business-offers.md
Storyboarding and motion design references/motion-grammar.md, then references/launch-film-notes.md for concrete moments
Building 3D components references/three-js-patterns.md, templates/component-lab.html, templates/projected-overlays.js
A 3D product hero that must move like the real thing (unfolds, closes, reveals) references/product-hero-realism.md
Any review round references/gauntlet.md, references/critic-prompts.md, references/quality-bar.md
Music, sound effects, mix references/audio.md
A worked example end to end references/case-study-alder.md (calm service film), references/case-study-duo.md (Three.js product film)

Non-negotiables

  1. Truth. Never invent testimonials, ratings, completed jobs, diagnoses, savings, warranties or confirmed appointments. A concept film says it is a concept ("Fictional brand · Concept film · AI-generated imagery"). A client film uses the client's approved footage and facts.
  2. Business purpose on mute. A first-time viewer must be able to say what the business does and what to do next, with the sound off, by the end.
  3. Independent judging. The builder never grades its own work. Every component and every full cut goes to a fresh critic that sees only the render, the brief and the references (references/gauntlet.md).
  4. Deterministic motion. Every animated state is a pure function of timeline time: no free-running requestAnimationFrame, Date.now(), unseeded randomness or physics history. Seek to any frame and get the same pixels.
  5. "No bugs" is not "good". Clean, smooth and error-free versions still get rejected for being basic, empty or slow. Measure (scripts/) and judge creatively.

Workflow

1. Brief (15 min)

Write BRIEF.md: business, buyer, the viewer's problem, the single action (CTA), what is provably true, available real assets, length, aspect ratios, brand (palette, type), and what must never be claimed. If the user has no real assets, agree it is a labelled concept.

2. References

Pick 3–6 moments from references/launch-film-notes.md whose mechanism fits the story, e.g. a foreground fly-through, a persistent selected object, or a layered exploded view. If the user supplies reference videos, extract frames (scripts/contact-sheet.sh) and cite exact timestamps. Borrow mechanisms, never layouts, logos or footage.

3. Storyboard before building

One table: time → what the viewer sees → business job of the beat → the transition out, including which object survives it. Rules:

  • 12–15 distinct compositions for a 30s film. Vary scale: macro → wide → overhead → UI close-up → type impact.
  • The lead subject fills 60–85% of the usable frame in feature beats. No small card floating in a big empty field.
  • Every beat has a readable landing, then an accelerating exit. No holds without motion over ~0.6s.
  • Name 3 signature transformations you can describe without effect names, e.g. "the inspection photo becomes the report's hero image".
  • 3D only where it explains something physical or spatial. Typography and UI stay crisp HTML/SVG. Get a quick critic pass on the storyboard itself (chronology, business logic, truthfulness).
4. Assets
  • AI stills: generate the key frame first, then animate it with image-to-video. Prompt as a production brief: lens, light, exposure ("bright, airy, nothing crushed to black"), negative space reserved for type, "no people / no text / no logos / no watermark" when needed.
  • AI video: short (4–5s) clips with restrained camera moves ("a steady gimbal dolly, about 25 cm of travel, preserve the exact geometry, no morphing"). Expect 720p/24fps and interpolate/upscale, which is not native detail. Reject clips whose geometry warps; regenerate rather than hide.
  • Keep a generation ledger: model, prompt, seed, job id, accepted window. Never commit API keys.
5. Build components in isolation

Each custom component (3D scene, report UI, booking flow, logo mark) gets its own lab page (templates/component-lab.html), is rendered to stills plus a short motion proof, and goes through a component Gauntlet round before it joins the film.

6. Assemble

One root timeline; each scene is a sub-composition; Three.js scenes are rendered from the root seek clock; overlays such as labels, pins and leader lines are positioned from projected 3D anchors every frame (templates/projected-overlays.js). Hand objects across scenes at exact pixel coordinates, so the last frame of scene A equals the first frame of scene B for the carried object.

7. Full-film Gauntlet

Render the whole film. Run scripts/frozen-time.sh and scripts/loudness.sh. Send to a fresh critic with references/critic-prompts.md (full-film prompt). Fix the highest-impact items, re-render, and send to a new critic that verifies the previous list item by item. Stop at the quality bar or when gains become cosmetic (usually 3–5 rounds).

8. Audio last, but not an afterthought

Follow references/audio.md: music matched to the buyer's customer and kept well under the effects (lo-fi or warm acoustic for home services); one soft, rumble-free whoosh per real transition; clean UI sounds only on real actions; per-event levels solved in each effect's band (scripts/solve-sfx-gains.py); candidates screened with scripts/sfx-candidates.py. Always deliver a music-only fallback, and isolate complaints with it.

9. Deliver

Master MP4 (1080p60 for motion work), poster frame, contact sheet, editable source, generation ledger, and a Gauntlet ledger (what each critic found → what changed → measured before/after). State limits honestly: what was measured versus listened to, and sampled versus exhaustive review.

Working style the clients in this playbook expected

  • Plan visibly (storyboard), then build without stopping to ask for approval of every step.
  • Report status in one line when working for a long time.
  • Show the work: contact sheets, measured numbers, critic verdicts.
1---
2name: business-motion-film
3description: Plan, build and quality-check a premium short commercial for a real business (roofing, property, ecommerce, B2B software) using AI-generated footage, code-built motion (HTML/GSAP), selective Three.js and an independent-critic "Gauntlet" loop. Use when asked to make a launch-style / SaaS-style video, business ad, explainer, sample reel or pitch video, or to review and improve one. Encodes motion principles distilled from 28 professional launch films, a quality bar, audio rules and a business-offer playbook.
4---
5 
6# Business motion film
7 
8Make short (15–40s) commercials that look like premium SaaS launch films but sell a real business outcome: explain a service, earn a quote request, follow up on a quote, or refresh an ad. The visuals can be ambitious; the claims must be true.
9 
10Read only the reference file your current step needs:
11 
12| Step | Read |
13|---|---|
14| Choosing a vertical, offer, pilot scope, pricing anchors | `references/business-offers.md` |
15| Storyboarding and motion design | `references/motion-grammar.md`, then `references/launch-film-notes.md` for concrete moments |
16| Building 3D components | `references/three-js-patterns.md`, `templates/component-lab.html`, `templates/projected-overlays.js` |
17| A 3D product hero that must move like the real thing (unfolds, closes, reveals) | `references/product-hero-realism.md` |
18| Any review round | `references/gauntlet.md`, `references/critic-prompts.md`, `references/quality-bar.md` |
19| Music, sound effects, mix | `references/audio.md` |
20| A worked example end to end | `references/case-study-alder.md` (calm service film), `references/case-study-duo.md` (Three.js product film) |
21 
22## Non-negotiables
23 
241. **Truth.** Never invent testimonials, ratings, completed jobs, diagnoses, savings, warranties or confirmed appointments. A concept film says it is a concept ("Fictional brand · Concept film · AI-generated imagery"). A client film uses the client's approved footage and facts.
252. **Business purpose on mute.** A first-time viewer must be able to say what the business does and what to do next, with the sound off, by the end.
263. **Independent judging.** The builder never grades its own work. Every component and every full cut goes to a fresh critic that sees only the render, the brief and the references (`references/gauntlet.md`).
274. **Deterministic motion.** Every animated state is a pure function of timeline time: no free-running `requestAnimationFrame`, `Date.now()`, unseeded randomness or physics history. Seek to any frame and get the same pixels.
285. **"No bugs" is not "good".** Clean, smooth and error-free versions still get rejected for being basic, empty or slow. Measure (`scripts/`) and judge creatively.
29 
30## Workflow
31 
32### 1. Brief (15 min)
33Write `BRIEF.md`: business, buyer, the viewer's problem, the single action (CTA), what is provably true, available real assets, length, aspect ratios, brand (palette, type), and what must never be claimed. If the user has no real assets, agree it is a labelled concept.
34 
35### 2. References
36Pick 3–6 moments from `references/launch-film-notes.md` whose *mechanism* fits the story, e.g. a foreground fly-through, a persistent selected object, or a layered exploded view. If the user supplies reference videos, extract frames (`scripts/contact-sheet.sh`) and cite exact timestamps. Borrow mechanisms, never layouts, logos or footage.
37 
38### 3. Storyboard before building
39One table: time → what the viewer sees → business job of the beat → the transition out, including which object survives it. Rules:
40- 12–15 distinct compositions for a 30s film. Vary scale: macro → wide → overhead → UI close-up → type impact.
41- The lead subject fills 60–85% of the usable frame in feature beats. No small card floating in a big empty field.
42- Every beat has a readable landing, then an accelerating exit. No holds without motion over ~0.6s.
43- Name 3 signature transformations you can describe without effect names, e.g. "the inspection photo becomes the report's hero image".
44- 3D only where it explains something physical or spatial. Typography and UI stay crisp HTML/SVG.
45Get a quick critic pass on the storyboard itself (chronology, business logic, truthfulness).
46 
47### 4. Assets
48- **AI stills:** generate the key frame first, then animate it with image-to-video. Prompt as a production brief: lens, light, exposure ("bright, airy, nothing crushed to black"), negative space reserved for type, "no people / no text / no logos / no watermark" when needed.
49- **AI video:** short (4–5s) clips with restrained camera moves ("a steady gimbal dolly, about 25 cm of travel, preserve the exact geometry, no morphing"). Expect 720p/24fps and interpolate/upscale, which is not native detail. Reject clips whose geometry warps; regenerate rather than hide.
50- Keep a generation ledger: model, prompt, seed, job id, accepted window. Never commit API keys.
51 
52### 5. Build components in isolation
53Each custom component (3D scene, report UI, booking flow, logo mark) gets its own lab page (`templates/component-lab.html`), is rendered to stills plus a short motion proof, and goes through a component Gauntlet round **before** it joins the film.
54 
55### 6. Assemble
56One root timeline; each scene is a sub-composition; Three.js scenes are rendered from the root seek clock; overlays such as labels, pins and leader lines are positioned from projected 3D anchors every frame (`templates/projected-overlays.js`). Hand objects across scenes at *exact* pixel coordinates, so the last frame of scene A equals the first frame of scene B for the carried object.
57 
58### 7. Full-film Gauntlet
59Render the whole film. Run `scripts/frozen-time.sh` and `scripts/loudness.sh`. Send to a fresh critic with `references/critic-prompts.md` (full-film prompt). Fix the highest-impact items, re-render, and send to a *new* critic that verifies the previous list item by item. Stop at the quality bar or when gains become cosmetic (usually 3–5 rounds).
60 
61### 8. Audio last, but not an afterthought
62Follow `references/audio.md`: music matched to the buyer's customer and kept well under the effects (lo-fi or warm acoustic for home services); one soft, rumble-free whoosh per real transition; clean UI sounds only on real actions; per-event levels solved in each effect's band (`scripts/solve-sfx-gains.py`); candidates screened with `scripts/sfx-candidates.py`. Always deliver a music-only fallback, and isolate complaints with it.
63 
64### 9. Deliver
65Master MP4 (1080p60 for motion work), poster frame, contact sheet, editable source, generation ledger, and a Gauntlet ledger (what each critic found → what changed → measured before/after). State limits honestly: what was measured versus listened to, and sampled versus exhaustive review.
66 
67## Working style the clients in this playbook expected
68- Plan visibly (storyboard), then build without stopping to ask for approval of every step.
69- Report status in one line when working for a long time.
70- Show the work: contact sheets, measured numbers, critic verdicts.
71 
View all files on GitHub →

Details

License
MIT
Stars on the repo
★ 665
Checked
Source
echris6/motion-video-kit ↗
Creator
echris6 · 1 listing
View creator

Similar skills

See all →
Launch Video Composerlatent-spaces/brag · by latent-spacesTurn the current project website into a short, polished, shareable launch video using Hyperframes. Use when someone says "/brag", "let's brag about this", "make a launch video", "turn this into a video", or wants to share what they built. Reads the project code directly — no live URL or screenshots needed.★ 12.5k GitHub starsQuick Launch Videolatent-spaces/brag · by latent-spacesTurn a project directory or a website URL into a short, shareable launch video with music, motion, and share copy. One file, no bundled assets — built entirely by the model with the tools already on the machine. Use when someone says "/brag-slim", "let's /brag about this", "brag about <url>", "make a launch video", or wants to show off what they built. If the /brag skill is also installed, let /brag handle those phrases; it hands off here on Opus 5.5.★ 12.5k GitHub starsPhase 5: Launch Growthmsitarzewski/agency-agents · by msitarzewski> Duration: 2-4 weeks (T-7 through T+14) | Agents: 12 | Gate Keepers: Studio Producer + Analytics Reporter★ 154k GitHub starsLaunch Readiness Planneraddyosmani/agent-skills · by addyosmaniPrepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy.★ 98.7k GitHub starsProduct Launch Plannercoreyhaines31/marketingskills · by coreyhaines31When the user wants to plan a product launch, feature announcement, or release strategy. Also use when the user mentions 'launch,' 'Product Hunt,' 'feature release,' 'announcement,' 'go-to-market,' 'beta launch,' 'early access,' 'waitlist,' 'product update,' 'how do I launch this,' 'launch checklist,' 'GTM plan,' or 'we're about to ship.' Use this whenever someone is preparing to release something publicly. For ongoing marketing after launch, see marketing-ideas. For the offer being launched (bonuses, guarantees, scarcity, naming), see offers.★ 51.1k GitHub starsPacsomatic Workflow ToolkitK-Dense-AI/scientific-agent-skills · by K-Dense-AIOperator toolkit for nf-core/pacsomatic matched tumor-normal workflows from BAM inputs. Use this skill when the user needs to validate run inputs, generate pacsomatic-compliant samplesheets, prepare reproducible Nextflow launch artifacts, run locally or submit to schedulers (LSF/Slurm/PBS/SGE), and triage execution failures. Triggers on requests to run pacsomatic, prepare launch commands/scripts, perform dry-run checks, or troubleshoot pipeline startup and scheduler submission errors.★ 46k GitHub stars