---
path_id: product-screenshots-to-promo-video
path_version: 1
status: partial
generated_from: SkillsTested structured records
---

# Product screenshots to a directed promo video

> Evidence status: PARTIAL EVIDENCE. This pack does not extend the published evidence boundary.

## Outcome

A reproducible Remotion project and rendered promo video, with a shot plan and technical verification report.

## Required inputs

- Product screenshots or a product URL
- One-sentence product promise
- Target duration and aspect ratio

## Expected outputs

- Shot plan
- Remotion project
- Rendered MP4
- Video metadata verification report

## Pinned installs

### video-shotcraft

- Source: https://github.com/Vincentwei1021/video-shotcraft
- Commit tested: `a87bf81`
- Verification: `function_verified`
- Install: `npx skills add Vincentwei1021/video-shotcraft -a claude-code -y`
- Not verified: User-supplied assets, a no-skill baseline, or repeated-run effect.

### remotion skills (official, 10-skill pack)

- Source: https://github.com/remotion-dev/skills
- Commit tested: `0dd76fa`
- Verification: `function_verified`
- Install: `npx skills add remotion-dev/skills -a claude-code -s '*' -y`
- Not verified: Repeated-run consistency, a no-skill baseline, or effect on a production video project.

## Execution

### 1. Direct the sequence

- Purpose: Turn the product story into deliberate shots, timing, transitions, and a still ending rather than an undirected animation.
- Input: Product screenshots, product promise, duration, and aspect ratio
- Instruction: Follow video-shotcraft's required template-versus-free-form choice, then write a frame-addressed shot plan before implementation.
- Output: shot-plan.md
- Evidence level: `function_verified`
- Human confirmation: required

### 2. Implement in Remotion

- Purpose: Translate the approved shot plan into a technically correct, editable Remotion composition.
- Input: shot-plan.md and normalized product assets
- Instruction: Use the official timing, animation, asset, and project-structure rules while preserving the shot plan's visual direction.
- Output: remotion-project/
- Evidence level: `function_verified`
- Human confirmation: not required

### 3. Render and verify

- Purpose: Prove that the deliverable exists and meets its mechanical contract before subjective review.
- Input: remotion-project/
- Instruction: Render with a pinned browser executable, then inspect codec, duration, resolution, frame rate, file size, and playback.
- Output: promo.mp4 and verification.json
- Evidence level: `unverified`
- Human confirmation: required

## Evidence

### Same five-second brief rendered with video-shotcraft and Remotion official skills

- Date: 2026-07-25
- What it proves: Both skill methodologies produced a working 150-frame Remotion scene from the same fixed brief. Setup, render timings, failures, output bytes, and frame 75 were recorded.
- Not verified: A user-supplied screenshot-to-video workflow, repeat-run success rate, public MP4 download, audio, or a fifteen-second final promo.
- Source: https://skillstested.com/compare/video-shotcraft-vs-remotion-skills/

## Known limits

- The published comparison used a fixed typography-and-check brief, not user screenshots.
- Only still frames are currently public; the final MP4 is not yet downloadable.
- Repeat-run workflow success has not been measured.
- Headless environments may need a local chrome-headless-shell and concurrency set to one.

## Next verification

Run one fixed six-screenshot product pack through the complete path three times, publish the MP4 and source project, and verify duration, resolution, playback, and repeat success.