What problem does it solve?
Writing scripts for AI-generated short drama requires dialogue as structured data (not prose) and strict per-episode runtime control, since overruns discovered downstream force costly regeneration. This Skill turns per-episode synopses from an outline into scenes with alternating action beats and dialogue lines, deterministically estimating each episode's duration so a three-minute episode is actually three minutes.
Core Features & Use Cases
- Beat-flow scripting: Every scene alternates action beats (one event each, narrative prose) with dialogue lines carrying speaker and delivery notes, feeding directly into per-line TTS generation.
- Deterministic duration budgeting: Dialogue converts at reading speed (4.5 chars/sec default) and action at a fixed per-beat estimate, with every episode gated to land within ±15% of its target seconds.
- Ten code-enforced quality gates: Line length limits, speaker legality, hook-in-first-3-beats cold opens, at least one action beat per scene, and cross-checks of characters, scenes, lighting states, and props against upstream outline and art-bible JSON files.
- Review report: Renders a self-contained bilingual (Chinese/English) HTML report with a duration gauge, per-episode scripts, scene table, and a character-grouped line book with voice-prompt copy buttons for TTS.
- Use Case: Given an outline.json for a 6-episode vertical drama, seed the script skeleton, write episodes in batches of up to 3, validate against the outline and art bible, then export script.json plus a review-ready HTML report.
Quick Start
Ask the agent to write the script for episodes 1-3 of your short drama using your outline.json, then validate and render the HTML report.
