CtrlK
BlogDocsLog inGet started
Tessl Logo

remotion-upgrade

Upgrade Remotion, and related packages

59

Quality

69%

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/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 content is a tight, command-driven upgrade runbook with a clear decision branch and a final verification step. Its only weaknesses are a couple of non-copy-paste spots in the manual path and the absence of an explicit fix-and-revalidate loop after the diff review.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence — no explanations of what Remotion or package managers are, no padding; each numbered step and command earns its place.

5 / 5

Actionability

Mostly executable guidance with concrete commands ("npx remotion upgrade", "npm view remotion version", the full "npx skills update ... --yes" list, "npx remotion versions"), but the "@remotion/studio@<version>" placeholder requires substitution and "Run the project's package manager to update its lockfile" is not a concrete command — minor gaps.

4 / 5

Workflow Clarity

A clear 1–5 sequence with an explicit CLI-vs-manual branch and a verification step ("Review the manifest and lockfile diff... run npx remotion versions as an additional check"), but for a batch manifest/lockfile operation there is no explicit fix-and-retry feedback loop, so it falls short of the 5 anchor.

4 / 5

Progressive Disclosure

The skill is under 50 lines with no need for external reference files; the numbered structure is well-organized, the one external link (Remotion releases changelog) is appropriately placed at the end, and the only bundle file (assets/remotion-icon.svg) is correctly left out of the body.

5 / 5

Total

18

/

20

Passed

Description

52%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 short and distinctive but under-specified: it states a single generic action with no explicit trigger guidance and no natural synonym coverage. It reads closer to a minimal domain label than to a complete capability + trigger description.

Suggestions

Add an explicit trigger clause, e.g. "Use when the user asks to upgrade or update Remotion, @remotion/* packages, or the Remotion version in a project."

Include natural synonyms users actually say — "update Remotion", "bump Remotion version", "upgrade @remotion packages" — to broaden trigger coverage.

State one or two more concrete capabilities, e.g. aligning auxiliary packages (zod, mediabunny) and updating the lockfile and installed Remotion skills.

DimensionReasoningScore

Specificity

The description names the domain ("Upgrade Remotion") but the action set is minimal and generic, akin to "Processes PDF files" — no second concrete capability (e.g., lockfile updates, related package alignment, or skill updates) is stated.

2 / 5

Completeness

The "what" is clear (upgrade Remotion and related packages), but there is no "Use when..." clause or any trigger guidance; per the guidelines a missing when-clause caps completeness at 3.

3 / 5

Trigger Term Quality

"Upgrade", "Remotion", and "related packages" are relevant keywords, but common natural variations users would say — "update Remotion", "bump the Remotion version", "@remotion/* packages" — are missing.

3 / 5

Distinctiveness Conflict Risk

"Remotion" is a distinctive named framework with a clear niche (Remotion upgrades specifically); the risk of triggering for an unrelated skill is minimal.

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