Content
87%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 excellent example of a lean, command-driven skill: fully executable commands, clear conditional branching, and a final verification step. Its one real weakness is the absence of an error-recovery loop for what is a batch manifest/lockfile edit — the verification step checks consistency but never says what to do on failure.
Suggestions
Add an explicit fix-retry loop to step 5, e.g. "If any Remotion package differs from the target version, correct the manifest and re-run the lockfile update before proceeding" — this is the specific gap that caps workflow clarity for a batch operation.
State how to determine CLI availability (e.g. check package.json/devDependencies for @remotion/cli) so the branch decision is mechanical rather than inferred.
Mention running the project's build or tests after the upgrade to confirm the new Remotion version does not break compilation, complementing the version-consistency check.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The ~30-line body is lean and assumes Claude's competence: no concept explanations, no padding — every line is an instruction, a copy-paste command, or a useful pointer ("The [Remotion releases](...) contain the changelog and may be useful"). Matches anchor 5; there is nothing to trim for anchor 4. | 5 / 5 |
Actionability | Fully executable commands cover both paths: "npx remotion upgrade", "npm view remotion version", "npm view @remotion/studio@<version> dependencies --json", "npx skills update ... --yes", and "npx remotion versions"; the <version> placeholder is filled by the preceding step's command, and manual instructions specify exact conventions (preserve dependency sections, use the mediabunny version for @mediabunny/*). | 5 / 5 |
Workflow Clarity | The numbered sequence with explicit branching (CLI vs. manual) and a final verification step would rate 4, but this is a batch operation — "Find every installed remotion and @remotion/* dependency ... and upgrade them all" plus lockfile regeneration — and there is no validate→fix→retry feedback loop: step 5 says "Ensure all Remotion packages use one version" without any instruction for what to do when the check fails. The rubric's feedback-loops rule caps batch workflows without a fix-retry loop at 3, so 4 does not apply. | 3 / 5 |
Progressive Disclosure | The skill is under 50 lines with no need for external reference files (the bundle contains only assets/remotion-icon.png, an icon), and the body is a well-organized numbered list with a clearly signaled external link to the Remotion releases — the simple-skill guideline scores this at 5. Not 4: no content is inlined that belongs in a separate file. | 5 / 5 |
Total | 18 / 20 Passed |