remotion-best-practices

Best practices for Remotion - Video creation in React

Quality

65%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./SKILLs/remotion/SKILL.md

The canonical home for this skill is remotion-best-practices in vercel-labs/json-render

Quality

Content

86%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 progressive-disclosure index: lean, well-organized, and clearly routing to per-topic rule files, with only minor actionability and selection-guidance gaps.

Dimension	Reasoning	Score
Conciseness	The body is a lean index: a one-line 'When to use', a short captions note, and a flat list of rule files each with a single descriptive phrase — no padded explanations of concepts Claude already knows.	5 / 5
Actionability	It routes Claude to specific files per topic (e.g. 'load the ./rules/subtitles.md file'), which is concrete and actionable navigation, but no executable code lives inline.	4 / 5
Workflow Clarity	The single workflow — identify the topic, read the matching rule file — is clear and the captions section models the routing, but selecting among 29 files relies on inferring from descriptions rather than explicit decision guidance.	4 / 5
Progressive Disclosure	A clean overview with one-level-deep references, each labeled with a concise description and consistent paths, matches the well-signaled, easily navigable structure of the score-5 anchor.	5 / 5
	Total	18 / 20 Passed

Description

43%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 distinct but too thin: it states only that the skill offers 'best practices' for Remotion and omits any use-when trigger guidance or concrete capabilities.

Suggestions

Add a concrete capability list, e.g. 'Best practices for Remotion: composing video sequences, animations, audio, and rendering in React.'

Append an explicit trigger clause such as 'Use when writing or debugging Remotion code, or when the user mentions video rendering in React.'

Include synonyms/file cues users naturally say (rendering, animation, .tsx compositions) to broaden trigger coverage.

Dimension	Reasoning	Score
Specificity	The phrase 'Best practices for Remotion - Video creation in React' names the domain clearly but the only action is the generic 'Best practices', with no concrete verbs (cf. anchor 2 'Processes PDF files').	2 / 5
Completeness	It gives a vague 'what' ('Best practices') and no 'when' / 'Use when...' clause, which the guidelines cap at 3; the absent trigger guidance pulls it to 2.	2 / 5
Trigger Term Quality	It includes relevant natural terms ('Remotion', 'Video creation', 'React') a user might say, but offers no synonyms or variations (rendering, animation, .tsx) beyond those three.	3 / 5
Distinctiveness Conflict Risk	Naming the specific framework Remotion (video creation in React) carves a clear niche with distinct triggers and minimal overlap with other skills.	5 / 5
	Total	12 / 20 Passed

Validation

81%

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

Validation for skill structure

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning
relative_links	Relative link issues: 30 missing	Warning

	Total	13 / 16 Passed

Repository: netease-youdao/LobsterAI
Path: SKILLs/remotion/SKILL.md
Commit: 100d3f7

Reviewed: 2 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.