Remotion Framework Skills - Setup Guide¶
Source: remotion-dev/remotion via skills.sh - 47.5K combined installs across 73 indexed listings; first seen 2026-10-30 (morning sweep)
GitHub: remotion-dev/remotion - 69,018 stars, license field reported as NOASSERTION by the GitHub API while LICENSE.md carries the two-tier Remotion License, branch main, last pushed 2026-10-30; 88 SKILL.md files in three layouts, packages/skills/skills/<name>/SKILL.md for the 13 public skills, .agents/skills/<name>/SKILL.md for 63 internal contributor skills plus symlinks to the public set, and packages/codex-plugin/skills/<name>/SKILL.md for the 12-skill Codex plugin copy
Category: Programmatic video production in React, rendering pipelines and media tooling
Quality Tier: 🟡 Beta - license field NOASSERTION rather than a standard OSI id; a deep, actively maintained library that covers React video markup, rendering, Studio behaviour and the maintainers' own release and PR workflows
Remotion is a React framework for making videos programmatically: compositions are React components, animations are driven by frame numbers, and rendering happens through a bundled Chromium. This repository is the whole thing, the framework packages, Remotion Studio, the player, Lambda rendering, the documentation site and a large agent skill library that ships alongside the code rather than in a separate docs page.
The skill library is the part this catalog entry indexes, and its shape is unusual. Thirteen public skills live in packages/skills/skills/ and are published for agents: remotion-best-practices is a router that loads the right specialist, and the specialists cover creating a project, React markup, captions, maps, Mediabunny media handling, Studio preview, rendering, upgrades and the commercial licence. Sixty-three further skills live in .agents/skills/ and are aimed inward, at people maintaining Remotion itself: adding an effect, an element or a package, fixing a Dependabot PR, naming a pull request, shepherding CI, cutting a release. What the install index measures here is a maintainer's daily habits rather than the usefulness of the video skills, which is worth knowing before you read the table as a ranking.
The licensing deserves a sentence up front because it is not an OSI licence. LICENSE.md grants free use to individuals, non-profits, and for-profit organizations with up to three employees, and requires a company licence above that size, with the exact terms in the file and at remotion.dev/license. Teams evaluating the skills should read that before shipping anything commercial, and the GitHub API reports the licence field as NOASSERTION rather than naming it.
Installation¶
The root README does not document a skills install at all. It offers one framework command, npx create-video@latest, and links the Agent Skills page at remotion.dev/docs/ai/skills. The install path lives in the skills package README, packages/skills/README.md:
npx skills add remotion-dev/skills
gh skill install remotion-dev/skills
Both commands name remotion-dev/skills, a separate repository rather than this monorepo, and packages/skills/README.md is generated by packages/skills/scripts/sync-readme.ts. The local package directory is therefore the source of truth for the thirteen. The skills README also notes that a new project is offered the option to add skills at creation time, which is a different creator command from the root README's own npx create-video@latest:
bun create video
Framework-side commands appear inside the skills themselves rather than in a README, and they are what the agent will actually run once installed: npx create-video@latest --yes --blank --no-tailwind my-video to scaffold, npx remotion render and npx remotion still to export, npx remotion add @remotion/media to add a package, and npx remotion upgrade to move a project and its local skills forward.
Hermes is not a target this repository publishes an adapter for, so the durable route for this profile is a directory copy from a clone:
cp -R packages/skills/skills/remotion-markup \
~/.hermes/profiles/corpusiq/skills/remotion-markup
Copy the whole directory, not the markdown file. remotion-markup carries 33 sibling reference files (compositions.md, timing.md, transitions.md, voiceover.md, 3d.md, lottie.md and more), remotion-captions carries transcribe-captions.md, display-captions.md and import-srt-captions.md, and remotion-best-practices nests the other public skills under itself. A lone SKILL.md leaves the agent pointing at relative links it cannot open.
What It Provides¶
| Skill | Installs | Use For |
|---|---|---|
| web-renderer-test | 2,786 | Adding or updating web renderer tests for an implementation change, which is Remotion's internal test-writing workflow for the browser renderer. |
| writing-docs | 2,766 | Writing and editing Remotion documentation: new pages, MDX edits under packages/docs, and prose changes to existing pages. |
| video-report | 2,707 | Generating a report about a video, the internal production reporting skill for rendered clips. |
| add-sfx | 2,604 | Adding a new sound effect to @remotion/sfx, the packaged sound-effect library. |
| docs-demo | 2,475 | Adding an interactive <Demo> component to a documentation page so a docs example can be run and edited in place. |
| add-expert | 2,451 | Adding a new expert to the Remotion experts page, with the data and portrait assets that page renders. |
| fix-dependabot | 1,010 | Fixing a Dependabot PR: updating every monorepo instance of the bumped dependency, running bun install, and pushing the result. |
| pr-name | 1,006 | Reviewing or correcting a pull request title against Remotion's naming conventions. |
| make-pr | 998 | Opening a pull request for the current feature; no directory with this name exists in the current .agents/skills tree, where the shipped equivalents are pr, pr-ready and merge. |
| add-effect | 839 | Adding an effect to @remotion/effects: implementation, package exports, docs, demos, preview images, skill updates, formatting and builds. |
| visual-mode | 822 | Working on Studio Visual Mode: sequence identity, node paths, symbolicated stacks, override IDs and hot reload behaviour. |
| version | 822 | Reading the Remotion version the repository is currently working on; a tiny reference skill rather than a workflow. |
| add-cli-option | 815 | Adding a CLI or config option: creating an AnyRemotionOption, registering CLI parsing, wiring config setters and updating docs. |
| add-new-package | 809 | Adding a package to the monorepo: scaffolding, monorepo registration, documentation, build scripts and release checklist updates. |
| pr | 807 | Opening a pull request for the current feature. |
| update-version | 779 | Bumping AvailableFrom in a PR to the next patch version, so documentation shows the right availability marker. |
| issue | 731 | Creating, editing or commenting on Remotion GitHub issues through the gh CLI. |
| pr-ready | 730 | Getting a PR ready: clearing CI failures and merge conflicts, handling local branch changes. |
| issue-management | 719 | Managing GitHub Issues 2.0 relationships: parent issues, sub-issues, blocked-by and blocking links. |
| flake | 678 | Tracking Remotion CI flakes in issue #8375, incrementing repeated signatures, discovering failed checks and rerunning flaky jobs. |
| merge | 662 | Shepherding a PR to merge: waiting for mergeability, resolving conflicts, separating flakes from real failures and merging. |
| add-webcodecs-bug | 661 | Adding a browser WebCodecs bug to the Mediabunny docs page from an issue URL, including title, filing date, reporter and resolution. |
| nullable-new-params | 656 | Forbidding new optional parameters and props in favour of required nullable values, converting internal APIs and updating call sites. |
| release | 655 | Cutting a new Remotion version; the maintainer release workflow. |
| interactivity-best-practices | 636 | Writing Remotion animations that stay intuitive for agents and editable in Studio Visual Mode. |
| upload-r2 | 604 | Uploading large repository assets to the Cloudflare R2 bucket behind remotion.media and replacing local files with hosted URLs. |
| formatting | 585 | Running Remotion formatting and style checks until they pass. |
| upgrade-mediabunny | 581 | Upgrading Mediabunny and the related @mediabunny packages across the monorepo. |
| add-bug | 581 | Adding a bug entry under packages/bugs/api for the affected Remotion versions so it surfaces through the bugs API. |
| update-stars | 580 | Refreshing the GitHub star count on the Remotion homepage and pushing the change to main. |
| checkout | 580 | Checking out a requested branch or ref, renaming the Codex task to the PR title, installing dependencies and building. |
| upgrade-caniuse | 579 | Upgrading the caniuse-lite override in the repository. |
| update-chrome-binaries-test-region | 578 | Publishing Lambda Chrome binaries to the eu-central-1 test region and updating the hosted layer and Chrome version references. |
| vercel | 511 | Setting up a Codex monitor for Vercel deployments and preview URLs, waiting until a preview is ready. |
| homepage-video-assets | 511 | Rendering or replacing the homepage creator strip videos, including transparent Chrome WebM and Safari MP4 assets on remotion.media. |
| player-example | 501 | Starting the @remotion/player example app and opening it for local inspection of the player. |
The remaining 37 indexed listings range from 98 to 499 installs.
Why This Matters for Hermes Agents¶
Video is the one media type an agent usually cannot produce end to end, and Remotion changes that shape: the output is code, the preview is a browser, and the render is a command. The public skills encode the decisions that make such a project work on the first attempt, from scaffolding rules (empty folder versus subfolder, create-video refusing non-empty directories) to the instruction that Studio should be opened before any composition is written so the user can steer the result while it is being built.
The router design is the other reason this suite installs well. remotion-best-practices is deliberately thin: it decides whether the request is creation, markup, maps, multimedia, interactivity or preview, loads the matching skill, and it tells the agent not to render by default when the user asked to make a video, because an interactive preview is what they actually want. A Hermes profile can hold that single skill and still reach the rest if the directories are present, instead of loading a dozen descriptions into routing context on every turn.
For builders the useful part is the reference depth behind the names. remotion-markup is not an essay, it is a folder of around forty topic files, one per decision: compositions, timing, transitions, audio, fonts, lottie, 3d, motion blur, measuring text, multi-scene structure. The agent reads the file that matches the question instead of carrying the whole framework in context, which is exactly how a long video project stays inside a token budget.
The internal half is unusually honest documentation of how a video framework is maintained, and it transfers. The workflow behind adding an effect to @remotion/effects touches implementation, exports, docs, demos, preview images and the skill text itself, and that checklist is a template any team shipping an animation package can borrow.
Finally, the suite is explicit about what needs a live service, so a Hermes cron can plan around it: vercel needs a deployment to watch, upload-r2 and offload-r2 need a Cloudflare bucket behind remotion.media, update-chrome-binaries-test-region needs Lambda publishing rights in eu-central-1, and the issue, flake and PR skills need an authenticated gh session.
Usage¶
| You say | What happens |
|---|---|
| "Make a promo video for a record store" | remotion-best-practices routes to remotion-create, which scaffolds with npx create-video@latest --yes --blank --no-tailwind, installs dependencies, opens Studio for preview, and then builds the composition from remotion-markup guidance rather than rendering straight away. |
| "Animate a route from Los Angeles to New York with the camera following it" | remotion-maps takes the request: static map setup, animated route and markers, Mapbox or MapLibre or MapTiler configuration, GeoJSON input, and an optional CesiumJS flyover if the shot needs 3D. |
| "Add captions from this SRT and animate them word by word" | remotion-captions loads the Caption type contract, imports the SRT through import-srt-captions.md, then uses display-captions.md for the rendering pattern and hands follow-up work back to the router skill. |
| "Render frames 0, 30 and 90 as PNGs to check the layout" | remotion-render uses npx remotion render [composition-id] out/frames --frames=0,30,90 --image-format=png, or npx remotion still [composition-id] --scale=0.25 --frame=30 when a single still is enough. |
| "Upgrade this project to the latest Remotion and keep the skills in step" | remotion-upgrade inspects manifests and the lockfile, runs npx remotion upgrade, aligns @mediabunny and auxiliary packages with the target @remotion/studio dependencies, then updates the installed skills in the same pass. |
| "I am adding a new sound effect to the sound-effect library" | add-sfx walks the addition of a new sound effect to @remotion/sfx, and the neighbouring internal skills cover package registration, docs and demos when the change grows beyond one folder. |
| "Which skills does this repo actually ship, and where do they live?" | skill-locations states the placement rule: public redistributable skills under packages/skills/skills, internal agent-only skills under .agents/skills, symlinks between them, and bun run syncskills plus bun run checkskills to keep them in step. |
Verification¶
All three raw paths below returned 200 on branch main when this guide was written on 2026-10-30:
curl -sL -o /dev/null -w "%{http_code} create\n" \
https://raw.githubusercontent.com/remotion-dev/remotion/main/packages/skills/skills/remotion-create/SKILL.md
curl -sL -o /dev/null -w "%{http_code} render\n" \
https://raw.githubusercontent.com/remotion-dev/remotion/main/packages/skills/skills/remotion-render/SKILL.md
curl -sL -o /dev/null -w "%{http_code} router\n" \
https://raw.githubusercontent.com/remotion-dev/remotion/main/packages/skills/skills/remotion-best-practices/SKILL.md
Expect 200 three times. Read at least the router before installing: its whole value is the routing table, and a copy whose relative links were broken in transit will still pass head and fail the agent. After a directory lands in the profile, confirm the frontmatter and the shape of the copy:
head -6 ~/.hermes/profiles/corpusiq/skills/remotion-create/SKILL.md
ls ~/.hermes/profiles/corpusiq/skills/remotion-markup | wc -l
A good copy shows name:, description: and version: in the frontmatter, and the second command should report a directory of reference files rather than a count of one. If it returns one, only the markdown was copied.
Security¶
skills.sh verdicts for sampled skills (verified 2026-10-30) - re-check the security pages on skills.sh before production use:
| Skill | Gen Agent Trust Hub | Socket | Snyk |
|---|---|---|---|
| web-renderer-test | Pass | Pass | Pass |
| writing-docs | Pass | Pass | Pass |
| video-report | Pass | Pass | Pass |
| add-sfx | Pass | Pass | Pass |
| remotion-docs | Pass | Pass | Pass |
No Fail or Warn verdict appears in the sampled five, which is the expected result for a first-party repository whose skills are instructions and reference markdown rather than executable tooling. Do not read that as a blanket clearance: the sample covers the top of the install table, and the skills that matter most for a builder, remotion-markup, remotion-render and remotion-captions, are not in it.
The real review surface is what the installed skills instruct an agent to run. Rendering downloads a Chromium build and executes the project's code in it, npx create-video@latest pulls a scaffold from npm, and the internal skills run gh, bun and Vercel and Cloudflare tooling against real accounts. Installation does not grant any of that, but the instructions will ask for it, so keep credentials in the environment rather than in a prompt and scope any token that the agent can reach.
One licence point belongs here as well: LICENSE.md is a two-tier licence, not MIT, and the free tier stops at for-profit organizations with more than three employees. The GitHub API reports NOASSERTION because the file is not a standard OSI text.
Integration with CorpusIQ¶
CorpusIQ is the connector layer that lets AI assistants read the systems a business already runs on - accounting, payments, CRM, email, files and analytics - and answer with the source named. It is read-only by design: it retrieves data and never writes to, or acts in, a connected system, which is what makes it safe to point at live accounts.
This page is part of the CorpusIQ directory, the reference we maintain for the MCP server and agent-skill ecosystem. Run alongside CorpusIQ, a third-party server like this one can be combined with a company's own business data in a single answer.
Limitations¶
- Snapshot data, verified 2026-10-30: 47,489 combined installs across 73 indexed listings; 69,018 GitHub stars; license field NOASSERTION in the GitHub API with a two-tier Remotion License in
LICENSE.md; last pushed 2026-10-30. Counts drift over time. - The index and the tree do not line up. Four indexed listings have no directory in the current checkout:
make-pr,update-remotion-rust-ffmpeg,install-canvas-capture-browserandpublish-element. Going the other way, the tree carries skills the index does not rank, among themremotion-license,remotion-maps,remotion-multimedia,remotion-studio,remotion-upgrade,product-recordingandupdate-ffmpeg. - Install counts here measure maintainer habits, not usefulness. The top of the table is internal contributor work such as
web-renderer-test,writing-docsandvideo-report, while the public video skills sit in the tail,remotion-create,remotion-renderandremotion-captionsat 107, 110 and 104 installs. Judge a skill by itsSKILL.mdand its reference folder. - The skills are instructions, not a runtime. Nothing renders without Node, a Remotion project and the CLI downloading its own browser, and several skills are inert without a live service:
vercelneeds a deployment to watch,upload-r2andoffload-r2need a Cloudflare R2 bucket,update-chrome-binaries-test-regionneeds Lambda publishing in eu-central-1, and the issue, flake and PR skills need an authenticatedgh. - The published install commands name
remotion-dev/skills, a separate listing, not this repository. The copies underpackages/skills/skills/are the source, andpackages/skills/README.mdis generated, so treat the package directory as authoritative and the readme as a view of it. - A large share of the indexed names are Remotion's own release and repository housekeeping,
release,update-version,update-stars,upgrade-caniuseand their neighbours, and they will do nothing useful in a project that is not the Remotion monorepo.
Related¶
- remotion-best-practices - Video Production Setup
- Motion Design Skills - After Effects and Remotion Setup
- Hyperframes Setup
Skills Catalog | Skills Marketplace
Pro Tips¶
- Install
remotion-best-practicesandremotion-markupfirst. The router costs one description in context and reaches the rest, and the markup folder answers most of the questions an agent actually gets asked about a video. - Copy directories, not files. The value of
remotion-markupis its 33 reference files, and a markdown-only copy turns a precise lookup into a confident guess. - Keep the agent in preview mode while it works. Every public skill repeats the instruction to open Studio before writing a composition and not to render unless the user asked for a file, which is also the cheapest way to review a video change.
- Check the licence before the first commercial render. The free tier covers individuals and companies up to three employees, and a team that crosses that line needs the company licence, not a code review.
- Pin the version. The public skills carry
version: 4.0.539, andremotion-upgradeexists precisely because a project and its installed skills drift apart quickly.
← Skills Catalog | Skills Marketplace → Powered by CorpusIQ