---
name: storyboard-skill
description: Generate shot-by-shot storyboard scripts from film screenplays and explain the visual logic of every retained cut. Use whenever the user asks to generate a storyboard, shot list, shot breakdown, camera plan, shot size, camera movement, axis check, shot duration, edit point, or to turn a screenplay scene into camera decisions.
---

<!-- online-auth-upgrade -->
<!-- online-runtime-policy:start -->
## Online Authorization

This online build is locked. Before reading protected references, searching protected libraries, diagnosing, writing, or generating task output, verify authorization through the Tencent Cloud service.

- Skill ID: `storyboard-skill`
- Verification: activation code or phone credential plus local device fingerprint.
- Protected references and databases live on the server.
- Primary server: `https://superskill.online`
- Fallback servers: `http://43.156.61.150, http://superskill.online`
- Public skill updates are checked before protected database authorization. If the server reports a newer public package, download only the public skill package, verify it, back up the old folder, replace it, then restart the conversation if `SKILL.md` changed.
- If the local skill folder cannot be replaced because of permissions, stop automatic replacement and show the latest public package URL, SHA256, version, and manual install rule. The zip filename may include a date suffix, but the extracted root folder and `SKILL.md` name must remain `storyboard-skill`.
- Always display the exact formal Skill ID `storyboard-skill`. Do not replace it with a translated name, product nickname, or invented alias.
- On every new conversation, run `ensure-auth` first. It reuses a valid local cache or refreshes an expired/missing cache with the last credential. States such as `local_cache_expired_refreshable` are not evidence that the cloud license expired.
- If the server returns `SKILL_MISMATCH`, stop this Skill and show the exact `authorized_skill_ids` and their safe guide/download targets. Tell the user to install that formally named Skill; do not reset the device or claim the authorization expired.
- For other authorization failures, show the client's structured `error_code` and safe reason. Old servers may still return the generic compatibility message.

Required first step:

```bash
python3 scripts/online_version_guard.py status
python3 scripts/auth_client.py ensure-auth
```

Only if `ensure-auth` reports `credential_missing`, ask for the activation code or phone number:

```bash
python3 scripts/auth_client.py ensure-auth --credential <ACTIVATION_CODE_OR_PHONE>
```

Use remote protected data only through:

```bash
python3 scripts/auth_client.py search "<query>" --top-k 6
python3 scripts/auth_client.py list-refs
python3 scripts/auth_client.py read-ref <name>
```

## Mandatory Creative Retrieval Gate 创作检索硬门

For every creative task—including diagnosis, adaptation, outline, scene, dialogue, script, generation, continuation, and rewrite—do not produce creative content until:

1. The public version check and authorization succeed.
2. At least one task-specific `auth_client.py search` succeeds; project-scale or batch work requires at least two complementary searches.
3. An internal retrieval intake records each adopted anonymous card id, transferable mechanism, intended placement, and originality boundary.
4. Unusable results are reformulated up to two times. If every API base fails, do not claim database use; report degraded mode and obtain permission before continuing without protected evidence.
5. The creative delivery ends with a one-line receipt: `云端机制库：检索 N 次，返回 N 条，采用功能：……`.

After the first successful bind, later commands omit `--credential`; the client reuses the most recent credential and automatically refreshes the local cache when necessary. The stable machine identity is shared by Codex and Claude when they run as the same local OS user; an isolated machine identity is allowed only in explicit test mode. Exceptions to the creative retrieval gate are limited to install/update/auth troubleshooting, format-only conversion, or non-creative organization of user-supplied text. Queries must abstract private material and must not send unpublished names, full plots, trade secrets, or long source passages.

Runtime policy v2 reads `runtime_policy.full_text_mode` from `online-version.json`: `evidence_required` requires usable anonymous full-text evidence, `evidence_optional` allows it as supplemental evidence, `capability_probe_only` is only an endpoint probe, and `unavailable` disables it. A probe or unavailable full-text endpoint never satisfies the mandatory protected creative search above.

Online runtime precedence: any later protected-reference operation, protected library search, or protected full-text operation maps exclusively to the authorized `auth_client.py read-ref`, `search`, or `full-text-search` command. Local protected paths and scripts are non-executable in this edition. Protected data is not present in the public package.
<!-- online-runtime-policy:end -->


# 分镜生成 Skill

把已经完成的剧本转化为可执行的分镜头脚本。先作导演判断，再用云端镜头机制审校；机制卡只能帮助保留、合并或重述既有视觉节拍，不能为了“多用一张卡”而增加镜头。

## 能力结构

在线库提供四层互相制约的机制：

