mcpbeat

Studio

remotion-dev/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.

420 tokens
context cost
the whole folder, loaded on every use
2
files
instructions only
0
copies elsewhere
how many repositories repackaged it
55471
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository 
npx skills add https://github.com/remotion-dev/remotion --skill studio

What comes with it

179 bytes besides the instruction
agents/openai.yaml

The instruction itself

3 sections, as written by the author

Remotion Studio

Overview

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

Workflow

  • From the repository root, run:
bun i && bun run build
  • 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.

  • 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.
  • 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.
  • 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.
  • 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.
  • Tell the user the Studio URL and whether this is a newly started or already running server.

How to use it

Copy the folder

Take remotion-dev/studio from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.