Content
77%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 is an efficient, well-sequenced operational spec with explicit validation gates and concrete state schemas — workflow clarity is a genuine strength. Its main defects are delegated substance living in reference files that are missing from the evaluated bundle, and one overloaded step-2 paragraph that hurts readability more than clarity of sequence.
Suggestions
Ship or fix the reference bundle: ../../references/directors-read.md, prompt-compiler.md and the other eight linked files are absent, so the skill's core mechanisms cannot be loaded; verify the relative paths resolve from the skill directory.
Split Build Process step 2 into separate steps (lane classification, ten-field record, directing-engine spine) — the current single sentence buries five instructions.
Deduplicate the reference-load instructions between the opening paragraph and the Build Process, or state the loading rule once and reference it.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is dense and assumes competence — no space is spent explaining what video generation or continuity is; every section carries operational rules. Minor trimming is possible: step 2 of the Build Process is a single ~120-word sentence packing five distinct instructions, and the reference-load list in the opening paragraph repeats content stated again in the Build Process, keeping it just below the 'lean, every token earns its place' anchor. | 4 / 5 |
Actionability | For an instruction-only skill the guidance is highly concrete: exact field lists for clip and scene cards, specific defaults ('max_chain_depth (default 2, hard ceiling 3)'), a worked micro-example ('exit terminal and reach open car door'), and a numbered 11-item output contract. Below 5 because several key mechanisms (the Director's Read record, the prompt compiler, the transfer contract) are delegated to reference files that are not present in the bundle, leaving those steps not fully executable as written. | 4 / 5 |
Workflow Clarity | The 11-step Build Process is explicitly ordered with real validation checkpoints: 'After generation, require the clip or final frame, record observed start/end state, reconcile physical and dramatic handoffs, and only then compile the next prompt', plus the intent-echo gate 'confirmed before generation spends money' and the chain-cap/re-anchor rules. This matches the anchor of clear sequence with explicit validation and a feedback loop; the only friction is readability of the step-2 run-on sentence, not the sequence itself. | 5 / 5 |
Progressive Disclosure | Structurally the body is a good overview with ten clearly named, one-level-deep, conditionally loaded references ('Load dense-storyboard-mode when the request contains many shots'), which reads like a 4-5. However, none of the referenced files (../../references/directors-read.md and the other nine) exist in the bundle — no references/ directory is present — so the disclosure structure is not actually navigable and key delegated content is inaccessible. That drops it to 'references present but not resolvable / organization incomplete'. | 3 / 5 |
Total | 16 / 20 Passed |