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

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./packages/skills/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

86%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 exemplary lean, actionable procedure: concrete commands, a clear conditional workflow with inspection and verification steps, and precise project-preservation guidance (exact versions, workspace/catalog conventions, unrelated changes). The only minor gaps are the instructional (non-executable) manifest-edit step in the manual path and the absence of a recovery loop if the final version check fails.

DimensionReasoningScore

Conciseness

The body is lean and assumes competence: every step instructs, no concepts are over-explained, and the single link (Remotion releases/changelog) is a useful pointer rather than padding. Every token earns its place, matching the 'lean and efficient' anchor.

5 / 5

Actionability

Mostly executable: concrete copy-paste commands cover the CLI path (`npx remotion upgrade`, `npm view remotion version`, `npm view @remotion/studio@<version> dependencies --json`, `npx skills update ... --yes`) and verification (`npx remotion versions`). The manual path's manifest-editing step and 'Run the project's package manager to update its lockfile' are instructional rather than executable, leaving minor gaps that keep it below the fully copy-paste-ready anchor.

4 / 5

Workflow Clarity

A clear 5-step sequence with an explicit decision branch (CLI available vs. manual) and a verification checkpoint (review the manifest/lockfile diff, ensure one version, run `npx remotion versions`). Validation is present, so the batch-operation cap does not apply, but there is no error-recovery loop telling Claude what to do if the version check fails — fitting 'clear sequence with most checkpoints; minor validation gaps' rather than the feedback-loop anchor.

4 / 5

Progressive Disclosure

The skill is under 50 lines, single-purpose, and needs no external references; the numbered procedure is well-organized and the only bundle file (assets/remotion-icon.svg) is an icon requiring no in-body reference. Per the rubric's simple-skill guideline, well-organized sections alone warrant a 5.

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 is concise and names a distinct niche (Remotion upgrades), but it is minimal: only one action, no trigger synonyms, and no 'when to use' guidance. It reads as a clear 'what' statement that stops short of the explicit trigger coverage the strongest examples demonstrate.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user asks to upgrade or update Remotion, @remotion/* packages, or Remotion dependencies'.

Include natural trigger synonyms such as 'update Remotion', 'Remotion version', and 'bump Remotion packages' so users' phrasing variations match.

Name one or two more concrete capabilities (e.g., aligning auxiliary packages like zod and mediabunny, updating project-local Remotion skills) to raise specificity.

DimensionReasoningScore

Specificity

The description names the domain ('Remotion') and one concrete action ('Upgrade') extended to 'related packages', matching the 1-2-concrete-actions anchor. It falls short of the score-4 anchor, which expects several specific actions listed.

3 / 5

Completeness

It clearly answers 'what' (upgrade Remotion and related packages) but provides no 'when' — no 'Use when...' clause or equivalent trigger guidance, which caps completeness at 3 per the judging guidelines. This exactly matches the score-3 anchor example of a clear 'what' with 'when' missing.

3 / 5

Trigger Term Quality

'Upgrade Remotion' is a natural phrase a user would say, but the keyword set is thin — common variations like 'update Remotion', 'Remotion version', or 'bump Remotion' are absent. This fits 'some relevant keywords but missing common variations or synonyms' rather than the good-coverage anchor.

3 / 5

Distinctiveness Conflict Risk

'Remotion' pins a clear niche with minimal conflict risk, but 'and related packages' leaves minor overlap with a generic dependency-upgrade skill, fitting 'mostly distinct; minor overlap risk with closely related skills' rather than the minimal-conflict score-5 anchor.

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/skills/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.