LabscoMCP early access ↗
REPO PACKAGECOMMUNITY

remotion-dev remotion

remotion-dev · publisher52,255 GitHub starsListed as freegithub.com/remotion-dev/remotion

LABSCO SUMMARY

Summary

Nearly all of the skills in Remotion's own monorepo are the maintainer team's tooling for building the video library itself rather than skills for making a video.

remotion-dev/remotion is the Remotion codebase — the React video-rendering library, its CLI, the Lambda and Vercel renderers, the @remotion/effects and @remotion/sfx packages, and Remotion Studio. The skills here are the contributor workflow around that codebase: release cuts a new Remotion version, merge and pr-ready shepherd a pull request through CI, checkout and formatting prepare a workspace, fix-dependabot and flake handle dependency PRs and CI flakes, add-new-package / add-effect / add-sfx / add-cli-option extend the monorepo, and issue, issue-management, upgrade-caniuse and upgrade-mediabunny round out a dozen more in the same vein — all written for someone with commit access to this repository.

Exactly one speaks to someone building a video rather than building Remotion: interactivity-best-practices, on keeping animations intuitive for an agent to write and editable in Remotion Studio's Visual Mode. A reader hoping for skills on rendering, captions, transitions or Lambda deployment won't find them among these skills — that material lives on remotion.dev instead.

READ MORE

The library these skills maintain is not permissively licensed.

Remotion's own README says outright that it "has a special license and requires obtaining a company license in some cases," pointing to its LICENSE.md rather than an OSI license, and our bundle records no open-source license field for the repository either. That's a fact about Remotion the product rather than about the skills, but it belongs here because most readers land on this page while deciding whether to build on Remotion at all.

Many need more than a checkout to run.

Some are classed as needing an account key — Lambda credentials for update-chrome-binaries-test-region, a Cloudflare R2 token for upload-r2, GitHub access scoped to remotion-dev/remotion for the release and PR skills — and others need a local tool such as bun or the gh CLI already on the machine. None of that access is something an outside contributor, let alone someone just using the Remotion library, is likely to have.