Content
71%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.
A highly actionable, well-sequenced workflow with a copy-paste-ready dispatch command and good failure guidance. It loses points for repeating the hyperframes special case at every step, inlining time-sensitive model version numbers, and a resource map that references an example.html file not present in the bundle.
Suggestions
Fix the Resource map to match the actual bundle: either ship example.html or remove it (and the preview entry) from the map.
Consolidate the four scattered hyperframes-html notes into one 'hyperframes-html variant' subsection and reference it from each step.
Move the per-model version-sensitive limits (Seedance 2 / Kling 4 / Veo 3 caps) into a single model-capabilities reference so they can be updated without touching the workflow.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Mostly lean and competent, but the `hyperframes-html` special case is narrated four separate times (intro "Special case", Step 1 "skip the extra pre-dispatch narration", Step 2 "write a concise motion-design brief instead", Step 4 "keep the reply especially short") and could be consolidated. Version-sensitive info ("Seedance 2 caps at 10s; Kling 4 supports up to 10s…; Veo 3 supports 8s with audio") is stated inline rather than in an old-patterns/deprecated section, which the guidelines penalize. Not 4 — the repetition and version pinning are more than 'minor instances that could be trimmed'. | 3 / 5 |
Actionability | The dispatcher block is fully executable with every parameter and placeholder specified ("$OD_NODE_BIN" "$OD_BIN" media generate --project… --model "<videoModel from metadata>" … --output "<short-slug>-<seconds>s.mp4"), the expected return shape is given ("prints one line of JSON: {\"file\": …}"), and per-model prompt formats ("Seedance: motion + camera + mood; Kling: subject + camera + style; Veo: subject + cinematography + sound") plus per-model hard limits cover the common cases, including the hyperframes variant. Nothing is pseudocode. | 5 / 5 |
Workflow Clarity | A clear Step 0→4 sequence (read metadata → plan shot → compose prompt → dispatch → hand off) with a pre-dispatch checkpoint ("show this to the user as a one-sentence plan… they can redirect cheaply") and explicit failure handling ("When the underlying model fails (NSFW filter, content policy, timeout), keep the raw provider error in the tool trace… Don't silently retry"). Not a destructive/batch operation, so the validation cap doesn't apply; not 5 because validation is expressed as after-the-fact 'Hard rules' rather than explicit inline checkpoints or a validate→fix→retry loop. | 4 / 5 |
Progressive Disclosure | Sections are well-organized, but the bundle's actual structure (SKILL.md only — no example.html, no references/scripts/assets directories) contradicts the declared "Resource map", which lists example.html (also referenced by the frontmatter preview entry). A resource map pointing at a nonexistent file is a real navigation defect, not a minor gap; a 4 would require references that are 'mostly clear' and accurate. All model-capability detail living inline in Step 0 could also sit in a small reference file. | 3 / 5 |
Total | 15 / 20 Passed |