CtrlK
BlogDocsLog inGet started
Tessl Logo

remotion-upgrade

Upgrade Remotion, and related packages

60

Quality

71%

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
SKILL.md
Quality
Evals
Security

Quality

Content

93%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 an exemplar of a lean, actionable upgrade workflow: concrete commands, a clear CLI-vs-manual branch, and an explicit verification step. The only gap is the absence of an explicit error-recovery feedback loop for the batch package-editing operation.

DimensionReasoningScore

Conciseness

The body is lean and tightly scoped: numbered steps plus short executable commands, with no padding or explanation of concepts Claude already knows, matching the 'lean and efficient; every token earns its place' anchor.

5 / 5

Actionability

It provides copy-paste-ready commands (npx remotion upgrade, npm view remotion version, npx skills update ... --yes, npx remotion versions) covering both the CLI-available and manual-upgrade branches, matching 'fully executable; specific examples cover the common cases'.

5 / 5

Workflow Clarity

The five-step sequence is clear and includes an explicit verification step (review diff, ensure single Remotion version and compatible Mediabunny version, run npx remotion versions), but it lacks an explicit fix-and-retry feedback loop, so it sits at the 'clear sequence with most checkpoints present' anchor rather than 5.

4 / 5

Progressive Disclosure

This is a single-purpose skill well under 50 lines with no need for external references (references/ and scripts/ are empty), and the content is well-organized into numbered steps with code blocks, qualifying for the simple-skill exception to score 5.

5 / 5

Total

19

/

20

Passed

Description

48%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 product-specific and concise but minimal: it states a single action and lacks any explicit "when to use" trigger guidance. Adding a "Use when..." clause and synonyms like "update" or "bump version" would materially raise completeness and trigger-term quality.

Suggestions

Append a 'Use when...' clause naming concrete triggers, e.g. 'Use when the user asks to upgrade or update Remotion, bump its version, or align @remotion/* and mediabunny packages.'

Add natural synonyms such as 'update', 'bump', or 'version' alongside 'Upgrade' to broaden trigger-term coverage.

Specify the 'related packages' (e.g. '@remotion/* and Mediabunny') so the action is concrete rather than generic.

DimensionReasoningScore

Specificity

The description names the domain and one concrete action ("Upgrade Remotion") but appends a generic "and related packages" with no further specificity, fitting the 'actions are minimal or generic' anchor better than the multi-action anchor of 3.

2 / 5

Completeness

It clearly states what the skill does (upgrade Remotion and related packages) but provides no "Use when..." clause or equivalent trigger guidance, so completeness is capped at 3 per the judging guidelines.

3 / 5

Trigger Term Quality

"Upgrade Remotion" is a natural phrase a user would say, but the description omits common variations and synonyms such as "update", "bump", "version", or "dependencies", matching the 'some relevant keywords but missing common variations' anchor.

3 / 5

Distinctiveness Conflict Risk

"Upgrade Remotion" carves out a clear, product-specific niche with minimal conflict risk, though it could overlap slightly with a generic dependency-upgrade skill, matching the 'mostly distinct; minor overlap risk' anchor.

4 / 5

Total

12

/

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.

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