short-drama-produce sends approved prompts to the media generation services you configure and saves the results and run records in the project. It covers images, video clips (single shots and multi-shot groups), voice-over and background music.
Nothing is sent until you confirm. The skill builds a preview of the whole batch: count, target service and model, durations or sizes, and every output path. A confirmation code tied to the exact prompt text, reference files and parameters then unlocks the run, and any edit invalidates it. It does not write prompts, change lines or choose voices. The skill’s text is in Chinese.
What You Get
- A batch preview listing count, service, model, parameters and output paths
- Confirmation receipts tied to a code that expires when anything changes
- Generated images, video clips, voice lines and music saved under the episode’s output folder
- Run records, a status report and an audit that finds orphaned remote jobs
- Built-in adapters for GPT Image 2, Seedance, MiniMax H3 video, MiniMax music and MiniMax speech
Common Use Cases
- Generate every first-frame image for one episode after approving a batch preview
- Resume a video batch after a dropped connection without paying twice
- Synthesize the dialogue lines of an episode with fixed voice presets
What Makes It Unique
Its confirmation is part of the tooling. A confirm code is bound to the exact prompt section, reference files, parameters and output paths, a vague ‘go ahead’ does not count, and the code is spent once a remote request is made. Resume and collect steps recover paid jobs after interruptions, and service keys live outside the project folder.
Under The Hood
A bundled Python tool, production_tool.py, prepares batches, records confirmations, runs jobs, checks status, collects results and audits. It reads prompt documents and reference images or audio from the project and writes media files and run records into the episode’s output folder. Once you confirm, it sends requests over the network to the generation service named in an adapter config that lives outside the project, with API keys taken from environment variables or the system credential store, and it polls for results. Those services bill you for each call. It runs only when you ask for generation.