Imported from fradser/dotclaude (
office/skills/remotion/SKILL.md). Install upstream withnpx skills add fradser/dotclaude --skill remotion. Copyright stays with the author.
Remotion Skills
This skill is a router for all Remotion video-creation operations. It mirrors the upstream remotion-dev/skills repository. Based on user intent, read the corresponding sub-skill SKILL.md before executing.
Sub-skills are authoritative. The files under each sub-skill directory are upstream content kept verbatim — do not edit them; re-sync from upstream instead. The table below is the index, the sub-skill SKILL.md is the instruction.
Sub-skill Index
| Sub-skill | Entry | Use When |
|---|---|---|
| New Project | remotion-create/remotion-create.md |
Scaffold a new Remotion project (npx create-video), design a video, start the Studio preview |
| React Markup | remotion-markup/remotion-markup.md |
Writing Remotion React markup — the core: animations, media, sequences, timing, fonts, effects, maps, Lottie, DOM measurement, transitions, trimming |
| Rendering | remotion-render/remotion-render.md |
Rendering videos and stills (npx remotion render/still), transparent videos |
| Captions | remotion-captions/remotion-captions.md |
Transcribing, importing SRT, and displaying captions/subtitles |
| Interactivity | remotion-interactivity/remotion-interactivity.md |
Making animations editable in Remotion Studio Visual Mode |
| SaaS / Apps | remotion-saas/remotion-saas.md |
Building video apps — <Player>, rendering on Lambda/Vercel/Cloudflare/Node, client-side rendering, choosing a framework |
| Mediabunny | mediabunny/mediabunny.md |
Multimedia handling in the browser — get audio/video duration, get video dimensions |
How to route
- Identify the user's intent against the Use When column.
- If the task spans several domains (e.g. "build a Remotion SaaS that renders captions"), load each relevant sub-skill in the order the task needs them.
- Read the sub-skill's entry file (
<name>/<name>.md, denested fromSKILL.mdso sub-skills are not auto-discovered), then follow anyreferences/-style.mdfiles it points to (each sub-skill folder carries its own detail files). - Sub-skills reference each other via relative paths like
../remotion-markup/remotion-markup.md— these resolve within thisremotion/directory.
Notes on cross-references
Some upstream sub-skill files contain links like [Remotion Best Practices](../remotion-best-practices/remotion-best-practices.md). remotion-best-practices/ is a local shim (not an upstream sub-skill) that forwards to this top-level router — treat those links as "go back to the Remotion router" (i.e. this file). All other sibling cross-references (../remotion-markup/remotion-markup.md, ../remotion-captions/remotion-captions.md, etc.) resolve correctly.