Remotion SaaS

Before you start: read this whole install prompt, tell me in a few lines what this skill does and what installing it involves, and wait for my go-ahead before you do anything else. Prerequisites — Licence and architecture disclosure first: no licence was found anywhere in this repository at the pinned commit (not MIT, not Apache — see the listing's licence note). Installing needs no account, no key and no payment, and nothing is run or deployed. At use time this is guidance for building an app around Remotion: its rendering guide discusses optional backends you would choose and set up yourself — plain Node.js servers, Remotion Lambda on your own AWS account (whose setup creates AWS credentials stored in a .env file; the guide explicitly says never to paste secrets into chat, and deploying the Lambda function and site is part of that chosen setup), Vercel, GitHub Actions, Azure Container Apps or Cloudflare Containers. None of that happens during installation, and no backend is set up unless you choose one at use time. Install "Remotion SaaS" for me. It is the guidance for building an application with Remotion — anything from a simple form hooked up to a render to a complex video editor. Its companions cover choosing a template or framework (Next.js, React Router 7, an Express render server, a Vercel template — clonable or usable as reference), embedding a live preview with the <Player> component from @remotion/player, and choosing how rendering happens (client-side or server-side: plain Node.js APIs, Remotion Lambda, Vercel, GitHub Actions, Azure Container Apps, Cloudflare Containers), while the main file links to the Remotion docs pages for using Remotion with Vue, Angular and Svelte. Its folder holds the main SKILL.md, those three companion guides, its agents/openai.yaml policy file and its icon. Repository: https://github.com/remotion-dev/skills (the skill is the whole skills/remotion-saas/ folder at the pinned commit: SKILL.md plus 5 companion files, 6 files in total) Pinned version: install the code at commit 6c67adcd9cdbe6eb84d76342da89b225f9161cb2 exactly. Do not substitute a newer version. If this commit is unreachable, stop and tell me. 1. Clone https://github.com/remotion-dev/skills into a temporary folder, check out commit 6c67adcd9cdbe6eb84d76342da89b225f9161cb2, and copy the skills/remotion-saas/ folder from that checkout. Then compare every file in the folder with the fingerprints recorded for this listing on 2026-10-22: [FINGERPRINTS] - SKILL.md: SHA-256 3a39b08776b794f5734f6e7b7af9e9cec024d5bfb55eeaa07bd004567b66dd76 - agents/openai.yaml: SHA-256 66be5403b3d10194c99e886372bbc1f4bdb2994fe560278bc7a39b4fbe7753a2 - assets/remotion-icon.svg: SHA-256 5007669bd0555b0f4565b4e7176fa191310ab0039b2ed09d867a9270f5b0ce58 - framework.md: SHA-256 5e35ca3306ac15ad1df189789642cefbc62c59f4929372ffc10a67165d7b04b5 - player.md: SHA-256 cc2f2944f1158d6ff1ddfc421a6a790f99ae86f54bbe0f0b18ef8bc7485e1b05 - rendering.md: SHA-256 b2f30b53e0191ef9e7f2da7360b36c0c5448ab5bdcf55575e1f7e55c5bbd257f If a file does not match, it changed since the listing was prepared: do not install it yet, tell me what you found and let me decide. 2. Read SKILL.md in full, and tell me in plain words: what the skill does when used, what it connects to, whether it reads or sends any personal information or credentials, and anything that seems unusual. Stop on any red flag and tell me before going further. Confirm these points from the files: - The skill folder holds 6 files only: the 1,053-byte SKILL.md, framework.md, player.md, rendering.md, agents/openai.yaml and the icon. There is no script and no other code in it; nothing is deployed or configured during installation. - Nothing is sent anywhere during installation itself; the only download at install time is the skill folder from GitHub at the pinned commit. No AWS or other cloud credential is asked for, read or created during installation. - At use time this is architecture guidance for my own app: templates that can be cloned or used as reference, the @remotion/player preview component, and rendering options I choose myself. The Lambda option in rendering.md is the one credential-bearing path: its setup creates AWS credentials stored in a .env file, and that same guide says never to ask me to paste secrets into chat and to handle authentication, rate limiting, cost controls and output privacy before production. - Do not scaffold or clone any template, do not deploy anything, do not create any cloud resource or credential, and do not use the skill in any way during this install: using it is a separate step that only starts when I ask for it later. 3. When I say "yes, install", install it as a skill: copy the whole remotion-saas folder into the agent's skills directory, in a folder named exactly "remotion-saas", keeping its 6 files in their original relative layout (SKILL.md at its root). 4. Verify with no network calls: frontmatter valid (name: remotion-saas), the 6 files in place with matching fingerprints. Do not run anything from the folder and do not use the skill to verify. 5. Report what was installed, where, and what I still need to do myself (for example: that building and deploying an app, choosing a rendering backend such as Lambda on my own AWS account, and any cloud credentials are separate use-time steps I choose myself — nothing of that is part of this install — and that the companion router remotion-best-practices also covers this skill). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. If anything looks off, stop and ask me.