agentleFS
Sign inStart free
mia-cxmia-cx/skills/skills/remotion-upgrade/SKILL.md

remotion-upgrade

Skill4 starsChanged 29 days agoCC0-1.0View on GitHub

Upgrade Remotion, and related packages

22 other projects use a version of this, 19 of them edited; 0 new projects in the last 4 weeks, against 1 the 4 before.

Adopted by

Cooling: 0 new projects took it in the last 4 weeks, 0× the 4 weeks before.thin data

Week of Sep 13: 0 new projectsWeek of Sep 20: 0 new projectsWeek of Sep 27: 1 new projectWeek of Oct 4: 0 new projectsWeek of Oct 11: 0 new projectsWeek of Oct 18: 0 new projectsWeek of Oct 25: 0 new projectsWeek of Nov 1: 0 new projects
Sep 2026Oct 2026Nov 2026
New projects taking a version of this file each week, over the 8 weeks our latest run read: only 1 in all, so this is a hint, not a trend.

Most recently taken up by

Used with

Projects with it also use mediabunny.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • gabros20Skill

    mediabunny

    Multimedia handling with the Mediabunny library

    Also in 4 projects that use this

The file

We split this skill into the rules it gives an agent

4 rules. 1 is common, 0 are distinctive, and 3 are very specific to this project.

  • 1

    Common

    Most of the 19 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 3

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    If @remotion/cli is not available, upgrade manually:

    line 18
  2. Very specific:

    Read the @remotion/studio dependencies for the target Remotion version using npm view @remotion/studio@<version> dependencies --json.

    line 21
  3. Common:

    Run the project's package manager to update its lockfile.

    line 22
  4. Very specific:

    If @remotion/cli is not available, update the installed Remotion skills:

    line 23

“Common” is measured: kept by at least 6 in 10 of the 19 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Upgrade Remotion

  1. Inspect the project manifests and lockfile to identify the package manager and workspaces. Preserve unrelated changes.

  2. Determine whether @remotion/cli is locally available. If it is, run:

    npx remotion upgrade

    This also updates project-local Remotion skills. Skip the manual upgrade below.

  3. If @remotion/cli is not available, upgrade manually:
    • Get the latest stable Remotion version with npm view remotion version.
    • Find every installed remotion and @remotion/* dependency across the project and upgrade them all to that exact version. Preserve their dependency sections and the project's workspace or catalog conventions.
    • Read the @remotion/studio dependencies for the target Remotion version using npm view @remotion/studio@<version> dependencies --json. Align installed auxiliary packages such as zod, mediabunny, and @huggingface/transformers with the versions listed there. Use the mediabunny version for installed @mediabunny/* packages.
    • Run the project's package manager to update its lockfile.

  4. If @remotion/cli is not available, update the installed Remotion skills:

    npx skills update remotion-best-practices remotion-captions remotion-create remotion-docs remotion-interactivity remotion-license remotion-maps remotion-markup remotion-multimedia remotion-render remotion-saas remotion-studio remotion-upgrade --yes
  5. Review the manifest and lockfile diff. Ensure all Remotion packages use one version and installed auxiliary packages use their recommended versions. If the CLI is available, run npx remotion versions as an additional check.

The Remotion releases contain the changelog and may be useful for summarizing relevant changes after the upgrade.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free