CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

remotion-best-practices

Best practices for Remotion - Video creation in React

Quality

56%

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 ./.agents/skills/remotion-best-practices/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

46%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 cleanly organized, token-efficient index that correctly practices one-level-deep progressive disclosure on paper. However, the entire bundle of rule files it points to is missing, so the skill delivers no actual domain knowledge and no actionable guidance. Shipping the rules/ directory (or inlining a minimal quick-start) is the critical fix.

Suggestions

Ship the rules/ directory with all referenced files, or remove/repair the links — 34 dangling references currently make the skill unusable.

Add a minimal inline quick-start (one small code sample of a Composition with an animated component) so the skill provides some standalone value before file loading.

Fold the four topical sections (Captions, FFmpeg, Audio visualization, Sound effects) into the single rule list or give them trigger conditions, since they currently duplicate the list's format with less context.

DimensionReasoningScore

Conciseness

The body is a lean routing index (one line per topic, e.g. 'load the [./rules/subtitles.md](./rules/subtitles.md) file for more information') with no explanation of concepts Claude already knows. Minor trimmable filler remains ('to obtain the domain-specific knowledge', the repeated 'for more information'), matching anchor 4 rather than the every-token-earns-its-place bar of 5.

4 / 5

Actionability

The body contains no code, commands, or inline examples — its only guidance is 'load file X', and all 34 referenced rules/*.md files are absent from the bundle, so the pointers lead nowhere. This is anchor 2 (high-level hints missing the specific steps to execute); not 1 because the pointers do give concrete file-to-topic routing instructions.

2 / 5

Workflow Clarity

As a simple routing skill the single action (match task to rule file, then read it) is unambiguous, but the workflow dead-ends because none of the referenced rule files exist. It sits between anchor 2 and 4: clear sequencing of intent, but the executable step cannot be carried out.

3 / 5

Progressive Disclosure

The structure is well-signaled (descriptive one-line entries, references one level deep), but scored against the actual bundle every referenced path (./rules/subtitles.md, ./rules/ffmpeg.md, and all 30 files under 'How to use') is missing, leaving navigation broken. The good organization cannot lift it above 2 when no reference resolves.

2 / 5

Total

11

/

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 identifies a distinctive, well-scoped niche (Remotion video creation in React) but says almost nothing about what the skill actually does or when to invoke it. It reads as a topic label rather than a capability description with trigger guidance.

Suggestions

List 2-3 concrete capabilities in the description, e.g. 'Render React components to video, build animations with interpolate/spring, sequence scenes with <Sequence>' instead of the generic 'Best practices for'.

Add an explicit trigger clause, e.g. 'Use when working with Remotion, rendering React components to video, or creating programmatic/animated video compositions.'

Include natural user phrasings and synonyms such as 'video rendering', 'animation', and 'composition' to broaden trigger-term coverage.

DimensionReasoningScore

Specificity

The description names a specific domain ("Best practices for Remotion - Video creation in React") but lists no concrete actions or capabilities. It matches anchor 2 ('names the domain but actions are minimal or generic') rather than 1 because a specific technology is named, and not 3 because no action verbs beyond 'best practices' appear.

2 / 5

Completeness

It states a 'what' (best practices for Remotion video creation in React) but has no 'when to use' clause at all, which caps completeness at 3 per the judging guidelines. It is above anchor 2 because the 'what' names a clear niche rather than being vague, but below 4 because 'when' is entirely absent.

3 / 5

Trigger Term Quality

"Remotion", "video", and "React" are relevant keywords and "Remotion" is the natural user trigger, but common variations are missing (render video, animation, composition, programmatic video). This fits anchor 3 ('some relevant keywords but missing common variations or synonyms'), not 4 which expects fuller coverage.

3 / 5

Distinctiveness Conflict Risk

"Remotion" is a unique named framework, giving a clear niche with only minor overlap risk against generic React or video skills. It falls short of anchor 5 because the description includes no explicit trigger phrases that lock in the distinct trigger surface.

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

Warning

Total

14

/

16

Passed

Repository

calesthio/OpenMontage

Path

.agents/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.