CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

remotion-studio

Preview a Remotion video

Quality

80%

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

Fix and improve this skill with Tessl

tessl review fix ./packages/skills/skills/remotion-studio/SKILL.md

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 an exemplary lean skill: concrete runnable commands, explicit verification steps, clear client-specific branching, and a tight flags table with zero padding. It fully respects the context window while leaving no ambiguity about what to do.

DimensionReasoningScore

Conciseness

Every line is operational and non-obvious: when to start Studio relative to building the composition, that a rerun prints the URL and exits, when to use --no-open, and keeping it open so the user can steer. There is no padding and no explanation of concepts Claude already knows, fitting the "lean and efficient; every token earns its place" anchor.

5 / 5

Actionability

The guidance is fully executable with copy-paste-ready commands ("npx remotion studio", "npx remotion studio --no-open") and a flags table with specific values (--log levels, --port, --force-new), covering the common client scenarios. It is not anchor 4 because there are no gaps — the already-running case and verification expectations are both addressed.

5 / 5

Workflow Clarity

This is a simple single-purpose skill whose action is unambiguous, and it includes explicit validation steps ("verify that Studio loads", "verify that its video preview loads") plus a clear guard ("Do not use --no-open if you cannot open the URL in the in-app browser"). No destructive or batch operations are involved, so the validation cap does not apply and the simple-skill exception holds.

5 / 5

Progressive Disclosure

The skill is under 50 lines, needs no external references, and is well organized as a single flow plus a "Useful flags" section, which per the judging guidelines earns a 5 for simple skills with well-organized sections. The only bundle asset (assets/remotion-icon.svg) is an icon, appropriately not referenced as instructional content.

5 / 5

Total

20

/

20

Passed

Description

53%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 names a distinct niche (Remotion video previewing), but it is too terse to be effective. It states a single action with no "when to use" guidance and few natural trigger terms, capping completeness and trigger quality at the midpoint.

Suggestions

Add an explicit trigger clause, e.g. "Use when creating or editing Remotion videos, rendering compositions, or when the user mentions Remotion or video previews."

Enumerate the concrete actions the skill covers (start Remotion Studio, open the live preview, keep it running while editing) so specificity reaches several concrete actions.

Include natural trigger synonyms such as "Studio", "live preview", and "render" that users would actually say when they need this skill.

DimensionReasoningScore

Specificity

"Preview a Remotion video" names the domain and a single concrete action (preview), matching the anchor for 1-2 concrete actions that are not comprehensive. It is more concrete than anchor 2's generic single action but lists nowhere near the several specific actions of anchor 4.

3 / 5

Completeness

The description clearly answers "what" (previews a Remotion video) but contains no "Use when..." clause or equivalent trigger guidance, which per the judging guidelines caps completeness at 3. It is not a 4 because the "when" is entirely absent rather than merely imprecise.

3 / 5

Trigger Term Quality

It includes relevant keywords ("Preview", "Remotion", "video") that a user working with Remotion would naturally say, but misses common variations and synonyms such as "Studio", "render", or "live preview", matching the anchor for some relevant keywords with missing variations.

3 / 5

Distinctiveness Conflict Risk

"Remotion" carves out a clear, specific niche with minimal conflict risk against generic skills, fitting anchor 4's "mostly distinct; minor overlap risk". It falls short of anchor 5 because the terse description provides only one distinct trigger term rather than a set of clearly distinct triggers.

4 / 5

Total

13

/

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/skills/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.