CtrlK
BlogDocsLog inGet started
Tessl Logo

remotion-best-practices

Best practices for Remotion - Video creation in React

51

Quality

64%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

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
SKILL.md
Quality
Evals
Security

Quality

Content

65%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 a textbook lean index with excellent one-level-deep reference structure, but its value is entirely contingent on the rules/ bundle, which is missing from this skill's files — every one of the 29 referenced paths is broken. Restoring the rules directory (or inlining minimal guidance for the most common tasks) is the single highest-impact fix.

Suggestions

Ship the referenced rules/*.md files in the skill bundle (including rules/subtitles.md); with none of the 29 files present, the skill currently routes Claude to nonexistent resources.

Fix the typo in the trigger line ('Use this skills' -> 'Use this skill') and normalize the subtitle link to the same rules/... path format used by the list.

Inline a minimal quick-start snippet or 2-3 core rules (e.g. a basic composition with useCurrentFrame) so the skill provides some standalone value before any rule file is loaded.

DimensionReasoningScore

Conciseness

The body is a lean ~40-line index with zero padding: it does not explain what Remotion or React is, and every line is either a trigger ('Use this skills whenever you are dealing with Remotion code') or a labeled pointer to a rule file. It assumes Claude's competence throughout, matching 'Lean and efficient; every token earns its place'.

5 / 5

Actionability

Concrete navigation guidance exists ('load the [./rules/subtitles.md](./rules/subtitles.md) file', 'Read individual rule files for detailed explanations and code examples') with specific per-topic pointers, but there is no inline executable guidance for common cases, and the detail lives entirely in files that are not present in this bundle. Guidance is real but incomplete, fitting 'Some concrete guidance but incomplete'.

3 / 5

Workflow Clarity

The skill is a simple routing/index skill and its single action (match the task to a rule file, with captions called out proactively) is stated, but the workflow's final step cannot be executed because none of the 29 referenced rules/*.md files exist in the bundle. The sequence as written is coherent, so it is not level 2, but the broken endpoint keeps it from level 4 or the simple-skill exception of 5.

3 / 5

Progressive Disclosure

The written structure is ideal for progressive disclosure — a concise overview with clearly signaled, one-level-deep, individually labeled references — but scoring against the actual bundle structure shows every referenced path (rules/subtitles.md and all 28 rules/*.md links) is unresolvable, breaking navigation. The excellent structure and signaling rule out level 2, but broken references prevent 4 or 5.

3 / 5

Total

14

/

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 distinct niche (Remotion video creation in React) but is under-specified: it names no concrete capabilities and provides no 'Use when' trigger guidance. Adding 2-3 concrete actions and an explicit trigger clause would move it into good-example territory.

Suggestions

Add concrete capabilities, e.g. 'Animate sequences, add captions and audio, embed videos and images, and render MP4s using Remotion'.

Append a trigger clause, e.g. 'Use when working with Remotion code, rendering videos in React, or when the user mentions compositions, <Sequence>, useCurrentFrame, or rendering MP4s'.

Include natural synonyms and file/term markers users would say (video rendering, animation, captions, .tsx video project) to broaden trigger-term coverage.

DimensionReasoningScore

Specificity

The description 'Best practices for Remotion - Video creation in React' names the domain but lists no concrete actions, matching the anchor 'Names the domain but actions are minimal or generic' (parallel to 'Processes PDF files'). No action verbs (render, animate, sequence, caption) appear, so it cannot reach level 3.

2 / 5

Completeness

A 'what' is present (best practices for video creation in React with Remotion) but there is no 'Use when...' clause or equivalent explicit trigger guidance in the description, which per the judging guidelines caps completeness at 3. It is not level 2 because the 'what' is domain-specific rather than extremely vague.

3 / 5

Trigger Term Quality

'Remotion', 'video', and 'React' are terms users would naturally say when they need this skill, but common variations and synonyms ('render video', 'MP4', 'animation', 'captions', 'make a video in React') are missing. Coverage is present but incomplete, fitting 'Some relevant keywords but missing common variations'.

3 / 5

Distinctiveness Conflict Risk

Naming the niche tool 'Remotion' makes this mostly distinct with clear niche identity; only minor overlap risk exists with general React or animation skills triggered by the bare words 'React' and 'video'. It is not level 5 because there are no explicit trigger phrases pinning when it applies.

4 / 5

Total

12

/

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: 29 missing

Warning

Total

14

/

16

Passed

Repository
fernandezbaptiste/trode
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.