CtrlK
BlogDocsLog inGet started
Tessl Logo

remotion

Best practices and comprehensive guide for Remotion - programmatic video creation in React with animations, compositions, and media handling

62

1.43x
Quality

45%

Does it follow best practices?

Impact

93%

1.43x

Average score across 3 eval scenarios

SecuritybySnyk

Advisory

Suggest reviewing before use

Optimize this skill with Tessl

npx tessl skill review --optimize ./cli-tool/components/skills/video/remotion/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Discovery

32%

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 identifies the technology (Remotion) and general domain (programmatic video in React) but reads more like a document title than a skill description. It lacks specific concrete actions Claude can perform and entirely omits a 'Use when...' clause, making it difficult for Claude to know when to select this skill over others.

Suggestions

Add an explicit 'Use when...' clause with trigger terms like 'Use when the user asks about creating videos with Remotion, programmatic video generation in React, video compositions, or rendering animations to MP4/WebM.'

Replace 'best practices and comprehensive guide' with specific concrete actions such as 'Create video compositions, add spring/interpolation animations, handle audio/video media, configure rendering pipelines, and build sequences in Remotion.'

Include common user-facing terms and file types like 'video rendering', '.mp4', 'useCurrentFrame', 'spring animations', 'video templates' to improve trigger term coverage.

DimensionReasoningScore

Specificity

Names the domain (Remotion, programmatic video creation in React) and mentions some areas (animations, compositions, media handling), but these are broad categories rather than specific concrete actions like 'create video compositions', 'add spring animations', 'render to MP4'.

2 / 3

Completeness

Describes what the skill covers (best practices and guide for Remotion) but completely lacks any 'Use when...' clause or explicit trigger guidance for when Claude should select this skill. Per the rubric, a missing 'Use when...' clause caps completeness at 2, and the 'what' portion is also weak (says 'best practices and comprehensive guide' rather than concrete capabilities), warranting a 1.

1 / 3

Trigger Term Quality

Includes relevant keywords like 'Remotion', 'React', 'video creation', 'animations', 'compositions', and 'media handling', which are terms users might use. However, it misses common variations like 'programmatic video', 'video rendering', 'video editing in code', 'useCurrentFrame', or file extensions like '.mp4'.

2 / 3

Distinctiveness Conflict Risk

Mentioning 'Remotion' specifically is distinctive and narrows the domain well, but the broad terms like 'React', 'animations', and 'media handling' could overlap with general React skills or animation libraries. The lack of explicit trigger conditions increases conflict risk.

2 / 3

Total

7

/

12

Passed

Implementation

57%

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

This skill functions primarily as a well-organized table of contents for Remotion reference materials, with excellent progressive disclosure but limited standalone actionability. The content suffers from some redundancy between the 'When to use', 'Core Concepts', and 'Key Features' sections, and lacks a clear workflow for the typical video creation process. The single code example is good but insufficient to make the main file independently useful.

Suggestions

Consolidate or remove the redundant 'Core Concepts' and 'Key Features' sections—they largely repeat the 'When to use' section and explain things Claude already knows

Add a brief workflow section showing the typical Remotion video creation process: define composition → create components → animate with frames → preview → render, with specific commands for each step

Add a second code example showing composition registration (registerRoot/Composition) since the current example only shows a component without showing how to wire it up

DimensionReasoningScore

Conciseness

The skill includes some unnecessary explanatory content (e.g., 'Remotion allows you to create videos using' with bullet points restating obvious concepts, the 'Key Features' section largely duplicates the 'When to use' section, and the 'Core Concepts' section explains things Claude already knows). However, the reference links section is well-organized and not overly verbose.

2 / 3

Actionability

The Quick Start Example provides one executable code snippet, and the Best Practices section gives concrete guidance. However, the skill is mostly a directory of references rather than containing actionable content itself—the actual executable guidance lives in the referenced files, and the main file provides limited concrete instruction beyond one example.

2 / 3

Workflow Clarity

There is no clear multi-step workflow defined. The Best Practices section lists tips but doesn't sequence them into a workflow. For a skill that covers video creation (which involves composition setup → animation → rendering), there's no explicit process flow or validation checkpoints (e.g., preview before render).

2 / 3

Progressive Disclosure

This is the skill's strongest dimension. It provides a clear overview with well-organized, categorized one-level-deep references to 25+ specific topic files. The references are grouped logically (Core Animation, Assets & Media, Text, Captions, etc.) with brief descriptions for each link.

3 / 3

Total

9

/

12

Passed

Validation

90%

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

Validation10 / 11 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

Total

10

/

11

Passed

Repository
davila7/claude-code-templates
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.