Content
67%Weight 40%Scale 1-5Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The body delivers concrete, domain-specific guidance organized along the real production pipeline, with an actionable field-level shot contract and incremental state rules. Its weaknesses are repetition of the same rules across sections and the absence of a worked panel example that would make the output structure copy-paste ready.
Suggestions
Consolidate repeated rules: state the 'no fixed shot count / duration' prohibition and the state_in/cut_in copying rules once each in their owning section instead of restating them in planning and review sections.
Add one worked example of a panel with its shot_design object (including a continuous successor showing state_delta), so the contract structure is executable rather than inferred.
Consider moving the shot_design field reference and the incremental-contract details into a reference file, keeping SKILL.md as a lean overview with a clearly signaled link.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is dense rule-only prose with no padding over concepts Claude already knows, but it repeats key rules across sections: the 'no fixed shot count' prohibition appears in 按原文规模规划生成段 and 审阅建议与保存, and the state/cut copying rules ('state_in 逐项复制前镜 state_out', 'continuous 镜逐字复制前镜 cut_out') are stated twice in detail. Mostly efficient but could be tightened by consolidating these. | 3 / 5 |
Actionability | Concrete field-by-field shot_design contract (focus/viewer_gain/framing/axis/movement/motivation/transition/cut_in/cut_out/state_in/state_out) with executable value rules ('state_delta 只列真实变化后的已有属性，无变化写 {}', '首镜及明确换时/换地镜给完整 state_in') and a clear output order (scene_plan summary then panels). Not 5 because there is no worked example of a panel or shot_design JSON, so the exact structure must be inferred. | 4 / 5 |
Workflow Clarity | Sections follow the actual pipeline (design → segment planning → cross-shot contract → refinement/first frame → review → media prompts → save) with explicit '先...再...' sequencing, and review checkpoints with fix loops exist ('先修对应镜', '真实结果不符时进入对应镜头复核'). Not 5 because the checkpoints are scattered in prose rather than consolidated into a reviewable sequence or checklist. | 4 / 5 |
Progressive Disclosure | A single well-organized SKILL.md with clear section headers, no dangling references, and no bundle files to navigate. Not 5 because at ~60 dense lines the shot_design field reference and the incremental-contract rules are substantial enough that they could arguably live in a separate reference file, keeping the overview leaner. | 4 / 5 |
Total | 15 / 20 Passed |