Content
92%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.
An exceptionally operational skill body: exact commands, an ordered and validated pipeline with named error-recovery actions, and a clean overview-to-references split with all referenced files real. The only notable weakness is mild verbosity from repeated rules and one overloaded Commands paragraph.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is dense and telegraphic with essentially no explanation of concepts Claude already knows — every line carries skill-specific routes, flags, exit codes, or rules. It falls just short of the lean/anchor-5 bar because the master-still handoff rule and the "sheets are for FX, icons and props" rule are each restated about three times across sections, and the Commands section is a single ~400-word paragraph that could be split or trimmed. | 4 / 5 |
Actionability | Fully executable guidance throughout: complete command lines with flags ("master_still.py generate --spec <json> --takes 3 --output-dir <new>"), a need-to-route pipeline table mapping every task to a specific tool invocation, documented exit codes (1/2/3/4) and env vars. This matches the anchor for copy-paste-ready commands covering the common cases. | 5 / 5 |
Workflow Clarity | The master-still workflow is a numbered 6-step sequence (spec, generate, choose, fix-by-edit, approve, motion handoff) and the processing pipeline is given as an explicit ordered chain. Validation is pervasive for these batch operations — --strict-qc publishes nothing on failure, QA envelopes with named checks, exit 4 on QA fail — and feedback loops are concrete (key_ring_spill -> "add --despill-radius 1 or --key-quality soft"; duplicated half-cycle -> regenerate the second half), plus an acceptance checklist. This matches the anchor for explicit validation steps with error-recovery loops. | 5 / 5 |
Progressive Disclosure | The body is an overview that pushes all deep detail to one-level-deep references (all 12 referenced .md files and the schema files exist in the bundle, including the hibit.md FX-route anchor), each labeled with its scope in the References section, and an inline need-to-route table for navigation. This matches the anchor for a clear overview with well-signaled one-level-deep references and easy navigation. | 5 / 5 |
Total | 19 / 20 Passed |