remotion

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

1.43x

Quality

63%

Does it follow best practices?

Impact

93%

1.43x

Average score across 3 eval scenarios

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./cli-tool/components/skills/video/remotion/SKILL.md

Quality

Content

65%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.

This is a well-structured reference skill with excellent progressive disclosure — a lean overview pointing to a complete, verified set of one-level-deep reference files. Its main weakness is redundant capability enumeration across three early sections and the absence of an explicit workflow with checkpoints.

Suggestions

Collapse the overlapping 'When to use', 'Core Concepts', and 'Key Features' sections into a single capability overview to remove the triple-restated list.

Add a brief end-to-end workflow (e.g. define composition -> animate with useCurrentFrame -> preview in Studio -> render) with an explicit 'verify in Remotion Studio before rendering' checkpoint.

Optionally inline one or two more tiny executable snippets for the most common tasks (e.g. a minimal Composition registration) so the body covers more common cases without relying on references.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient and does not explain concepts Claude already knows, but the capability list is restated three times across 'When to use', 'Core Concepts', and 'Key Features', which is unnecessary padding that could be tightened into a single pass.	3 / 5
Actionability	It provides a concrete, executable Quick Start example with real imports and a numbered Best Practices list of clear directives, with the bulk of executable detail appropriately delegated to reference files; only minor gaps remain in-body.	4 / 5
Workflow Clarity	The body offers a categorized navigational index and best-practice directives, but there is no explicit multi-step workflow with validation checkpoints; since the skill is not destructive/batch, this is acceptable but stops at a sequence-implicit level.	3 / 5
Progressive Disclosure	The body is a clear overview with a well-signaled, categorized index of 28 one-level-deep reference files (all verified present), each with a short description, giving easy navigation with no nested references.	5 / 5
	Total	15 / 20 Passed

Description

61%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 identifies a clear product niche and surfaces relevant capability keywords, but it is missing an explicit 'Use when...' trigger clause, which caps its completeness. Tightening the topical enumeration into concrete actions would raise specificity.

Suggestions

Add an explicit trigger clause, e.g. 'Use when creating or editing videos programmatically with Remotion, or when the user mentions Remotion, programmatic video, or rendering React components to video.'

Replace topical nouns with concrete verb-actions (e.g. 'render videos, animate elements frame-by-frame, trim and sequence media, generate captions') to improve specificity.

Drop the 'Best practices and comprehensive guide' padding to make the opening leaner and more action-oriented.

Dimension	Reasoning	Score
Specificity	The description names the domain ('programmatic video creation in React') and enumerates capability areas ('animations, compositions, and media handling'), but these are topical nouns rather than concrete verb-actions like 'render', 'extract', or 'trim', and 'Best practices and comprehensive guide' is mild padding.	3 / 5
Completeness	It clearly answers 'what' (programmatic video creation in React) but has no 'Use when...' clause or equivalent explicit trigger guidance, which per the rubric caps completeness at 3.	3 / 5
Trigger Term Quality	It includes strong natural keywords users would say — 'Remotion', 'video creation', 'React', 'animations', 'compositions', 'media handling' — with only a few common variations missing (e.g. 'render', 'export', 'make videos').	4 / 5
Distinctiveness Conflict Risk	Naming the specific product 'Remotion' gives it a clear, distinct niche with minimal conflict risk, though the lack of an explicit use-trigger leaves minor overlap ambiguity with generic React or animation skills.	4 / 5
	Total	14 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: davila7/claude-code-templates
Path: cli-tool/components/skills/video/remotion/SKILL.md
Commit: 8a3613d

Reviewed: 3 days 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.