CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

remotion-best-practices

Best practices for Remotion - Video creation in React

Quality

72%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./.claude/skills/remotion-best-practices/SKILL.md

The canonical home for this skill is remotion-best-practices in calesthio/OpenMontage

SKILL.md
Quality
Evals
Security

Quality

Content

75%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 SKILL.md body is an efficient, well-organized index that routes Remotion tasks to per-topic rule files with clear one-level-deep references. Its main gaps are structural consistency (mixed path styles, four rules missing from the master list) and the absence of the referenced rule files in the bundle it ships with.

Suggestions

Normalize link paths to a single style (e.g. 'rules/3d.md' everywhere) so references resolve consistently.

Merge the four topic-section rules (subtitles.md, ffmpeg.md, audio-visualization.md, sound-effects.md) into the 'How to use' list, or make the topic sections the single routing mechanism, so no rule is discoverable in only one place.

Tighten the opening 'When to use' sentence to a direct trigger statement (e.g. 'Use when writing or reviewing Remotion code.') to remove the remaining padding.

DimensionReasoningScore

Conciseness

The body is a lean index: every entry is a one-line pointer with a short scope description, and it assumes Claude's competence with no concept explanations. Minor trimmable content keeps it at 4 rather than 5: the padded opener 'Use this skills whenever you are dealing with Remotion code to obtain the domain-specific knowledge' and the four topic sections that partially duplicate the flat list's routing function.

4 / 5

Actionability

As an instruction-only index skill, the guidance is concrete and executable: 'When dealing with captions or subtitles, load the ./rules/subtitles.md file' gives an explicit trigger plus a specific file action, and each list entry names what the file covers. It is not 5 because there is no code or command at all and the flat list's one-line descriptions give no executable detail for choosing among closely related rules (e.g. timing vs. animations).

4 / 5

Workflow Clarity

The single routing action (identify the task, load the matching rule file) is unambiguous for the topic sections, and no destructive or batch operations require validation. It falls short of 5 because the structure is split: four rules (subtitles, ffmpeg, audio-visualization, sound-effects) appear only in topic sections and are missing from the 'How to use' list, and choosing among the ~26 remaining flat-list rules relies on terse descriptions rather than clear routing.

4 / 5

Progressive Disclosure

Good structure: the body is a pure overview with clearly signaled, one-level-deep references and per-file scope notes, matching anchor 4's 'good structure; references mostly clear'. It does not reach 5 because link paths are inconsistent ('./rules/subtitles.md' vs 'rules/3d.md'), and the referenced rule files are not present in the provided bundle (no rules/ directory exists), so navigation dangles; nor is it 3, since the references are clearly signaled and nothing that belongs in a separate file is inlined.

4 / 5

Total

16

/

20

Passed

Description

60%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 clear, distinctive niche (Remotion) but is under-specified: it names no concrete capabilities and omits any explicit 'use when' trigger guidance. Adding action verbs and a trigger clause would move it to the top of the scale.

Suggestions

State concrete actions, e.g. 'Best practices for Remotion - programmatic video creation in React: animations, transitions, audio, captions, and rendering.'

Add an explicit trigger clause, e.g. 'Use when working with Remotion code, compositions, or @remotion/* packages, or when the user mentions Remotion or making videos in React.'

Include a few natural synonyms users say ('motion graphics', 'video rendering', 'animation') to broaden trigger-term coverage.

DimensionReasoningScore

Specificity

The description 'Best practices for Remotion - Video creation in React' names the domain clearly (Remotion, video creation in React) but offers zero concrete actions; 'Best practices' is generic. It matches anchor 2 ('Names the domain but actions are minimal or generic'), not 3, because no specific action like 'create animations' or 'render videos' is stated.

2 / 5

Completeness

The 'what' is reasonably clear (Remotion best practices for React video creation), but there is no 'Use when...' clause or equivalent trigger guidance, capping completeness at 3 per the judging guidelines. It is not 4 because 'when' is entirely absent rather than just under-specified; it is above 2 because the 'what' concretely names the tool and domain rather than being vague.

3 / 5

Trigger Term Quality

'Remotion', 'Video creation', and 'React' are natural terms a user needing this skill would say, giving good keyword coverage. It falls short of anchor 5 because common variations such as 'animation', 'video rendering', 'motion graphics', or task terms like 'transitions' and 'captions' are absent.

4 / 5

Distinctiveness Conflict Risk

'Remotion' is a highly specific, niche tool name that serves as a distinct trigger; virtually no other skill would compete for it. The trailing 'Video creation in React' adds minor context but 'Remotion' dominates, so conflict risk is minimal (anchor 5).

5 / 5

Total

14

/

20

Passed

Validation

87%

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

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

relative_links

Relative link issues: 34 missing

Warning

Total

14

/

16

Passed

Repository

calesthio/OpenMontage

Path

.claude/skills/remotion-best-practices/SKILL.md

Reviewed

Table of Contents

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.