Video Shotcraft Skill for Remotion Product Video Production

Video shotcraft skill gives product marketers, motion designers, and frontend teams a documented way to plan, build, preview, inspect, and review Remotion product videos. It combines reusable shot recipes with a reference template and a staged production method, so the work starts with assets and approvals instead of jumping straight into animation code.

This is a third-party agent skill and motion-production toolkit by Wei Yihao. It is not a generic one-click video generator, and the repository does not promise campaign results, automatic commercial delivery, or endorsement by any brand whose films informed its techniques.

Skill Summary

Video Shotcraft is one installable agent skill for Claude Code and Codex. At the locked repository commit, it packages 106 shot recipe cards, 161 motion previews covering 162 styles, Remotion demo implementations, production references, audio assets, and a complete Ink Press template.

The repository offers three routes. A team can adapt the complete reference template, follow the documented pipeline for a new production, or start from one named shot card. When a request does not name a route, the skill instructions say to introduce the built-in template first and ask whether the user wants the template, free creation, or a specific card.

Where This Skill Fits

Use Video Shotcraft when a web or desktop product needs a promo, launch, demo, or feature video built in Remotion. It fits after the team has a real product surface, a message to communicate, and time to review intermediate artifacts. It is less suitable when the request is only “make an AI video” with no product pages, brand direction, approved storyboard, or review owner.

The useful operating boundary is review before expensive work. The source asks for captured assets, a styleframe, and a storyboard before full implementation. It also requires static-frame checks during construction, full renders after changes, and a formal acceptance review at the end.

Who It Helps

• Product marketers who need a feature-led promo tied to real product screens rather than invented UI.
• Motion designers who want reusable shot structures, timing guidance, camera ideas, and sound-design checks.
• Frontend and design engineers who can provide real pages, layout coordinates, and product-safe demo data.
• Agent-assisted production teams that can approve a styleframe and storyboard, then inspect rendered evidence before delivery.

Access / Install Links

The official repository documents a skills CLI install:

npx skills add Vincentwei1021/video-shotcraft

It also documents a manual route: clone the repository and link it into the skill directory used by Claude Code or Codex.

git clone https://github.com/Vincentwei1021/video-shotcraft.git
ln -s /path/to/video-shotcraft ~/.codex/skills/video-shotcraft

Claude Code users can link the same clone at ~/.claude/skills/video-shotcraft. The repository is Apache-2.0 licensed, while Remotion and the bundled audio sources have their own terms that still need project-specific review.

Setup Steps

1. Install or clone the repository, then confirm that your agent can read the root SKILL.md, references, shot cards, demos, and template.
2. Choose the template, free-creation, or named-card route. Also decide whether music is already selected and what data must be anonymized.
3. Prepare real product pages or a local project, product copy, brand direction, and a safe fictional data set for any screenshots.
4. Run a bounded test: capture one page, approve one styleframe, and render one still before committing to the full video.

How Video Shotcraft Works

The repository describes a six-stage production pipeline after the initial route and compliance questions.

1. Capture assets. Use real product pages for existing interfaces, produce high-resolution page textures and element cutouts, and record layout coordinates. Replace customer or project data with fictional content.
2. Set the visual direction. Derive colors, type, materials, and tone from the product. Use a cheap HTML or CSS styleframe to approve the look before animation work.
3. Approve the storyboard. Map product features to shots, select recipe cards where useful, budget hold and rest frames, and get one clear approval on the sequence.
4. Build and inspect shots. Read the relevant recipe and demo source before coding. Render stills for individual shots, then render the full composition and extract frames after structural changes.
5. Add sound after the picture is stable. Manage cues in a relative-frame table, match sound to camera and scene actions, and recheck every cue if the timeline moves.
6. Run formal acceptance. Review the latest MP4 and key frames against the repository checklist, record problems with frame-number evidence, repair them, and render the delivery version.

The source also calls for deterministic rendering: avoid Date.now() and Math.random() in compositions so repeated renders do not drift unpredictably.

Shot Cards and the Ink Press Template

The first-party gallery organizes the 106 recipe cards with 161 motion previews and 162 styles at the locked commit. A card is a starting structure, not permission to copy another product’s branding or assets. The skill says to inherit motion structure while deriving the visual language from the product being promoted.

