CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

remotion-studio

Preview a Remotion video

Quality

82%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

The canonical home for this skill is remotion-studio in remotion-dev/skills

SKILL.md
Quality
Evals
Security

Quality

Content

100%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 exemplary for a simple, single-purpose skill: fully executable commands, explicit verification steps for both Studio load and composition preview, clear branching across client types, and a tight flags table with no wasted tokens. No changes needed.

DimensionReasoningScore

Conciseness

The ~30-line body is lean with zero padding: no concepts Claude already knows, and every operational detail (URL printing behavior, already-running case, in-app browser caveat) earns its place. It matches the 'lean and efficient; assumes Claude's competence' anchor.

5 / 5

Actionability

Fully executable, copy-paste-ready commands ("npx remotion studio", "npx remotion studio --no-open") with concrete flag values (--log levels, --port, --force-new) and explicit handling of the common cases (Cursor, other clients, Studio already running). Matches the top anchor.

5 / 5

Workflow Clarity

A simple single-purpose skill with an unambiguous sequence — start Studio as soon as the project can run, before building the composition, keep it open while working — plus explicit validation checkpoints ("verify that Studio loads", "verify that its video preview loads") and an error-avoidance rule ("Do not use --no-open if you cannot open the URL"). Meets the simple-skill exception for a top score.

5 / 5

Progressive Disclosure

Under 50 lines, no external references needed (the only bundle file is an icon asset, consistent with the body's lack of file references), and content is well-organized into a main workflow plus a 'Useful flags' section. Per the rubric's simple-skill guidance, this earns a 5 with just well-organized sections.

5 / 5

Total

20

/

20

Passed

Description

57%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 is concise and unambiguous within the Remotion niche, but it is too sparse: it omits any 'when to use' trigger guidance and under-sells the skill's actual behavior (launching and monitoring Remotion Studio while developing a video). The missing trigger clause is the main weakness.

Suggestions

Add an explicit trigger clause, e.g. "Use when creating or editing a Remotion video, or when the user wants to preview or see live changes to a video composition."

Expand the 'what' to reflect the skill's real actions, e.g. "Launch Remotion Studio to live-preview a video project and keep the preview open while editing."

Include natural synonyms such as "studio", "video preview", and "render" so the description matches phrasings a user would naturally say.

DimensionReasoningScore

Specificity

"Preview a Remotion video" names the domain (Remotion) and one concrete action (preview), matching the 1-2 concrete actions anchor. It is not 4-5 because only a single action is listed with no coverage of starting Studio, keeping it open, or flag control; it is not 2 because the stated action is concrete rather than generic.

3 / 5

Completeness

The 'what' is stated clearly ("Preview a Remotion video") but the 'when' is entirely absent — there is no 'Use when...' clause or equivalent trigger guidance, which caps completeness at 3 per the judging guidelines. Not 2 because the 'what' is concrete, not vague.

3 / 5

Trigger Term Quality

"Remotion", "preview", and "video" are relevant natural terms, but common variations are missing — notably "studio" (the actual tool being launched), "render", and "video preview". This matches the 'some relevant keywords but missing common variations or synonyms' anchor.

3 / 5

Distinctiveness Conflict Risk

"Remotion" is a highly distinctive niche term with a clear dedicated trigger; minimal conflict risk with any other skill. Not 4 because the niche is unambiguous rather than carrying minor overlap with closely related skills.

5 / 5

Total

14

/

20

Passed

Validation

93%

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

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository

remotion-dev/remotion

Path

packages/codex-plugin/skills/remotion-studio/SKILL.md

Reviewed

Table of Contents

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.