remotion-dev/remotion

studio

Start Remotion Studio from packages/example and open it in the Codex browser. Use when the user invokes /studio or $studio, asks to launch the example Studio, or wants the Remotion Studio dev UI available locally.

First seen Jul 9, 2026

Installation

$ npx skills add remotion-dev/remotion --skill studio

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from remotion-dev/remotion · top by installs.

npx skills add remotion-dev/remotion

Browse all from remotion-dev/remotion

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 58.6K
License LICENSE.md
Default branch main
Open issues 155
Status Active

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,503 B
  • docs SUMMARY.md 1,473 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 280 installs

SKILL.md

Remotion Studio

Overview

Prepare the Remotion monorepo, launch the example Studio, and open the served URL in the Codex in-app browser.

Workflow

  1. From the repository root, run:
bun i && bun run build
  1. Start Studio from the example package:
cd packages/example && bunx remotion studio --no-open

Use bunx, not npx. Always pass --no-open; Codex should open the printed URL explicitly instead of letting the CLI open a browser.

  1. Do not check localhost:3000 before starting Studio. Another worktree may already be using that port, and probing it first can open the wrong Studio.
  2. Keep the server process running and read its output for the local URL. The expected default is http://localhost:3000, but the CLI output is the source of truth.
  3. If the CLI says Studio is already running, use the exact URL printed by that CLI invocation. Only verify with curl after the CLI has identified the URL for this worktree.
  4. Open the exact CLI URL in the Codex in-app browser yourself. If no browser tool is available yet, use tool_search for the in-app browser control tool, then navigate to the local URL.
  5. Tell the user the Studio URL and whether this is a newly started or already running server.