Best practices and comprehensive guide for Remotion - programmatic video creation in React with animations, compositions, and media handling
55
33%
Does it follow best practices?
Impact
93%
1.43xAverage score across 3 eval scenarios
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./cli-tool/components/skills/video/remotion/SKILL.mdQuality
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 domain (programmatic video in React) but reads more like a document title than a skill description. It lacks specific concrete actions, a 'Use when...' clause, and sufficient trigger terms to help Claude reliably select this skill from a large pool.
Suggestions
Add an explicit 'Use when...' clause, e.g., 'Use when the user asks about Remotion, creating videos programmatically in React, or rendering video compositions with code.'
Replace the vague 'best practices and comprehensive guide' framing with specific actions like 'Create video compositions, add animations and transitions, handle audio/video media, configure rendering and output settings.'
Include additional natural trigger terms users might say, such as 'programmatic video', 'video rendering', 'React video', 'motion graphics in code', or 'Remotion project'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description 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 transitions', 'render to MP4'. | 2 / 3 |
Completeness | The description addresses 'what' (best practices and guide for Remotion video creation) but completely lacks a 'Use when...' clause or any 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' itself is also somewhat vague ('best practices and comprehensive guide'), so this scores a 1. | 1 / 3 |
Trigger Term Quality | Includes relevant keywords like 'Remotion', 'React', 'video creation', 'animations', 'compositions', and 'media handling' which users might naturally use. However, it misses common variations like 'programmatic video', 'video rendering', 'video editing in code', 'motion graphics', or file extensions. | 2 / 3 |
Distinctiveness Conflict Risk | Mentioning 'Remotion' specifically provides some distinctiveness since it's a specific library, but the broader terms like 'React', 'animations', and 'media handling' could overlap with general React development skills or other animation/media skills. | 2 / 3 |
Total | 7 / 12 Passed |
Implementation
35%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 verbose table of contents for Remotion reference files. While the progressive disclosure structure with categorized references is reasonable, the main file is padded with unnecessary explanatory sections (Core Concepts, Key Features, When to use) that explain things Claude already knows. The single Quick Start example is the strongest element, but the skill would benefit significantly from trimming redundant sections and adding more actionable workflow guidance.
Suggestions
Remove the 'Core Concepts', 'Key Features', and 'When to use' sections entirely — they explain things Claude already knows and add no actionable value.
Add a concrete end-to-end workflow: project setup → define composition → add animations → preview → render, with specific commands for each step.
Prioritize the reference files by indicating which are essential vs. advanced, rather than listing all 25+ files with equal weight.
Add a second Quick Start example showing composition registration (registerRoot, Composition component) since that's a critical step Claude needs to know.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is extremely verbose with extensive lists of features, concepts, and references that largely restate what's already obvious from the file names. The 'Core Concepts' and 'Key Features' sections explain things Claude already knows (what React components are, what frame-based animation means). The 'When to use' section is redundant with the content itself. | 1 / 3 |
Actionability | There is one concrete, executable Quick Start example which is good, and the best practices section provides specific guidance (e.g., avoid CSS animations, use interpolate). However, the bulk of the skill is a table of contents pointing to reference files rather than providing actionable guidance itself, and the best practices are fairly surface-level. | 2 / 3 |
Workflow Clarity | The best practices provide a loose sequence of considerations, and the Quick Start example shows a basic pattern. However, there's no clear multi-step workflow for creating a Remotion video from start to finish (project setup → composition definition → animation → rendering), and no validation checkpoints for the rendering process. | 2 / 3 |
Progressive Disclosure | The skill has well-organized categories with clear one-level-deep references to 25+ reference files, which is good structure. However, since no bundle files were provided, we can't verify these references exist. More importantly, the main SKILL.md itself contains too much inline content (Core Concepts, Key Features, When to use) that is largely filler rather than a lean overview, and the sheer number of references without any prioritization makes navigation harder. | 2 / 3 |
Total | 7 / 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.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
3b3ea9e
Table of Contents
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.