CtrlK
BlogDocsLog inGet started
Tessl Logo

remotion-best-practices

Best practices for Remotion - Video creation in React

52

Quality

59%

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 ./SKILLs/remotion/SKILL.md

The canonical home for this skill is remotion-best-practices in vercel-labs/json-render

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 body is a well-organized, token-efficient index that correctly uses progressive disclosure: a brief trigger line plus a comprehensive annotated list of one-level-deep rule files. Its main weaknesses are that the referenced rule files are missing from the bundle entirely and that the SKILL.md body itself provides no actionable guidance, code, or examples beyond navigation.

Suggestions

Include the referenced rules/ directory in the skill bundle — all 31 paths cited (rules/animations.md, ./rules/subtitles.md, etc.) are absent, leaving every link broken.

Fold the 'Captions' section into the unified rule list (or as an entry in the same format) so all reference navigation follows one consistent pattern.

Add a few lines of inline guidance or a minimal code snippet for the most common Remotion tasks so the skill delivers value even before a rule file is loaded.

DimensionReasoningScore

Conciseness

The body is a lean index with no padding and no explanation of concepts Claude already knows: a one-line 'When to use' ('Use this skills whenever you are dealing with Remotion code'), and 30 one-line annotated links. Every token earns its place, matching 'Lean and efficient; assumes Claude's competence'.

5 / 5

Actionability

Pointers are concrete per topic (e.g., 'load the ./rules/subtitles.md file' for captions, 'rules/animations.md - Fundamental animation skills'), but the body contains no code, commands, or executable guidance of its own, and all the referenced rule files are absent from the bundle, so nothing can actually be executed. Fits 'Some concrete guidance but incomplete'.

3 / 5

Workflow Clarity

For a simple index skill the single action (identify the topic, read the matching rule file) is unambiguous via the annotated list, but there are minor gaps: subtitles.md is segregated under a separate 'Captions' heading instead of the unified rule list, and there is no guidance when multiple rules apply (e.g., videos vs. trimming). Matches 'Clear sequence with most checkpoints present; minor validation gaps' at the structural level.

4 / 5

Progressive Disclosure

Structurally exemplary progressive disclosure: a short overview with clearly signaled, one-level-deep, individually annotated references (each 'rules/*.md' link has a one-line description). However, none of the 31 referenced files (including ./rules/subtitles.md and all rules/*.md) exist in the provided bundle, so every reference is broken and navigation does not resolve — a gap that keeps this below a 5.

4 / 5

Total

16

/

20

Passed

Description

43%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 short and names a distinct, recognizable domain (Remotion video creation in React), which gives it excellent distinctiveness. However, it specifies no concrete capabilities, contains no trigger guidance for when to use the skill, and misses natural trigger terms like animation, captions, or rendering.

Suggestions

Add an explicit 'Use when...' clause, e.g., 'Use when working with Remotion code, rendering videos in React, or when the user mentions Remotion, programmatic video, or video compositions.'

Enumerate 2-3 concrete capabilities instead of the generic 'Best practices', e.g., 'Animations, captions, transitions, audio/video embedding, and rendering for Remotion (video creation in React).'

Include natural trigger-term variations users would say (animation, captions/subtitles, video rendering, React video) to broaden keyword coverage.

DimensionReasoningScore

Specificity

Names the domain ('Remotion - Video creation in React') but lists no concrete actions or capabilities, matching the anchor 'Names the domain but actions are minimal or generic'. It is not a 3 because no specific action verbs or capability list (e.g., animations, captions, transitions) appear.

2 / 5

Completeness

Has only a vague 'what' ('Best practices for Remotion') and no 'when' clause whatsoever, exactly matching 'Has a vague what and no when'. The missing 'Use when...' guidance also caps this dimension at 3 per the judging guidelines.

2 / 5

Trigger Term Quality

'Remotion', 'Video', and 'React' are natural keywords a user would say, but common variations and synonyms (animation, captions, subtitles, rendering, programmatic video) are missing, fitting 'Some relevant keywords but missing common variations or synonyms'. Not a 4 because coverage is thin for a multi-faceted skill.

3 / 5

Distinctiveness Conflict Risk

'Remotion' is a unique named product with a clear niche (video creation in React), so it is highly distinguishable from other skills with minimal conflict risk, matching 'Clear niche with distinct triggers; minimal conflict risk'.

5 / 5

Total

12

/

20

Passed

Validation

81%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

relative_links

Relative link issues: 30 missing

Warning

Total

13

/

16

Passed

Repository
netease-youdao/LobsterAI
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.