reviewer-review-outline
Skill21 starsChanged 2 months agoMITView on GitHub
在已采用单集大纲且需要独立评估时,审查场景节奏、因果、资产和结局落点。
In this repository34 other files it gives its agents.
- AGENTS.mdAGENTS.md
- auto-videoSkill
- check-videoSkill
- creator-create-assetsSkill
- creator-fix-asset-imageSkill
- creator-fix-assetSkill
- creator-generate-imagesSkill
- creator-local-referenceSkill
- creator-provider-dreaminaSkill
- creator-update-recordsSkill
- director-arcSkill
- director-fix-arcSkill
- director-fix-outlineSkill
- director-input-confirmSkill
- director-orchestrateSkill
- director-outlineSkill
- director-plot-optionsSkill
- edit-storySkill
- generate-videoSkill
- repair-storySkill
- reviewer-review-arcSkill
- reviewer-review-asset-prompt-singleSkill
- reviewer-review-asset-promptsSkill
- reviewer-review-assets-visualSkill
- reviewer-review-asset-visual-singleSkill
- reviewer-review-scriptSkill
- reviewer-review-shot-inputsSkill
- reviewer-review-storyboardSkill
- scriptwriter-fix-scriptSkill
- scriptwriter-scriptSkill
- series-videoSkill
- short-videoSkill
- storyboarder-fix-storyboardSkill
- storyboarder-storyboardSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 38
Read 实际配置(SVD_CONFIG 或 config.md)
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
输入
委托说明当前集数 ep、短篇/新系列/续集语境、审核目标、保留要求与参考路径;mode 是语境描述,不是函数参数。
文件读取
story/episodes/{ep}/outline.md— 必须读取(受托 review 目标)- 实际配置 SVD_CONFIG(未设时 config.md)— 必须读取(用户每集时长及确认边界 / 场景数量目标 / 世界观锚点);本文及配套指南中的 config.md 均指该实际配置
story/arc.md— series 且存在、适用时读取;不因缺少 arc 要求补建assets/目录 — 必须扫描(核对 asset 引用是否 dangling)${CLAUDE_PLUGIN_ROOT}/skills/_meta/rules/output-language.md— 必须读取(语言一致性)${CLAUDE_PLUGIN_ROOT}/skills/_meta/rules/review-meta-rules.md— 必须读取(review 意见格式规约)
专业参考
${CLAUDE_PLUGIN_ROOT}/skills/reviewer-review-outline/series.md— 系列的连续性、阶段推进与规划契约参考${CLAUDE_PLUGIN_ROOT}/skills/reviewer-review-outline/short.md— 短篇的注意力、情绪落点与结构参考
审核边界
本 skill 是可选规划审核;遵守共享规则的独立新 Reviewer context/主 AI relay 协议,只写 reviews/{ep}/outline.md 的 Markdown 意见与轮次,不增加 runtime kind/evidence,不调度修复或替用户批准。不以规划缺失阻塞无此请求的制作,不运行全生产 readiness。读取失败/无法判定为 unknown。
适用指南
按当前委托选用 series.md 或 short.md 的专业维度;不把无关模式要求带入本集。下面按证据与判断分组,不规定固定思考顺序。
当前材料
- Read
story/episodes/{ep}/outline.md - Read 实际配置(SVD_CONFIG 或 config.md)
- mode∈series 且相关文件存在: Read
story/arc.md - Glob
assets/characters/*.md,assets/locations/*.md建立已注册 asset 集合
时长契约
DURATION=$(bash "${CLAUDE_PLUGIN_ROOT}/scripts/read-config.sh" "每集时长目标" "${SVD_CONFIG:-config.md}")结合用户已确认边界换算秒数;仅已确认 ±10% 的单值用 bash "${CLAUDE_PLUGIN_ROOT}/scripts/scene-duration.sh" "story/episodes/{ep}/outline.md" --target <N>。显式范围/更严格限制用 --target-min <M> --target-max <X> 替换 target 参数,精确目标 M=X,不额外放宽,也不把单值格式当容差同意。系列核对初始共同目标,不用前集实际时长。
缺失、空白、读取失败或边界不清/冲突为 unknown,交顶层主 AI/Director 澄清,实际答复回原审核任务,不回退模板或其他配置、不替用户确认。已有明确决定复用。实跑并保留 sum、边界、退出状态;超界写具体意见,脚本无法执行为 unknown。不以修订次数或审美判断放宽预算,不要求补建未采用的大纲。
叙事判断
阻塞意见聚焦框架与确认意图;有价值的措辞或节奏建议可另列理由,不作为审美门禁。意见供生产 Director 协调,不要求作者逐条照搬或调用指定修复方法。
质性检查项(四维):
- 场景关系是否符合已确认叙事意图,在需要理解时提供足够的时空与因果线索;允许回溯、交叉叙事或高潮先行,不要求相邻场景互为因果
- 场景过渡是否自然(时空切换有铺垫 / 交代)
- 是否存在被砍掉的因果关键环节
- arc 必需事件覆盖(仅 series 已采用 arc 时):对照本集分配的必需事件,确认在 outline 可识别;跨多集节点不要求每集重复覆盖全部事件
审核记录
写入 reviews/{ep}/outline.md(append 模式,同一目标重审串行)。
Round 自检:
- Read
reviews/{ep}/outline.md(若不存在,本次为第 1 轮;否则按最大标题轮号递增) - 用 Write(首次创建)或 Edit(append;oldString 用文件末尾 50 字符 anchor)追加本轮段
本轮段格式:
通过时(仅 heading 行):
## 第 {N} 轮 ({YYYY-MM-DD HH:MM}) - 通过不通过时:
## 第 {N} 轮 ({YYYY-MM-DD HH:MM}) - 需修改 ({M} 项)
1. **{位置(场景 N / 字段名)}:** {问题描述} → {修改建议}
2. **{位置}:** {问题描述} → {修改建议}注意:每轮段前留一个空行,与上一轮段隔开。
规则
重审聚焦关键问题,不以次数豁免验收。具体权利风险按共享规则升级,不因现实名称自动要求改名。
输出
文件操作
- 使用 Write 或 Edit 维护
reviews/{ep}/outline.md(append 模式,详见审核记录)
返回内容
- 简报:
pass、needs_revision {M}或unknown({M} = 本轮意见条数)→ 返回原生产 Director - 详细意见已写入文件,下游 director-fix-outline 自行读取该文件最后一轮段
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

