Skip to main content
Agent skill

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.

Get started

Get the complete skill folder, including its scripts and reference files.

When to use this skill

Use Studio when an AI agent needs a reusable SKILL.md workflow for this job: 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.

When not to use it

Skip Studio when the task is outside the coding category, or when a more specific skill in this directory already covers the same workflow with clearer triggers.

How to install

Where will you use it?

Install scope
Claude Code folder setup
mkdir -p ~/.claude/skills/studio
# Save SKILL.md to ~/.claude/skills/studio/SKILL.md
  1. Claude Code personal install: place the skill and its bundled files at ~/.claude/skills/studio/SKILL.md. For a shared project, commit the folder at .claude/skills/studio/ instead.
  2. Current Claude Code detects SKILL.md changes in watched directories during the session. If you just created a top-level skills directory, run /reload-skills. Check that the skill is listed before testing its trigger.
  3. For Claude chat or Cowork in the Desktop app, manage uploaded skills in Customize > Skills; copying files into a local Claude Code folder is not a Desktop install. Other agents may use different install locations.

Full install guide for Claude, Cursor, and Codex →

Try a starter prompt

After installing the skill, paste this starter prompt into your agent to verify it triggers on a small task.

Starter prompt
Use the Studio skill for this task: From the repository root, run:. Confirm any required inputs or files before making changes.

What supports this recommendation?

83/100 provisional content score. This measures documentation, practical detail and source signals. It is not a measured task success rate or a security certification.

Documentation
92/100
Practical detail
92/100
Source evidence
63/100
Source signals
70/100
Model compatibility evidence
  • claudeuntested

    No model-specific signal or recorded compatibility test was found.

  • chatgptuntested

    No model-specific signal or recorded compatibility test was found.

  • geminiuntested

    No model-specific signal or recorded compatibility test was found.

  • copilotuntested

    No model-specific signal or recorded compatibility test was found.

  • llamauntested

    No model-specific signal or recorded compatibility test was found.

  • perplexityuntested

    No model-specific signal or recorded compatibility test was found.

  • mistraluntested

    No model-specific signal or recorded compatibility test was found.

  • grokuntested

    No model-specific signal or recorded compatibility test was found.

Inferred compatibility is based on content signals. Check the app, its available tools and setup requirements before running a skill.

What this skill does

# 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:

```bash bun i && bun run build ```

2. Start Studio from the example package:

```bash 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.

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

Intended uses

  • From the repository root, run:
  • Start Studio from the example package:
  • 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 toolsearch 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.

Implementation notes

  • Review the source instructions and adapt inputs before running the workflow.

Try it, then tell us how it went

A copied prompt does not tell us whether the task worked. Report your result after checking the output. We collect your tool and outcome, never your files or prompt.