mcpbeat

Remotion Best Practices

remotion-dev/remotion-best-practices

Router for all Remotion skills

282k tokens
context cost
the whole folder, loaded on every use
134
files
ships runnable scripts
0
copies elsewhere
how many repositories repackaged it
4202
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository
npx skills add https://github.com/remotion-dev/skills --skill remotion-best-practices

What comes with it

130 915 bytes besides the instruction
agents/openai.yaml
assets/remotion-icon.png
remotion-captions/REFERENCE.md
remotion-captions/agents/openai.yaml
remotion-captions/assets/remotion-icon.png
remotion-captions/display-captions.md
remotion-captions/import-srt-captions.md
remotion-captions/transcribe-captions.md
remotion-create/REFERENCE.md
remotion-create/agents/openai.yaml
remotion-create/assets/remotion-icon.png
remotion-create/tailwind.md
remotion-create/video-layout.md
remotion-docs/REFERENCE.md
remotion-docs/agents/openai.yaml
remotion-docs/assets/remotion-icon.png
remotion-interactivity/REFERENCE.md
remotion-interactivity/agents/openai.yaml
remotion-interactivity/assets/remotion-icon.png
remotion-maps/REFERENCE.md
remotion-maps/agents/openai.yaml
remotion-maps/assets/remotion-icon.png
remotion-maps/techniques/cesium/TECHNIQUE.md
remotion-maps/techniques/cesium/assets/CesiumFlythrough.tsx
remotion-maps/techniques/cesium/assets/cesium-path.json
remotion-maps/techniques/cesium/assets/city-path.json
remotion-maps/techniques/cesium/assets/example-Root.tsx
remotion-maps/techniques/cesium/assets/flight-path.ts
remotion-maps/techniques/cesium/assets/sample-river.geojson
remotion-maps/techniques/cesium/references/3d-data-sources.md
remotion-maps/techniques/cesium/references/3d-flyover-architecture.md
remotion-maps/techniques/cesium/references/3d-troubleshooting.md
remotion-maps/techniques/cesium/scripts/prep-cesium-path.mjs
remotion-maps/techniques/mapbox/TECHNIQUE.md
remotion-maps/techniques/mapbox/references/render-stability.md
remotion-maps/techniques/maplibre/TECHNIQUE.md
remotion-maps/techniques/maplibre/references/render-stability.md
remotion-maps/techniques/maptiler/TECHNIQUE.md
remotion-maps/techniques/maptiler/assets/CountryLabel.tsx
remotion-maps/techniques/maptiler/assets/MapTilerVectorElement.ts

The instruction itself

11 sections, as written by the author

Creating a video

If the user asks to make, create, or build a new video or composition, load Create a new Remotion video, whether or not a Remotion project already exists.

New project setup

If no Remotion project currently exists, load Create a new Remotion project

React Markup Best Practices

If you are writing Remotion React Markup, load Remotion Markup Best Practices

Maps

For static maps, animated routes and markers, geographic explainers, Mapbox, MapLibre, MapTiler, GeoJSON, or 3D geographic flyovers, load Remotion Maps.

Multimedia

For achieving multimedia tasks in the browser, such as trimming, cropping videos, or getting metadata from them, load Remotion Multimedia

Improving Interactivity

By structuring the Remotion markup well, we can allow users to interactively change things in the Studio and write back to code. If relevant: Interactivity Best Practices

Rendering

For advanced rendering beyond simple npx remotion render, see: Rendering Best Practices

Captions

When working with Captions, load Remotion Captions.

Creating a SaaS, automation or application

Use the Remotion SaaS skill for knowledge about Remotion-powered SaaS apps, such as <Player>, rendering on Lambda, Vercel, Cloudflare, via Express.js, client-side rendering, or for finding the right SaaS template.

Looking up Remotion APIs and documentation

To find and read current Remotion documentation, load Remotion Docs.

Upgrading

To upgrade Remotion, related packages, compatible Mediabunny packages, and installed Remotion Agent Skills, load Remotion Upgrade.

How to use it

Copy the folder

Take remotion-dev/remotion-best-practices from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.

Install what it needs

The instructions reference npx. Without those the skill loads but fails at the first command.