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

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./.agents/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 admirably concise and well-indexed as a navigation hub, but it provides almost no actionable guidance inline and—critically—points to a ./rules/ bundle that is not present in the staged skill, so the progressive-disclosure structure cannot actually be navigated.

Suggestions

Ship the ./rules/ bundle alongside SKILL.md (the tarball contains only SKILL.md), or remove/inline any rule references that have no backing file so links are not dangling.

Add a minimal inline quick-start snippet (e.g., a basic <Composition> + <Sequence> + interpolate example) so the skill is actionable before any rule file is loaded.

Consolidate the scattered top rule pointers into the 'How to use' index and signal each reference clearly (e.g., bolded **Captions**: see rules/subtitles.md) so the primary navigation is unambiguous.

Dimension	Reasoning	Score
Conciseness	The body is extremely lean — short section headers each with a single purpose sentence and a pointer, plus a flat bulleted index of rule files. It assumes Claude's competence and explains nothing Claude already knows, so every token earns its place.	5 / 5
Actionability	The body gives only high-level hints ('load the file for more information', 'FFmpeg should be used') with no inline code, commands, or concrete steps. This matches 'minimal concrete guidance; high-level hints but missing the specific steps to execute'; it is not score 1 because the per-rule blurbs do name concrete tools (Three.js, Mapbox, ElevenLabs, Medicabunny).	2 / 5
Workflow Clarity	A rough sequence exists (caption → ffmpeg → audio viz → sound → 'How to use' index), but there are no validation checkpoints, and the 'How to use' step 'Read individual rule files' is vague. This fits 'steps listed but validation gaps; checkpoints missing or implicit'; no destructive/batch cap applies since the skill is non-destructive.	3 / 5
Progressive Disclosure	The body relies entirely on ./rules/*.md references, but the rules/ bundle directory is absent from the provided skill (the tarball contains only SKILL.md), so the references are broken/dangling and navigation is impossible. Even structurally, the top-of-file rule pointers (subtitles.md, ffmpeg.md, etc.) are buried among sections rather than clearly signaled as the primary index, fitting 'minimal structure; references buried.'	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 correctly identifies a specific, distinct niche (Remotion) but is thin: it states only 'Best practices' with no concrete actions and no explicit 'Use when...' trigger guidance. Trigger terms are present but lack synonyms and natural phrasings.

Suggestions

Add 2–4 concrete actions, e.g. 'Compose, animate, and render React videos; manage audio, captions, transitions, and timing.'

Append an explicit trigger clause, e.g. 'Use when writing or debugging Remotion compositions, animations, or server-side video rendering.'

Include natural synonyms users say ('video', 'animation', 'rendering', 'React video') alongside 'Remotion' to broaden trigger coverage.

Dimension	Reasoning	Score
Specificity	The description names the domain ('Remotion', 'Video creation in React') but lists no concrete actions — it says only 'Best practices', which is minimal and generic. It fits the score-2 anchor (names domain, actions minimal/generic) better than score 3, which requires 1–2 concrete actions.	2 / 5
Completeness	There is a clear 'what' (best practices for Remotion video creation) but no 'when'/'Use when...' clause, so completeness is capped at 3 per the guideline that a missing trigger clause caps completeness at 3.	3 / 5
Trigger Term Quality	'Remotion' and 'Video creation in React' are relevant natural terms a user might say, but common synonyms and trigger phrases ('video', 'animations', 'rendering', '.tsx compositions') are missing. This matches 'some relevant keywords but missing common variations or synonyms.'	3 / 5
Distinctiveness Conflict Risk	'Remotion' is a specific, niche framework, so the skill is mostly distinct with only minor overlap risk against generic React/video skills. It is not a score-5 niche because the description lacks the explicit concrete triggers that would make conflicts unlikely.	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: 34 missing	Warning

	Total	14 / 16 Passed

Repository: calesthio/OpenMontage
Path: .agents/skills/remotion-best-practices/SKILL.md
Commit: 08e2151

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