studio-mode

Understand the capabilities and restrictions of each Remotion Studio mode. Use when implementing or reviewing Studio actions, permissions, availability, or UI across interactive, detached, deployed, and browser-based Studios.

Quality

80%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/studio-mode/SKILL.md

Studio Modes

Remotion Studio operates in four modes:

Regular interactive Studio: Started with npx remotion studio. A Studio server is attached and the Studio is fully interactive. It can render server-side, use "Open in" actions, execute codemods, install packages, and perform other server-backed actions.
Regular Studio with the preview server detached: previewServerConnected is false. The Studio is effectively read-only, although client-side rendering remains available.
Read-only Studio: A deployed Studio with no server attached. Hide or disable actions that require a server. GitHub is the only supported "Open in" action.
Browser Studio: Deployed at remotion.dev/new and backed by a virtual file system that is hidden from the user. It cannot use "Open in" actions, but it can install dependencies and execute codemods.

When adding or changing a Studio action, determine which modes support it and hide or disable it everywhere else.

Repository: remotion-dev/remotion
Path: .agents/skills/studio-mode/SKILL.md
Commit: 6f4e0d5

Last updated: 5 days ago
First committed: 17 days ago

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.