Content
82%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 tight, highly actionable overview: concrete strong/avoid phrase pairs, intent-to-move mappings, and a clear output contract teach the skill's judgment without padding. The main weaknesses are an unnumbered workflow whose reference-file order is implicit, and reference links that point outside the skill bundle rather than to files that ship alongside it.
Suggestions
Reference the bundle files with paths inside the skill's own directory (e.g., references/quick-ref.md) and ship them with the skill, so the ../../references/ links resolve without an unstated parent-repo layout.
Number the core workflow (load Director's Read → classify → build the camera record → select the move → emit the output contract) so the order of loading quick-ref, directing-engine, and cinematography-shot-language is unambiguous.
Trim the Intent section's empathy-metaphor sentences to a single directive line and show one example of the final 'prompt-ready integrated sentence' the Output Contract asks for.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is dense directive prose with almost no filler — tables, one-line rules, and terse anchors like '24mm wide lens for spatial energy'. Minor over-explanation appears in the Intent section ("Camera grammar is empathy mechanics: a push-in is leaning closer, a locked frame is holding your breath"), which teaches a concept Claude already knows and could be trimmed to one sentence. | 4 / 5 |
Actionability | The Need/Strong-phrase/Avoid table gives copy-paste-ready camera phrases covering five common cases ("slow dolly-in from medium close-up to tight close-up as Character A lowers the envelope"), Move Selection maps intents to specific moves, Continuity Rules supply exact reference-tag phrasing ("@Video1 controls camera rhythm only; do not transfer performer, room, logo, or identity"), and the Output Contract enumerates deliverables. For an instruction-only skill this is fully actionable guidance. | 5 / 5 |
Workflow Clarity | A sequence is stated up front ("Before producing prompt text... load the Director's Read, classify the brief, and complete its canonical narrative or non-narrative record") and the Output Contract defines the endpoint. It is not a 5 because the steps are not crisply ordered across the loaded reference files (quick-ref vs. directing-engine vs. cinematography-shot-language have no stated order), and validation is implicit rather than a checkpoint ("A prompt-ready camera phrase should be physically possible"). | 4 / 5 |
Progressive Disclosure | The ~50-line body stays a lean overview and signals one-level-deep references with a purpose per file ("Load quick-ref for prompt assembly", "directing-engine... to derive the move"). It is not a 5 because every referenced path points to "../../references/" — outside the skill directory — and no references/ directory exists in this bundle, so the navigation cannot be verified and the links resolve only inside an unstated parent layout. | 4 / 5 |
Total | 17 / 20 Passed |