Player Example
Start the @remotion/player example app and open it in the Codex browser. Use when the user invokes /player-example or $player-example, asks to launch the player testbed, or wants to inspect @remotion/player locally.
Get the complete skill folder, including its scripts and reference files.
When to use this skill
Use Player Example when an AI agent needs a reusable SKILL.md workflow for this job: Start the @remotion/player example app and open it in the Codex browser. Use when the user invokes /player-example or $player-example, asks to launch the player testbed, or wants to inspect @remotion/player locally.
When not to use it
Skip Player Example 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?
mkdir -p ~/.claude/skills/player-example # Save SKILL.md to ~/.claude/skills/player-example/SKILL.md
- Claude Code personal install: place the skill and its bundled files at ~/.claude/skills/player-example/SKILL.md. For a shared project, commit the folder at .claude/skills/player-example/ instead.
- 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.
- 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.
Use the Player Example 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
- 72/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
# Player Example
## Overview
Prepare the Remotion monorepo, launch the player example app, 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 the player example:
```bash cd packages/player-example && bun run dev ```
3. Keep the server process running and read its output for the local URL. The expected default is `http://localhost:3000`, but follow the printed URL if Next.js chooses another port. 4. Open the URL in the Codex in-app browser. 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 player example URL and whether this is a newly started or already running server.
Intended uses
- From the repository root, run:
- Start the player example:
- Keep the server process running and read its output for the local URL. The expected default is http://localhost:3000, but follow the printed URL if Next.js chooses another port.
- Open the URL in the Codex in-app browser. 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 player example 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.