remotion-best-practices

Best practices for Remotion - Video creation in React

Quality

51%

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 ./demo-project/.claude/skills/remotion-best-practices/SKILL.md

Quality

Content

53%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 well-organized and token-efficient as a reference index, but it relies entirely on a rules/ bundle that does not exist, breaking actionability, navigation, and the terminal workflow step. The skill cannot actually deliver its referenced detail.

Suggestions

Add the missing rules/ directory with the referenced rule files (e.g., rules/animations.md, rules/timing.md), or remove the dead links.

Include at least one small inline executable snippet or concrete starting pattern so the skill is actionable before any rule file is loaded.

Fix the typo "Use this skills" to "Use this skill" and verify each listed link resolves to a real file.

Dimension	Reasoning	Score
Conciseness	The body is lean: a short "When to use," a captions pointer, and a one-line-per-entry index of rule files with concise descriptors, with no over-explanation of concepts Claude already knows.	5 / 5
Actionability	The body provides only high-level hints (one-line descriptors per rule) and directs Claude to "Read individual rule files," but contains no executable code or commands itself, and the referenced rule files do not exist, so the guidance cannot be executed.	2 / 5
Workflow Clarity	A simple reference workflow is present and unambiguous (consult the relevant rule file per topic), but the workflow dead-ends because every referenced rules/*.md file is missing, leaving the sequence incomplete at its terminal step.	3 / 5
Progressive Disclosure	The intended structure is a clean one-level-deep index with clearly signaled references, which is ideal, but the rules/ directory and all referenced files are absent, so navigation is effectively non-functional.	2 / 5
	Total	12 / 20 Passed

Description

48%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 specific niche but is vague on concrete capabilities and omits any explicit trigger guidance, capping completeness. It is distinguishable yet would benefit from named actions and a "Use when..." clause.

Suggestions

Replace the generic "Best practices" framing with 2-4 concrete actions (e.g., render, compose, animate, and synchronize media in Remotion).

Add an explicit "Use when..." clause listing natural trigger phrases (e.g., "Use when working with Remotion code, video rendering in React, or composition/animation tasks").

Include common synonyms and file/keyword variations users might say (rendering, animation, compositions, .tsx video) to improve trigger coverage.

Dimension	Reasoning	Score
Specificity	The description names the domain ("Remotion - Video creation in React") but offers no concrete actions, only the generic phrase "Best practices," which is minimal and non-specific rather than naming 1-2 concrete operations.	2 / 5
Completeness	It gives a clear "what" (best practices for Remotion video creation) but includes no "Use when..." clause or equivalent trigger guidance, so "when" is missing; per the rubric a missing trigger clause caps completeness at 3.	3 / 5
Trigger Term Quality	"Remotion," "Video creation," and "React" are relevant natural keywords a user would say, but common variations like rendering, animation, or composition are missing.	3 / 5
Distinctiveness Conflict Risk	The Remotion-in-React niche is mostly distinct with minor overlap risk against generic React skills, but the absence of an explicit trigger phrase keeps it just below a clearly distinct 5.	4 / 5
	Total	12 / 20 Passed

Validation

87%

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

Validation for skill structure

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning
relative_links	Relative link issues: 29 missing	Warning

	Total	14 / 16 Passed

Repository: fernandezbaptiste/trode
Path: demo-project/.claude/skills/remotion-best-practices/SKILL.md
Commit: 46ff4b8

Reviewed: 1 day 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.