Content
100%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 exemplary for a simple, single-purpose skill: fully executable commands, explicit verification steps for both Studio load and composition preview, clear branching across client types, and a tight flags table with no wasted tokens. No changes needed.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The ~30-line body is lean with zero padding: no concepts Claude already knows, and every operational detail (URL printing behavior, already-running case, in-app browser caveat) earns its place. It matches the 'lean and efficient; assumes Claude's competence' anchor. | 5 / 5 |
Actionability | Fully executable, copy-paste-ready commands ("npx remotion studio", "npx remotion studio --no-open") with concrete flag values (--log levels, --port, --force-new) and explicit handling of the common cases (Cursor, other clients, Studio already running). Matches the top anchor. | 5 / 5 |
Workflow Clarity | A simple single-purpose skill with an unambiguous sequence — start Studio as soon as the project can run, before building the composition, keep it open while working — plus explicit validation checkpoints ("verify that Studio loads", "verify that its video preview loads") and an error-avoidance rule ("Do not use --no-open if you cannot open the URL"). Meets the simple-skill exception for a top score. | 5 / 5 |
Progressive Disclosure | Under 50 lines, no external references needed (the only bundle file is an icon asset, consistent with the body's lack of file references), and content is well-organized into a main workflow plus a 'Useful flags' section. Per the rubric's simple-skill guidance, this earns a 5 with just well-organized sections. | 5 / 5 |
Total | 20 / 20 Passed |