remotion-video-creation

Best practices for Remotion - Video creation in React. 29 domain-specific rules covering 3D, animations, audio, captions, charts, transitions, and more.

Quality

83%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No known issues

Quality

Content

85%

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 hub: concise, well-organized, and easy to navigate. Its only weakness is actionability within the body itself, since all executable guidance lives in the referenced rule files rather than inline.

Suggestions

Add a short inline quick-start snippet (a minimal Remotion composition registration) so Claude has one concrete starting point before reading rule files.

Fix the grammatical typo "Use this skills" to "Use this skill" in the When-to-use section.

Dimension	Reasoning	Score
Conciseness	The body is a lean index with no padding and no explanation of concepts Claude already knows; every line is a one-line pointer to a rule file, so each token earns its place.	3 / 3
Actionability	It gives concrete navigation guidance (which rule file to read per domain) but no executable code or commands within the body itself; the actionable detail is fully delegated to the referenced files.	2 / 3
Workflow Clarity	As a simple single-action skill, the workflow is unambiguous: "When to use" states the trigger and "How to use" states the single action (read the relevant rule file), satisfying the simple-skill allowance.	3 / 3
Progressive Disclosure	A clear overview hub with 29 well-signaled, one-level-deep references each annotated with a short description; content is appropriately split and navigation is easy.	3 / 3
	Total	11 / 12 Passed

Description

82%

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 specific, rich in natural trigger terms, and clearly distinct, but it omits an explicit "Use when..." clause, capping completeness at 2. Adding trigger guidance would lift the strongest remaining weakness.

Suggestions

Append an explicit trigger clause, e.g. "Use when working with Remotion compositions, rendering video in React, or when the user mentions Remotion, programmatic video, or React video rendering."

Lead with the verb-driven action (e.g. "Apply Remotion best practices...") so the capability reads as concrete actions rather than a topic list.

Dimension	Reasoning	Score
Specificity	"29 domain-specific rules covering 3D, animations, audio, captions, charts, transitions, and more" lists multiple specific concrete capability areas rather than vague abstraction, matching the score-3 anchor.	3 / 3
Completeness	It clearly answers "what" (best practices / 29 rules across named domains) but lacks any explicit "Use when..." trigger clause, so per the guideline a missing trigger caps completeness at 2.	2 / 3
Trigger Term Quality	Natural user-facing terms like "Remotion", "Video creation in React", "3D", "animations", "audio", "captions", "charts", and "transitions" give good coverage of phrases a user would actually say.	3 / 3
Distinctiveness Conflict Risk	"Remotion - Video creation in React" is a clear, narrow niche with distinct triggers unlikely to conflict with unrelated skills.	3 / 3
	Total	11 / 12 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: 28 missing	Warning

	Total	14 / 16 Passed

Repository: affaan-m/ECC
Commit: 754b8dd

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