video-shotcraft, tested
A 51.1MB product-video production kit: 104 shot recipe cards, Remotion templates, audio assets, and an opinionated workflow. We installed the current commit and rendered a complete five-second 1920×1080 MP4 with motion and sound.
- Repo
- Vincentwei1021/video-shotcraft
- Stars
- 2,561 as of 2026-07-29
- Commit tested
- d491544
- Install
npx skills add Vincentwei1021/video-shotcraft -a claude-code -y- Install time
- 42.54s (measured)
- Environment
- os macOS arm64, node v24.14.0, package manager pnpm 11.9.0
- Failures hit
- 1
- Tested on
- 2026-07-29
- Verified scope
- Fresh current-commit install plus a full five-second 1920x1080 MP4 render with visible motion and an AAC audio track; playback frames and media streams were checked.
- Not verified
- Repeated-run consistency, user-supplied product assets, captions, publishing, or a full revision workflow.
- Evidence
- Open the supporting comparison
What it is
video-shotcraft is the less an instruction file than a self-contained production kit. The core is a library of 104 shot recipe cards, plus Ink Press — a complete, accepted 36.2-second 1920×1080 promo template with 2.5D page dollies, title cards, transitions and sound design, meant to be re-skinned with your product's screenshots. The current default install is substantially slimmer than the 164MB build we measured on July 23; dated readings remain on the comparison page.
The install, as it actually happened
npx skills add Vincentwei1021/video-shotcraft -a claude-code -y42.54 seconds in the fresh current-commit test. The installer copied 51.1MB across 660 files
into .claude/skills/; per-project installs each get their own copy.
The test: a complete playable output
Docs-reading is not testing, so we opened the current Remotion 4.0.484 template, installed its dependencies (124.79s), implemented the shared five-second brief, and rendered H.264 video plus AAC audio. Watch the output and copy the exact start prompt on the decision page.
What broke (and the fixes)
The pnpm warning did not block the current render. The template's normal npm workflow avoids that ambiguity; if your team standardizes on pnpm, approve esbuild's build script explicitly.
Who it's for
Solo developers and small teams who want a product promo without a motion designer. The honest trade-offs: the SKILL.md is written Chinese-first (the README is bilingual, and agents handle the language fine, but English-only humans browsing the cards will lean on the gallery); and use-time depends on a working Remotion/Chromium stack, which is where all our failures lived. The template-first workflow — the skill explicitly offers Ink Press before freeform creation — is the fastest path we have seen to an acceptable result.
FAQ
Do I need Remotion installed before adding the skill?
No. The skill installs in seconds without it; Remotion is pulled in per-template via
npm install when you actually produce a video.
Can it render on a headless server?
Yes, with care: preinstall an approved chrome-headless-shell in restricted CI, pass it with
--browser-executable, and cap --concurrency to your core count. The first
browser download succeeded in our Mac test but dominated the first-render time.