remotion-best-practices

Best practices for Remotion - Video creation in React

1.26x

Quality

47%

Does it follow best practices?

Impact

100%

1.26x

Average score across 3 eval scenarios

Securityby

Advisory

Suggest reviewing before use

Fix and improve this skill with Tessl

tessl review fix ./skills/remotion-best-practices/SKILL.md

Quality

Content

72%

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

This skill functions well as a navigation hub/index for Remotion-related rules, with excellent progressive disclosure and concise presentation. Its main weakness is the complete absence of any inline actionable content—no quick-start example, no common patterns, no code snippets—making it purely a table of contents rather than a skill that provides immediate value. Adding a brief quick-start section with a minimal Remotion example would significantly improve actionability.

Suggestions

Add a 'Quick start' section with a minimal executable Remotion composition example (e.g., a simple component with useCurrentFrame and interpolate) so Claude has immediate actionable guidance without needing to read sub-files.

Consider grouping the rule links into logical categories (e.g., 'Getting Started', 'Media', 'Animation', 'Captions', 'Advanced') to provide workflow clarity and help Claude navigate to the right rule faster.

Dimension	Reasoning	Score
Conciseness	The content is lean and efficient. It provides a brief 'when to use' and 'how to use' section followed by a well-organized list of references. No unnecessary explanations of what Remotion is or how React works.	3 / 3
Actionability	The skill itself contains no concrete code examples or executable guidance—it's purely a navigation index. While the references are clearly labeled, Claude must follow links to get any actionable content. For an index/hub skill this is somewhat expected, but it still lacks any quick-start code or inline examples.	2 / 3
Workflow Clarity	There is no workflow or sequencing guidance. For someone new to Remotion, there's no indication of where to start, what order to read rules in, or how different rules relate to each other. However, since this is primarily an index skill pointing to individual rule files, the lack of a multi-step workflow is partially justified.	2 / 3
Progressive Disclosure	This is an excellent example of progressive disclosure: a concise overview with well-signaled, one-level-deep references to individual rule files. Each link has a clear, descriptive label indicating what the referenced file covers.	3 / 3
	Total	10 / 12 Passed

Description

22%

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 too terse and vague, relying on 'best practices' without specifying what actions the skill enables or when it should be selected. While 'Remotion' provides some distinctiveness, the lack of concrete capabilities and explicit trigger guidance makes it poorly suited for skill selection among many options.

Suggestions

Replace 'Best practices' with specific concrete actions, e.g., 'Create video compositions, configure rendering pipelines, animate React components, and export videos using Remotion.'

Add an explicit 'Use when...' clause, e.g., 'Use when the user asks about Remotion, programmatic video creation in React, video rendering, compositions, or animation sequences.'

Include additional natural trigger terms users might say, such as 'animation', 'render video', 'video export', 'Remotion composition', or 'React video'.

Dimension	Reasoning	Score
Specificity	The description says 'best practices' which is vague and does not list any concrete actions. It names the domain (Remotion, video creation in React) but provides no specific capabilities like 'create video compositions', 'render animations', or 'configure output formats'.	1 / 3
Completeness	The 'what' is extremely vague ('best practices') and there is no 'when' clause or explicit trigger guidance at all. Per the rubric, a missing 'Use when...' clause caps completeness at 2, and the weak 'what' brings it down to 1.	1 / 3
Trigger Term Quality	It includes 'Remotion', 'Video creation', and 'React' which are relevant keywords a user might mention. However, it misses common variations like 'animation', 'render', 'video editing', 'composition', '.mp4', or 'programmatic video'.	2 / 3
Distinctiveness Conflict Risk	Mentioning 'Remotion' specifically is fairly distinctive and narrows the niche, but 'best practices' and 'React' are broad enough that it could overlap with general React coding skills or other video-related skills.	2 / 3
	Total	6 / 12 Passed

Validation

90%

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 — 10 / 11 Passed

Validation for skill structure

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning

	Total	10 / 11 Passed

Repository: tibelf/ai_project_init
Commit: 56f4516

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