director-skill

Converts scripts into shot-level director briefing scripts for AI video generation.

Updated Aug 12, 2026
One-click install
npx skills add https://github.com/VANTSU-1874/woods-video-studio --skill director-skill-vantsu-1874
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: director-skill
Source: https://github.com/VANTSU-1874/woods-video-studio/tree/main/template/.agents/skills/director-skill
Command: npx skills add https://github.com/VANTSU-1874/woods-video-studio --skill director-skill-vantsu-1874

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? It turns raw short-drama scripts into structured, shot-level director briefing documents that downstream AI video prompt writers (e.g., Seedance) can directly inherit, while enforcing asset consistency against locked per-episode asset snapshots. ## Core Features & Use Cases - Script-to-Scene Breakdown: Reads .txt, .md, or pre-converted .docx scripts and splits them into scenes (P01/P02...) by time-space jumps, emotional turns, and narrative function shifts. - Fused Shot-Level Briefing: Outputs director shots (镜1/镜2...) where camera design, blocking, original dialogue with tone annotations, and performance details are fused into chronological paragraphs, with key shots flagged for multi-angle reaction chains. - Internal Asset Consistency Check: Verifies characters, scenes, and props against the series asset bible and the episode's locked asset snapshot without emitting asset lists in the output. - Use Case: Given episode 3 of a short drama, produce 01-导演讲戏.md with scene functions, rhythm curves, key-shot visual anchors, and a closing hook, ready for the storyboard stage to split into formal Seedance S segments. ## Quick Start Analyze the script for episode 3 and generate the director briefing document following the director analysis template.

Frequently Asked Questions about director-skill

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

FAQPage Schema
How do I convert a script into a director briefing for AI video generation?

Provide the episode script in .txt or .md format (or .docx pre-converted by the Node converter). The skill reads project-config.json and the locked asset snapshot, then outputs scene-by-scene fused shot paragraphs with dialogue, camera design, and performance details.

What script formats does the director analysis support?

It supports .txt, .md, and .docx inputs. .docx files are extracted and split by the Node converter into 资产/converted-scripts/epXX.md during initialization. PDF, PPTX, and XLSX are not supported and must be converted first.

Does the director output include formal storyboard shot IDs or durations?

No. Director shots use informal labels like 镜1/镜2 and never include S01/S02 IDs, shot counts, durations in seconds, or video generation parameters. Formal Seedance S-segment splitting is the storyboard stage's responsibility.

Why does the director analysis stop with an asset snapshot error?

The skill requires a locked per-episode snapshot at .claude/production/state/asset-snapshots/epXX.json as the final visual source of truth. If the snapshot is missing or not locked, analysis halts and you must complete the asset snapshot stage first.

Can the director briefing add new dialogue or transition lines?

No. All dialogue, narration, and voiceover must come verbatim from the source script in its original language. Adding transitional or explanatory lines is forbidden; weak lines must be strengthened through camera and performance design instead.