remotion-best-practices

Router for all Remotion skills

Quality

55%

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

Quality

Content

78%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 lean router — concise, well-sectioned, with concrete trigger-to-skill dispatches — but its progressive disclosure relies on sub-skill files that are not present in this bundle, leaving all of its detail references dangling.

Suggestions

Ensure the referenced sub-skills (remotion-create, remotion-markup, remotion-maps, etc.) are bundled as siblings so the ./remotion-*/SKILL.md links resolve, or change the links to point at the installed-skill lookup mechanism.

Add a one-line precedence rule for overlapping triggers (e.g. clarify when 'Creating a video' vs 'New project setup' should each load remotion-create) to remove dispatch ambiguity.

Tighten soft triggers like 'If relevant' and 'If you are writing Remotion React Markup' into sharper, user-intent-matching conditions.

Dimension	Reasoning	Score
Conciseness	Each section is a tight 1-2 sentence trigger plus a single dispatch link with no concept explanations of what Remotion/video/rendering is, matching 'lean and efficient; assumes Claude's competence; every token earns its place'.	5 / 5
Actionability	Every section pairs a concrete trigger with an executable dispatch ('load [Remotion Captions](./remotion-captions/SKILL.md)'), but a few triggers are soft ('If relevant', 'If you are writing...') leaving minor gaps versus fully specified dispatch.	4 / 5
Workflow Clarity	The body is a clear, well-organized condition-to-skill routing table (simple-skill exception applies — single dispatch action), but 'Creating a video' and 'New project setup' both load remotion-create with no guidance on precedence when multiple sections apply, a minor ambiguity.	4 / 5
Progressive Disclosure	The signaling and one-level-deep structure are excellent, but scored against the actual bundle: every referenced path (./remotion-create/SKILL.md, ./remotion-markup/SKILL.md, etc.) is missing — only assets/remotion-icon.png is present — so navigation to the detail content is broken despite good structure.	3 / 5
	Total	16 / 20 Passed

Description

32%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 terse and identifies a clear niche, but it is too abstract: it gives a vague 'what' (router) and entirely omits a 'when' trigger clause, so it does not tell Claude when to reach for this skill over its sub-skills.

Suggestions

Add an explicit 'Use when...' clause listing concrete triggers (e.g. 'Use when the user wants to make, render, or edit a Remotion video and you need to decide which Remotion skill to load').

Replace the abstract word 'router' with 2-3 concrete actions or outcomes so the 'what' is unambiguous (e.g. 'Routes Remotion requests to the right specialized skill — video creation, markup, rendering, captions, maps').

Include the natural user terms as keywords (video, composition, render, Studio, captions) so the description matches how users actually phrase requests.

Dimension	Reasoning	Score
Specificity	The phrase 'Router for all Remotion skills' names the domain (Remotion skills) and a single minimal action ('router'), matching the anchor 'Names the domain but actions are minimal or generic' rather than the 3-anchor which requires 1-2 concrete actions.	2 / 5
Completeness	The 'what' ('router') is abstract and there is no 'when' / 'Use when' clause at all; per the cap a missing trigger clause limits completeness to 3, and the vague-what-plus-no-when pattern matches anchor 2.	2 / 5
Trigger Term Quality	Only 'Remotion' is a natural keyword; the natural phrases users actually say ('make a video', 'render', 'captions', 'maps') are absent and 'router' is technical jargon, fitting 'missing the natural phrases users say'.	2 / 5
Distinctiveness Conflict Risk	'Router for all Remotion skills' carves a clear Remotion niche with minimal conflict against non-Remotion skills; the only overlap is with its own sub-skills, which is intentional for a router (anchor 4, 'mostly distinct; minor overlap risk').	4 / 5
	Total	10 / 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
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning
relative_links	Relative link issues: 12 missing	Warning

	Total	14 / 16 Passed

Repository: remotion-dev/remotion
Path: packages/skills/skills/remotion-best-practices/SKILL.md
Commit: 77354de

Reviewed: about 21 hours 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.