This skill handles project initialization, cross-stage routing, production format, and the Dashboard. The main content of each stage is completed by the corresponding owner.
Quick Start
All projects uniformly use creator-first workflow: each episode maintains on demand
剧本.md、视觉设定.md、分镜.md、图片提示词.md、视频提示词.md, without establishing a parallel structured creative source of truth.
For specific writing methods, see five creative documents。
Routing
| What the user wants to do | owner / behavior |
|---|---|
| Develop ideas, series promises, adaptations, and episode maps | $short-drama-develop, only when the user needs it |
| Identify episodes from existing complete scripts/drafts for multiple episodes | $short-drama-develop establish a temporary index according to actual boundaries |
| Analyze a long original work | $short-drama-novel-analyze, only when the user needs it |
| Write or revise a single-episode script | $short-drama-write → 剧本.md |
| Break down characters, looks, locations, and props | $short-drama-assets → 视觉设定.md |
| Write asset image prompts | $short-drama-image-prompts → 图片提示词.md |
| Do shots and freeze keyframes | $short-drama-storyboard → 分镜.md |
| Write video/timeline music prompts | $short-drama-video-prompts → 视频提示词.md |
| Actually generate media | $short-drama-produce, preview first, then explicitly confirm, and finally run |
| Edit produced materials into a final cut | $short-drama-edit → 剪辑单.md and 制作成果/成片/ |
| Review or validate | $short-drama-review, only when the user names it |
| Initialize, Dashboard, archive named documents | This skill |
项目开发/ The long-material analysis and episode indexing are optional analysis workspaces and do not participate in single-episode layout decisions; writing any episode still only maintains
that episode's five creator-first Markdown documents.
Ready-made scripts can be directly broken down into assets; existing visual facts can be directly used to write image prompts or storyboards; existing storyboards can be directly used to write video prompts. Do not fabricate upstream just to complete a nominal pipeline.
The five creative documents record the script, visuals, and prompts; the edit sheet records choices and post-processing after material production. When modifying the story, shot responsibilities, or upstream duration declarations, return to the document responsible for that content.
Execute the request
- Find the project or materials given by the user, and read only the direct input for the current task.
- Hand the complete scope named by the user to the corresponding owner; batches only control context and continue automatically.
- Ask only when there is a real creative fork; do not ask creators about schema, directories, transactions, or checkers.
- After the scope is completed, report once on what was completed, key decisions, real open items, and optional next steps.
- Do not automatically start reviews, archiving, or production that the user did not name.
- When a request spans visual settings, image prompts, storyboards, or video prompts, perform a visual dependency reconciliation against the current five documents before finishing; do not leave the later-completed branch outside the other branch's old references just because image prompts and storyboards can run in parallel.
- When a video prompt request encounters "input reference image: none" or still carries "reference image to be added," first route the storyboard owner to check the project's existing images and refresh the binding. If there is a matching image, continue in the same request; if a necessary image is missing, stop with a list.
When stopping, give all three paths together: put the existing image into the project and bind it as
REF-...; the creator produces images in their own tools, and for this round first usePLAN-...to write out a per-shot image plan and produce video prompts as usual; or explicitly switch to text-to-video. Producing reference images with this kit requires an adapter and credentials outside the project, which is only one way of doing the first path — do not present it as the only entry point, and do not offer only the two options of "generate reference images / text-to-video". Do not treat "not manually specified" as an explicit choice of text-to-video. In this round, if the shots still lack "visual grounding", also backfill by the frozen keyframes already finalized; the two grounds describe the same frame, so do not fill in only one. - When the user names a target video model in the session ("write it for MiniMax H3", "use Seedance 2.5") and
short-drama.json'sproduction_profileorunset, first write this choice, along with the native duration, reference method, and body language it entails, into the profile, then continue to the downstream stages. If a naming in the session is not written into the profile, the next round will fall back to the generic path, and the dialect and duration will have to be guessed again.
Initialization and Dashboard
When project configuration is needed, run:
python3 {技能目录}/scripts/project_tool.py init ./my-drama --title "示例短剧"
When directly entering a creator statement language, prompt language, aspect ratio, episode count, or single-episode target duration that has already been confirmed, for the first init include the corresponding
--language、--prompt-language、--aspect-ratio、--episode-count、--target-seconds; omit only
unconfirmed items, and do not leave certain facts from the Brief as nullin the configuration. When writing confirmed production profile entries, the status is uniformly
accepted;unset only means not yet decided; do not invent intermediate states.
init only establishes the configuration and empty directories; on the first creation, write the document into 剧集/<EP>/, and do not pre-create empty files.
When the project is already set up and the user only later settles on a target video model, write the choice into the profile and at the same time show its impact on the duration range, reference method, and
body language. The profile only accepts creator decisions that have been published and accepted, so it is three steps, not one. First write a one-line decision record
(accepted_value is the object itself that is to go into choices ; do not wrap another layer of choices):
{"decision_id":"CD-H3","status":"accepted","target_locators":[{"src":"short-drama","field":"/creator_authority/production_profile/choices"}],"accepted_value":{"target_video_model":"minimax-h3","video_prompt_dialect":"minimax-h3","video_prompt_language":"en","native_duration_seconds":{"min":4,"max":15},"supported_generation_modes":["text","first_frame","first_last_frame","reference"],"audio_generation":"same_pass"}}
then publish, accept, and write:
python3 {技能目录}/scripts/project_tool.py publish <project> --owner short-drama \
--artifact-id AR-PROFILE --output "创作者决策/production-profile.jsonl=输入/profile.jsonl"
python3 {技能目录}/scripts/project_tool.py accept <project> --artifact-id AR-PROFILE --decision accepted
python3 {技能目录}/scripts/project_tool.py set-authority <project> \
--field /creator_authority/production_profile/choices \
--decision-ref "创作者决策/production-profile.jsonl#CD-H3"
The field values are given by the matched model dialect:$short-drama-video-prompts 's MiniMax H3 / Seedance / Wan 3.0 dialect files all write the
recommended profile. After writing, use status to double-check whether video_model_profile has already appeared.
See Run preflightfor project positioning and safe writing. When the user explicitly requests the Dashboard, run:
python3 {技能目录}/scripts/dashboard_server.py --workspace <workspace> --port 0 --detach --open
--detach lets the service process run independently of the current shell; the end of the session, closing of the terminal, or exit of the agent will not take it down;
the link therefore remains valid throughout the entire creation period. The running address, port, and pid are recorded in
<workspace>/.short-drama/dashboard.json(readable only by the owner), and the logs in the same directory dashboard.log:
python3 {技能目录}/scripts/dashboard_server.py --workspace <workspace> --status # 打印当前链接
python3 {技能目录}/scripts/dashboard_server.py --workspace <workspace> --stop # 停止
When the same workspace already has a running Dashboard, starting it again only prints the same link and does not open a second port; if you really want to change
the port or change the token, add --restart. Without adding --detach , the behavior is unchanged: run in the foreground, end with Ctrl-C.
The Dashboard presents the project by stage: the full-series page gives the next step and per-episode progress; each episode is divided into six views — script, settings, storyboard, prompts, final cut, and review — and ⌘K searches the full series. The structure view is read-only; changes are saved as Markdown in "Edit Source". The visuals only recognize bindings in the document:
thumbnails are those of the 用途:起始帧 in the storyboard REF-..., each shot's material is the "source" of the edit list, and the finished film is the editing output; if there is no binding,
it shows an empty slot and does not match images by file name. It is not responsible for workflow orchestration or media production; wherever writing or generation is needed, it only copies one request sentence and returns it to the conversation.
The target duration of each episode comes from status of format, and rhythm comparison only uses accepted rhythm_profile。
Project-level creative decisions
When production form, visual direction, playback surface, and episode length goals indeed constrain multiple stages, present the choices and their impact, and let the user decide. Look Development is an optional branch, not a fixed gate for entering image prompts or storyboards.
Rhythm values (opening hook seconds, emotional beat interval, number of reversals, VO ratio, average shot length, etc.) live in
creator_authority.rhythm_profile. The fields and default values are proposed by $short-drama-develop according to the production form,
and after the creator accepts or rewrites them, write them in according to the three steps above: the decision's accepted_value is a complete archive object,--field
write /creator_authority/rhythm_profile; after the archive has been accepted, when changing only one value, --field points to that field.
set-authority only validates type and range; missing fields, out-of-range values, or extra unknown fields are all rejected for writing. Downstream only performs arithmetic checks on archives where status is accepted ; missing,unset or
proposed all mean "undeclared, do not check". After writing, use status to review rhythm_profile; if the archive is invalid after manual editing,
it returns an empty archive, and the problems are listed in rhythm_profile_problems。
Read only one piece of relevant knowledge according to the question:
- Rule tiers and owner routing:Rules and routing index
- Output language, stable IDs, ownership, and safety boundaries:Contract and ownership
- Form differences among live action, 2D, 3D, ink wash, Q-style, and Chinese animation:Production forms
- When representative frames need to be compared:Look Development
- What reference images can control:Reference characters
- Occlusion, delayed reveal, and audience knowledge timing:Audience reveal
- Responsibilities of the master, reshoots, and alternate versions:Reshoots and alternates
Production and delivery boundaries
External production always retains preview -> explicit confirm -> run. Archiving only copies the current documents and finished products named by the user, excluding
private inputs, credentials, absolute paths, and hidden runtime state; it does not fabricate approvals, hashes, or a second set of content for the archive.
When the user asks "how do I export/deliver it to me when it's done", use export to package the current state:
python3 {技能目录}/scripts/project_tool.py export <project> --out <项目外目录>
It copies each episode's existing five creative documents and 剧集/<EP>/制作成果/ to --out, attaches manifest.json and
checksums.sha256, and excludes 输入/、交付/ and .short-drama/. When only part is wanted, add
--episode EP001(repeatable); when only text is wanted, add --no-media; to overwrite the old directory, add --overwrite。
--out must be outside the project.
export iscurrent state snapshot, and in the manifest asserts_approval is always false: it does not claim any review or
creator acceptance. The only path that still provides a formal delivery package with approval evidence is package/verify .
Installation and maintenance
Run only during installation, upgrade, or troubleshooting python3 scripts/selftest.py。