Index of every page on this site: llms.txt
All skills
remotion-dev avatar

/remotion-upgrade

@7ba4dcf official
by Remotionremotion-dev/skills5.2k stars
570
Run it yourself

Upgrade Remotion, and related packages

Use this Skill: https://skilld.dev/gh/remotion-dev/skills/remotion-upgrade

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

≈14 tokens for metadata: the name and description. ≈457 when used: this file. ≈71 more on demand in 1 file.

How this Skill uses context

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈57 characters, or 0.7%.

Your model, settings, and other Skills decide how much text your Agent can read.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

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

Source: SKILL.md on GitHub

Skill behaviors

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

Third-party checks

No alerts3d3 checks · Risk SAFE
  • Gen Agent Trust Hub3d

    This skill provides automated workflows for upgrading the Remotion framework and its associated dependencies. It uses standard tools like npm and npx to fetch version metadata and execute official upgrade scripts from the vendor's own packages.

  • Socket3d

    No alerts

  • Snyk3d

    Risk: LOW · No issues

Provenance

Signed by skilld at 7ba4dcf. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub 3 days ago.

Activeupdated 4 days ago

Capability

version
4.0.535

README badge

README badge for remotion-dev/skills/remotion-upgrade