Content
86%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 content is an exemplary lean router: a precise dispatch table, explicit scope boundaries, and verified one-level-deep references into a well-organized eight-file reference bundle. The only weaknesses are minor — a few instructions assume context (the task contract's location) and validation specifics live in referenced files rather than the body.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The ~19-line body contains no concept explanations, no padding, and no content Claude already knows; every sentence routes, bounds, or sequences work (e.g. "their metadata is a menu, not a preload checklist", "Do not expand a targeted task into a complete-film workflow"). This matches the 'lean and efficient; every token earns its place' anchor. | 5 / 5 |
Actionability | Concrete guidance dominates: the work-to-Skill mapping table, "Generation/editing defaults to `acceptance=studio-preview`", "Prepare scene anchors before synthesis", "silent/media/music work skips TTS", and "Return the actual source and completed output paths". Minor gaps keep it below 5 — e.g. "Read the active task contract" never says where that contract lives, and acceptance criteria are delegated to a reference file. | 4 / 5 |
Workflow Clarity | A clear sequence is present (identify scope → load the one matching Skill → storyboard-to-production progression → checks → return paths) with named checkpoints ("use component/preview checks and Studio playback", "applicable acceptance"). It is not 5 because validation details are implicit in referenced files rather than explicit in-body, and not 3 because checkpoints are named, not absent. | 4 / 5 |
Progressive Disclosure | The body is a clear overview with well-signaled, one-level-deep references ([shared session boundaries](references/video.md), [its input contract](references/video.md#uploaded-video-input), [acceptance](references/video-acceptance.md)); all referenced files exist in the references/ bundle, the #uploaded-video-input anchor matches a real heading, and detail is appropriately split out rather than inlined. This matches the top anchor exactly. | 5 / 5 |
Total | 18 / 20 Passed |