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

84%

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

86%Weight 40%Scale 1-5

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

The body is lean and well-structured with executable commands and a clearly sequenced workflow including a server-output checkpoint. Main gaps are the abstract browser-navigation step and the absence of error-recovery feedback loops for the build/serve steps.

Suggestions

Make the browser-navigation step concrete by naming the specific in-app browser tool and the exact call used to navigate to the URL, so the final action is copy-paste ready rather than relying on a 'tool_search' fallback.

Add an error-recovery feedback loop for the build step (e.g., 'If `bun run build` fails, re-run `bun i` and retry') to give the workflow an explicit validation checkpoint.

Add an explicit server-ready checkpoint (e.g., confirm a 'Ready' line appears in the dev-server output before opening the browser) to strengthen the feedback loop around step 3.

Dimension	Reasoning	Score
Conciseness	The body is lean and operational — a one-line Overview and five terse steps with two short bash blocks — assuming Claude knows bun/Next.js; every line earns its place with no concept padding.	5 / 5
Actionability	Provides copy-paste ready commands ('bun i && bun run build', 'cd packages/player-example && bun run dev'), but the browser step is described abstractly via a 'tool_search' fallback rather than a concrete executable call, a minor gap below 5.	4 / 5
Workflow Clarity	A clear five-step sequence with a checkpoint in step 3 ('read its output for the local URL'), but there are no explicit error-recovery feedback loops for the build/serve steps; this is not a destructive or batch operation so the cap-at-3 rule does not apply.	4 / 5
Progressive Disclosure	Under 50 lines, single-purpose, with no need for external references and no inlined content that belongs in separate files; the well-organized Overview and Workflow sections satisfy the simple-skill exception for a 5.	5 / 5
	Total	18 / 20 Passed

Description

82%Weight 40%Scale 1-5

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 clearly and explicitly answers both what and when with concrete trigger phrases in proper third-person voice, occupying a distinct niche. It is held back only by limited action specificity (two actions) and a few missing natural synonyms.

Dimension	Reasoning	Score
Specificity	Names the domain and two concrete actions — 'Start the @remotion/player example app and open it in the Codex browser' — matching the '1-2 concrete actions' anchor; not 'several' so it does not reach 4.	3 / 5
Completeness	Explicitly answers what ('Start... and open it in the Codex browser') and when ('Use when the user invokes /player-example or $player-example, asks to launch the player testbed, or wants to inspect @remotion/player locally') with concrete trigger phrases, matching the 5 anchor.	5 / 5
Trigger Term Quality	Good natural-term coverage via '/player-example or $player-example', 'launch the player testbed', and 'inspect @remotion/player locally'; a few plain synonyms (run/open the player example) are missing, keeping it below 5.	4 / 5
Distinctiveness Conflict Risk	Occupies a clear narrow niche (Remotion player example) with unique slash/dollar-command triggers and package-specific phrasing, giving minimal conflict risk with other skills.	5 / 5
	Total	17 / 20 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: 19ec0ee

Reviewed: about 14 hours 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.