04-storyboard-shotlist

Convert video scripts into structured shot lists with camera, lighting, and timing metadata.

1|Updated Apr 20, 2026
One-click install
npx skills add https://github.com/ntd237/draft_toolkits_20042026 --skill 04-storyboard-shotlist-ntd237
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: 04-storyboard-shotlist
Source: https://github.com/ntd237/draft_toolkits_20042026/tree/main/other-skills/video-skills/04-storyboard-shotlist
Command: npx skills add https://github.com/ntd237/draft_toolkits_20042026 --skill 04-storyboard-shotlist-ntd237

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning a written video script into a production-ready shot list is error-prone: shots get missed, durations drift from the script, and downstream prompt engineers lack the technical details (camera angle, motion, lighting) needed to generate each shot. This Skill standardizes that breakdown into machine-readable JSON plus a human-readable Markdown table. ## Core Features & Use Cases - Scene-to-shot mapping: Splits each script scene into one or more shots based on subject changes, camera angle changes, engine duration limits, and location changes. - Per-shot technical specification: Defines camera angle, camera motion, lighting, action, dialogue, sound effects, and transitions for every shot. - Dual validated output: Produces shotlist.json (schema-conformant, for machines) and shotlist.md (for humans) with enforced consistency, unique sequential shot IDs, and total duration matching the script within ±5%. - Use Case: After writing a 30-second promotional video script, run this Skill to get a shot-by-shot breakdown that a video prompt engineer can directly convert into AI video generation prompts. ## Quick Start Read my concept.md and script.md files and generate a complete shotlist.json and shotlist.md breaking the script into individual shots with camera, lighting, and timing details.

Frequently Asked Questions about 04-storyboard-shotlist

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I break a video script into a shot list?▼

Map each script scene into one or more shots, splitting whenever the subject, camera angle, or location changes, or when a shot would exceed the engine's duration limit. Then assign each shot a camera angle, motion, lighting, action, dialogue, and transition.

What should a shot list for AI video generation include?▼

Each shot needs a unique ID, scene reference, start time, duration, a one-sentence visual description, camera angle and motion, lighting, dialogue quoted verbatim from the script, sound effects, and the transition to the next shot.

How do I keep shot durations within AI video engine limits?▼

Read the duration_per_shot value fixed in concept.md and check it against the engine's technical limits in the config. Split any scene that would exceed that limit into multiple shots, and verify total duration matches the script within ±5%.

Can I merge two different actions into one shot?▼

No. Actions happening in different places or at different times must be separate shots, because AI-generated shots are short and each shot is an independent render command. Combining them produces inconsistent or unusable output.

What are the limitations of automated script-to-shotlist conversion?▼

The process cannot invent shots missing from the script; gaps must be reported back rather than filled. It also cannot alter total runtime or rewrite dialogue, so a poorly structured script yields a poorly structured shot list.