Ink Press is the repository-provided reference production: a 36.2-second, 1920×1080, 30fps, 10-shot Remotion template. Its documented structure alternates feature sequences with title-card breathing room, uses real page captures in 2.5D camera moves, and finishes with a formal review. “Validated” here is the repository’s description of its own template, not an independent Big Prompt Hub benchmark.

Inside the template directory, the source documents these preview and render commands:

npm install
npx remotion studio src/index.ts
npx remotion render src/index.ts AiflPromo out/promo.mp4

Example Inputs

Use video-shotcraft to create a promo for my desktop product.

Use deck-deal-flyin and row-embed shot cards for this product promo.

Design a close-up inspired by spotlight-hero-card.

Expected Outputs

• Asset set: real page captures, element cutouts, layout coordinates, and anonymized demo data.
• Approval artifacts: a styleframe, design specification, storyboard, and feature-to-shot mapping.
• Implementation: a Remotion project with reusable components, deterministic animation logic, and review stills.
• Delivery: a rendered MP4, optional sound design, extracted key frames, and an acceptance report with evidence for any repairs.

Use Cases

• Adapt the Ink Press structure for a web app while replacing every demo screen with the product’s own safe assets.
• Build a launch video from an approved feature list, brand direction, and storyboard.
• Prototype one hero, fly-in, embedded-row, or title-card shot before funding the full production.
• Audit an existing Remotion promo with static frames, full-render inspection, audio cue checks, and a final acceptance report.

Common Mistakes & Fixes

• Mistake: coding before approval. Fix: approve the assets, styleframe, and storyboard first.
• Mistake: copying demo branding. Fix: keep only the motion structure and rebuild the look from the product.
• Mistake: adding sound before picture lock. Fix: stabilize the timeline, then pin and recheck every cue.

Limitations

• Video Shotcraft does not prove that one command can produce a finished commercial video. The documented workflow depends on assets, decisions, implementation, renders, and human review.
• The shot-card, preview, and style counts are repository facts at the locked commit and may change in later versions.
• Template screenshots are demo assets. Replace them with the target product’s pages and remove or fictionalize customer, project, and sensitive data.
• Remotion may require a paid license in some company contexts. Check the current official Remotion license for the team and use case.
• Bundled audio does not share one blanket license. Review the repository’s attribution file and the terms for each selected track or effect.
• The repository credits techniques distilled from product films, but it includes no permission to reuse those films’ footage, artwork, branding, or other protected assets.

Related Tools / Prompts

Video Shotcraft sits on top of Remotion and a product-asset workflow. It pairs naturally with browser capture tools for real pages, frontend code agents for safe demo data and component work, video review tools for frame-level notes, and human approval checkpoints for styleframes and storyboards. Those tools complement the skill; they do not remove its review requirements.

FAQ

• Q: What is video shotcraft skill?
  A: It is a third-party agent skill and toolkit for planning, building, rendering, and reviewing Remotion product videos with reusable shot recipes.
• Q: How do I install Video Shotcraft for Codex?
  A: Use the documented skills CLI command, or clone the repository and link it to the Codex skills directory.
• Q: Does Video Shotcraft automatically create a commercial video?
  A: No. The source requires product assets, staged approvals, Remotion implementation, render inspection, and a final evidence-based review.

Use this skill when your team can provide real product material and review intermediate decisions, not when the brief expects unreviewed one-click delivery.

Explore more in AI Skills and Video & Music.

Follow @bigprompt for more practical AI skills and reviewed production workflows.

Related Guides for Reviewed Creative Work

Apple Design skill guide for reviewing interface motion before implementation

Social media approval workflow for keeping a human decision before scheduling

Product photo workflow for turning source assets into reviewed campaign creative

ChatGPT local folder guide for making project files available to a desktop agent

Unused agent skills cleanup guide for reviewing local skill value and removal boundaries

Big Prompt Hub Review

Video Shotcraft is strongest as a production discipline packaged around Remotion, not as a promise of instant video creation. Its shot cards and reference template can shorten the search for a motion structure, while the staged approvals and render checks keep the team responsible for product truth, visual quality, licensing, and the final decision to ship.