Remotion's Claude skill, tested — and when you want the alternative

Tested and written by Fred at SkillsTested · Published 2026-07-26 · Updated 2026-10-14

Remotion's official agent-skills repo now contains 12 top-level skills. Our July 2026 test installed the then-11-skill pack and rendered a complete five-second MP4 with motion and sound. On 2026-10-14 we checked the newer source and ran a focused, two-second frame-animation test. The two runs have different scopes.

What's in the official pack

At upstream commit 7ba4dcf, the repo has 12 top-level skills: remotion-create, remotion-render, remotion-captions, remotion-markup, remotion-saas, remotion-docs, remotion-upgrade, remotion-interactivity, remotion-best-practices, remotion-maps, and remotion-multimedia, plus remotion-studio. The official Skill guide explains the current install route. This count is a source check, not a claim that we ran all 12 today.

The July 2026 full-pack install

npx skills add remotion-dev/skills -a claude-code -s '*' -y

In that dated test, all 11 then-available skills landed in 4.12 seconds. Instruction-only at install time; Remotion itself (npm install remotion @remotion/cli) enters the picture when you scaffold a project.

What the July render taught us

The July scaffold and full render both succeeded. The surprise was time distribution: the 150-frame render took 8.094 seconds, while the first browser download took 375.53 seconds in this fresh project. Preflight Chrome Headless Shell in CI instead of discovering that dependency at export time.

2026-10-14 focused retest: a CSS fade that exports correctly

We copied only the remotion-best-practices hub from pinned upstream commit 7ba4dcf8ebe1626b00baa41e1f2478113719b60b into a clean temporary Codex project. The installed copy matched the source hash. With Remotion and its CLI fixed at 4.0.535, we asked the agent to repair a title card whose fade used CSS @keyframes and to export an MP4. It read the installed markup rule, changed the animation to useCurrentFrame() and inline interpolate(), and preserved the text and composition settings.

The agent's first render was blocked by macOS browser-process permissions inside its CLI sandbox. We reran the same project with local Chrome outside that inner sandbox. The resulting H.264 MP4 has 60 frames at 30 fps, is 640×360, lasts two seconds, and has no audio. Checked frames show the title going from transparent to visible. This verifies one animation-repair task and its exported output; it does not retest the whole pack.

Read the pinned-source and output checks. The practical fix is to compute opacity from the frame and frame rate, with interpolation clamped at both ends; a browser's wall-clock CSS animation is not a reliable export timeline.

Still unverified on this commit: installing all 12 with the Skills CLI, Claude Code activation, Studio interactions, audio, captions, external media, repeated runs, and a no-Skill comparison. We did not find a standalone license file in the pinned repo, so this test does not establish redistribution rights for its Skill text.

Official pack or video-shotcraft?

Our read after testing both: they stack. The official pack keeps the agent's Remotion code correct; video-shotcraft supplies taste and a finish line. If the goal is "a promo video this week," start from the template and let the official skills handle the API details underneath.

FAQ

Do I need the skills if I already know Remotion?

The pack's value is keeping the agent current — version-correct APIs and upgrade guidance — which matters precisely when you stop writing every line yourself.

Does the pack work with Codex or Cursor?

Yes; the installer's -a flag targets other agents, and the skills are plain markdown per the agentskills spec.