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.

Quality

100%

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

Quality

Content

100%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The skill body is a tight, actionable runbook: a one-line overview followed by a concrete five-step workflow with executable bun commands and sensible fallbacks for port and browser-tool availability. It stays lean without explaining concepts Claude already knows and is well-organized for a simple single-purpose skill.

Dimension	Reasoning	Score
Conciseness	The body is lean with no concept explanations or padding — Overview states the goal and the Workflow gives direct commands, so every token earns its place rather than including unnecessary explanation.	3 / 3
Actionability	Provides fully executable, copy-paste-ready commands ('bun i && bun run build', 'cd packages/player-example && bun run dev') with concrete fallbacks for alternate ports and the browser tool, matching the anchor for fully executable guidance.	3 / 3
Workflow Clarity	A clear five-step sequence includes conditional handling (follow the printed URL on another port; use tool_search if no browser tool), and since this launches a dev server rather than a destructive/batch operation, no validation cap applies.	3 / 3
Progressive Disclosure	Under 50 lines with no external references needed and well-organized Overview/Workflow sections; no bundle files exist, so the simple-skill guidance allows a top score for clear, self-contained organization.	3 / 3
	Total	12 / 12 Passed

Description

100%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is concise, concrete, and clearly scoped: it states two specific actions and pairs them with an explicit 'Use when...' clause covering both slash/keyword invocations and natural-language requests. It is highly distinctive and unlikely to conflict with other skills.

Dimension	Reasoning	Score
Specificity	Names two concrete actions — 'Start the @remotion/player example app and open it in the Codex browser' — which matches the anchor for listing multiple specific concrete actions rather than the partial coverage at level 2.	3 / 3
Completeness	An explicit 'Use when...' clause states when to invoke it, and the opening sentence states what it does; both what and when are present with explicit triggers, using third-person imperative voice.	3 / 3
Trigger Term Quality	Covers natural invocation forms ('/player-example or $player-example') plus phrasings users would say ('launch the player testbed', 'inspect @remotion/player locally'), giving good coverage rather than a single generic term.	3 / 3
Distinctiveness Conflict Risk	Scoped tightly to the @remotion/player example app with unique invocation triggers, making it unlikely to fire for or conflict with unrelated skills.	3 / 3
	Total	12 / 12 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: remotion-dev/remotion
Path: .agents/skills/player-example/SKILL.md
Commit: 1b58387

Reviewed: 2 days ago

Table of Contents

Discovery Implementation Validation

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.