CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

remotion-upgrade

Upgrade Remotion, and related packages

Quality

75%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./packages/codex-plugin/skills/remotion-upgrade/SKILL.md

The canonical home for this skill is remotion-upgrade in remotion-dev/skills

SKILL.md
Quality
Evals
Security

Quality

Content

87%Weight 40%Scale 1-5

Reviews 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.

DimensionReasoningScore

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

Description

53%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description states a clear, distinct core action but is minimal: it omits any "Use when..." trigger guidance (capping completeness), leaves "related packages" undefined, and misses natural synonyms like "update". It reads as a terse label rather than a discoverable, trigger-rich description.

Suggestions

Add a trigger clause, e.g. "Use when the user asks to upgrade or update Remotion, bump the Remotion version, or align @remotion/* packages" — this lifts completeness past its capped 3.

Replace the vague "and related packages" with specifics such as "all @remotion/* packages plus auxiliary dependencies (zod, mediabunny)" so the scope is concrete.

Include common natural phrasings users would say ("update Remotion", "Remotion version mismatch", "@remotion/* packages") to improve trigger-term coverage.

DimensionReasoningScore

Specificity

"Upgrade Remotion" is a single concrete action naming the domain, but "and related packages" is generic with no specifics about which packages (@remotion/*, zod, mediabunny). Fits anchor 3 (domain + 1-2 concrete actions, not comprehensive) better than anchor 2 because "upgrade" is specific rather than generic; not 4 because most capabilities the body actually covers are unmentioned.

3 / 5

Completeness

The "what" is clear ("Upgrade Remotion, and related packages") but there is no "when" — no "Use when..." clause or equivalent trigger guidance, which the judging guidelines explicitly cap at 3. Not 4 because the "when" is entirely absent rather than merely weak.

3 / 5

Trigger Term Quality

"Upgrade", "Remotion", "packages" are relevant natural terms a user would say, but common variations are missing ("update Remotion", "Remotion version", "@remotion/* packages"). Matches anchor 3 (some relevant keywords, missing common variations); not 4 since coverage is only two content words and the most common synonym "update" is absent.

3 / 5

Distinctiveness Conflict Risk

"Remotion" carves a distinct niche that is unlikely to trigger the wrong skill family, but the skill ecosystem has many close siblings (remotion-render, remotion-studio, remotion-best-practices, etc.), creating minor overlap risk — anchor 4. Not 5: only two content words with no additional distinguishing trigger phrases.

4 / 5

Total

13

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository

remotion-dev/remotion

Path

packages/codex-plugin/skills/remotion-upgrade/SKILL.md

Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.