Skip to content
SkillModel-led420 tokens in use

remotion-upgrade

Upgrade Remotion, its related packages, matching auxiliary versions and the installed Remotion skills.

7,648 stars on the repositoryremotion-dev/skills · skills/remotion-upgrade
npx skills add remotion-dev/skills
View source

Install command as written in the repository's README

Skill label

measured from its files

What installing remotion-upgrade costs

12tokens idle
420tokens in use

Idle is what sits in context while the skill is installed. In use is its instructions, loaded when it runs. Counts are approximate, made offline with cl100k_base.

Model dependence Model-led

Script-ledMixedModel-led

Mostly instructions, so how well it works depends on the model that follows them.

This describes the skill's structure, how much of it is scripts. It does not say how well it works.

Touches

shelldetected

Declared tags come from the skill's frontmatter; detected ones from its scripts, its code blocks and the commands it names in inline code. This is detected, not audited.

How it scores

Quality

How well the skill is written, counted from its own files: its frontmatter, its steps, examples, stated output and constraints, its size and whether every file it ships is one it names.How we score it →
Needs attention
  • Frontmatter4/15
  • Structure11/25
  • Examples9/15
  • Output0/15
  • Size15/15
  • Resources0/15

Security

Starts at 100 and loses points for each thing in the skill's files that a reader should look at first.How we score it →
Excellent
  • Runs shell commands−5

    does this on the machine, and the frontmatter does not say so

    SKILL.md, line 13

Repository health

Pre-computed score based on development activity, maintenance, community, maturity, and trend momentum.How we score it →
Good
  • Development activity88
  • Maintenance48
  • Community52
  • Maturity32
  • Momentum40

A five-step upgrade routine for Remotion projects. The agent identifies the package manager and workspaces, then runs npx remotion upgrade when the CLI is present. Without the CLI it finds the latest stable version, moves every remotion and @remotion/* dependency to that exact version, and aligns zod, mediabunny and similar packages with the versions Studio lists.

It finishes by updating the installed Remotion skills and reviewing the manifest and lockfile diff.

What You Get

  • A first-choice path using npx remotion upgrade when @remotion/cli is installed
  • A manual path: read the latest version with npm view, upgrade all remotion and @remotion/* packages to the same exact version, and refresh the lockfile
  • A rule to read @remotion/studio dependencies for the target version and align zod, mediabunny, @huggingface/transformers and @mediabunny packages
  • A command to update all thirteen Remotion skills
  • A final check of the diff and of npx remotion versions

Common Use Cases

  • Moving a project to the latest Remotion release
  • Fixing a version mismatch between Remotion packages
  • Bringing Mediabunny in line with what Studio expects
  • Refreshing installed Remotion agent skills after a release

What Makes It Unique

It treats the upgrade as one version across all Remotion packages and also aligns the auxiliary packages Studio depends on, which are easy to miss. It respects workspace and catalog conventions and keeps unrelated changes, and it ends with a check for mixed versions.

Under The Hood

The skill is instructions only, with no scripts. It tells the agent to read package manifests and lockfiles, run npx remotion upgrade, or use npm view to query the npm registry, edit dependency versions, run the project’s package manager to update the lockfile, and run npx skills update for the Remotion skills. It changes files in the project and installs packages from the network.

Join founders building with open source

Opinionated takes, migration guides, cost-saving tips, and insights from the open source ecosystem.

Subscribe on SubstackJoin 750+ subscribers