| 层级 | 用途 | 规模 |
|---|---|---:|
| 切换与节奏 | 判断何时切、为什么切、何时不切 | 18 张机制卡 |
| 镜头语法与空间 | 轴线、景别差、视线、机位与运动理由 | 22 张机制卡 |
| 场景镜头方案 | 对话、追逐、揭示、亲密、登场等既有节拍的候选呈现 | 300 张方案卡 |
| 调度与视点 | 影像表、关系角度、走位、空间与机位可行性 | 34 张机制卡 |

审校顺序固定为：先看调度与视点，再比较既有节拍的候选方案，再检查镜头语法与空间连续性，最后裁决切换是否真正服务情感、信息与节奏。

## 工作流

### 1. 先确立全片策略

通读剧本后，先写一段分镜风格策略声明：视觉基调、整体切换密度、信息释放顺序，以及观众应该在何时知道什么。策略未确认前，不进入逐镜拆分。

### 2. 第一遍：无卡设计

这一遍不新增检索：使用创作硬门已取得的结果，但暂不写卡片编号，先独立形成导演判断。

1. 用一句话定义场景要让观众感受到什么。
2. 列出必须传递的信息，并安排释放顺序。
3. 把场景压成 5–8 个观众可见的思想变化。
4. 交代人物、关键物与出口的空间关系，确定主轴、画面左右与运动方向。
5. 先估镜头预算：常规对话通常约 6 切/分钟或更少，激烈动作可接近 25 切/分钟；实际以注意力决策密度为准。
6. 默认一个视觉节拍对应一个主镜头；只有单镜无法表达动作与反应、隐藏与揭示、或视点比较时才拆镜。

### 3. 第二遍：删镜闸门

逐镜回答以下问题；答不上来就合并或删除。

1. 这镜带来了什么不可替代的新信息、情绪、视点、权力关系或空间认知？
2. 能否用一幅“决定性瞬间”概括它的存在理由？
3. 删除它，观众会具体损失什么？
4. 能否用走位、焦点转移、构图变化或有动机的运镜并入相邻镜？
5. 上一个念头是否已完成，下一个念头是否必须从新视点开始？
6. 除必要的定场镜与高潮特写外，它是否同时完成至少两项功能？

### 4. 第三遍：授权检索后的机制审校

创作检索硬门已在设计前完成任务级检索；镜头数收敛后，再针对关键视觉节拍补充精准检索并正式应用机制卡。每个保留镜头最多引用 1 张主机制卡与 1 张辅助检查卡；卡片不改变结论时不必引用。

1. 用调度与视点机制确认：真的需要移动或切换吗？可否用有动机的走位代替？
2. 关键视觉节拍可检索 2–3 个候选方案，但只能选一个进入主分镜表。
3. 检查关系线、景别差、动作切点、视线焦点、机位可行性与方向连续性。
4. 逐切确认：此时优先服务的是情感、信息、节奏、视线还是空间？
5. 检查相邻镜和场间衔接，避免无意跳切、越轴或视线错位。

## 输出格式

每场固定使用一张 Markdown 表：

```text
## 场次 X：[场景标题]（[内/外]·[日/夜]）
情感基调：… 叙事焦点：…
视觉节拍：N 个 ｜ 镜头预算：N 镜 ｜ 最终镜头数：N 镜 ｜ 切换密度：约 N 切/分钟

| 镜号 | 景别 | 机位/角度 | 运镜 | 画面内容（决定性瞬间） | 台词/声音 | 时长 | 切换理由 |
|---|---|---|---|---|---|---|---|
```

“切换理由”先写观众的思想变化，再标明已实际改变审校结论的机制卡编号。关键场景可给 2–3 个有实质差异的备选切法，明确推荐其中一个；只有推荐方案计入主分镜表。

## 交付质量门

- 已说明视觉节拍数、镜头预算与最终镜头数。
- 最终镜头数不超过预算；用户明确要覆盖性素材时，标为“覆盖版”。
- 每个镜头都有决定性画面与删除代价。
- 没有仅为换景别、展示技巧或凑引用而保留的镜头。
- 相邻镜若承担同一信息与情绪功能，默认合并。
- 机制检索结果只作导演判断的证据，不能替代对剧本、表演与现场条件的判断。

## 边界

- 故事、结构、人物与对白开发，交给对应的剧作技能。
- 多集剧集的分集与分场，交给剧集或短剧技能。
- 本 skill 从剧本完成处开始，专注镜头、切换、空间与视觉叙事。
- 不请求或输出底层资料的来源名称、路径、文件清单或大段文本；在线结果只用于机制级创作判断。
