Individual skill

remotion

Use when a task involves Remotion compositions, Studio, Player, @remotion packages, programmatic video rendering, captions, media processing, maps, or Remotion and Mediabunny upgrades.

sdk/cloud/catalog/skills/remotion/SKILL.md

Read pinned source

Source commit f83b859a173802a73d978197e92328ab2bf57a6e

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
No
Observed behavior
Network or broad shell
Last checked
Nov 9, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
1,364
Repository last updated
Oct 22, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Remotion

Build and maintain Remotion projects while preserving user changes. If a file
changed unexpectedly, treat it as intentional unless the user confirms otherwise.

## Workflow

1. Inspect `package.json`, the lockfile, existing compositions, the current
   diff, and `npx remotion versions`. Reuse the package manager and project
   shape; keep every `remotion` / `@remotion/*` package on one exact version.
2. Confirm the requested output: composition/source changes, Studio preview,
   rendered media, an embedded Player, or a rendering service.
3. Implement deterministic, frame-driven visuals and keep render inputs
   serializable.
Back to top