Content
80%Weight 40%Scale 1-3Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
A lean, actionable overview that gives concrete scaffold/preview/still commands and a clean index of topic rule files, but it relies entirely on ~30 referenced ./rules/*.md files that do not exist, breaking progressive disclosure and leaving most promised detail inaccessible.
Suggestions
Provide the referenced ./rules/*.md bundle files (or remove the dangling links) so progressive disclosure actually resolves; currently every 'load the rules/X.md file' pointer and the entire 'How to use' index points to non-existent files.
Add one explicit validation/feedback step where a render could fail (e.g. 'if `remotion still` errors on the composition id, confirm it matches a registered composition in Root before retrying') so workflow_clarity moves from a set of recipes to a checkpointed process.
De-duplicate the 5 rule files that appear both as their own sections and in the 'How to use' list, or convert the dedicated sections into single-line index entries, to remove the only redundancy in an otherwise lean body.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is lean and assumes Claude's competence — it never explains what Remotion, React, or video rendering are, and every section is a terse recipe or pointer, e.g. 'npx remotion still [composition-id] --scale=0.25 --frame=30'. The only mild redundancy is that 5 rule files (subtitles, ffmpeg, silence-detection, audio-visualization, sfx) get both a dedicated section and an entry in the 'How to use' index, but that duplication serves navigation rather than padding. | 3 / 3 |
Actionability | It gives fully executable commands — 'npx create-video@latest --yes --blank --no-tailwind my-video', 'npx remotion studio', 'npx remotion still ... --frame=30' — with copy-paste-ready flags and a concrete note that '--frame=30' is the one-second mark at 30 fps. The '[composition-id]' placeholder is appropriate rather than pseudocode. | 3 / 3 |
Workflow Clarity | Tasks are presented as independent recipes (setup, preview, render check, captions, etc.) rather than one sequenced multi-step process, and the only checkpoint — the 'Optional: one-frame render check' sanity step — is framed as a check but lacks an explicit validate→fix→retry feedback loop. It is not a score-1 (steps are individually unambiguous) and not a score-3 (no cohesive workflow with explicit validation checkpoints). | 2 / 3 |
Progressive Disclosure | The body is well-organized as an overview with clearly signaled, one-level-deep references and a navigable index of ~30 rule files — structurally a score-3 design — but no ./rules/ directory or any referenced file actually exists, so the disclosure leads nowhere and navigation is broken. That missing bundle structure caps it at 2 rather than 1 because the SKILL.md itself is well-structured and references are clearly signaled. | 2 / 3 |
Total | 10 / 12 Passed |