CtrlK
BlogDocsLog inGet started
Tessl Logo

remotion-best-practices

Best practices for Remotion

48

Quality

53%

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

Quality

Content

100%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is an exemplary routing/index SKILL.md: concise, actionable with explicit sub-skill paths, unambiguous routing, and clean one-level-deep progressive disclosure. No bundle files are present locally, so progressive disclosure is scored against the well-organized reference structure in the body.

DimensionReasoningScore

Conciseness

The body is lean: each section is one to three lines, explains no concepts Claude already knows, and every token earns its place, matching the 'lean and efficient' anchor.

3 / 3

Actionability

Each route gives copy-paste-ready load instructions with explicit relative paths (e.g. remotion-markup/SKILL.md) and the Maps section enumerates concrete triggers (Mapbox, MapLibre, GeoJSON), providing fully executable guidance for a hub skill.

3 / 3

Workflow Clarity

This is a single-purpose routing skill whose single action (load the matching sub-skill) is unambiguous per topic, and there are no destructive or batch operations requiring validation, so it qualifies for score 3 under the simple-skill note.

3 / 3

Progressive Disclosure

It is a textbook hub overview with clearly signaled one-level-deep references to eleven sub-skills, organized by topic with easy navigation, matching the 'clear overview with well-signaled one-level-deep references' anchor.

3 / 3

Total

12

/

12

Passed

Description

7%

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 a bare domain label with no concrete capabilities and no usage triggers, scoring at the floor on specificity, triggers, and completeness. It is distinguishable only by virtue of the Remotion product name.

Suggestions

Add concrete actions, e.g. 'Compose, animate, and render videos with Remotion'.

Append a 'Use when...' trigger clause listing natural terms users say: video, rendering, composition, animation, <Player>, Lambda rendering.

Avoid the generic 'Best practices' phrasing in favor of capability + trigger phrasing so it cannot be confused with a general React skill.

DimensionReasoningScore

Specificity

The description 'Best practices for Remotion' names only the domain and no concrete actions, matching the 'Vague or no actions' anchor like 'Helps with documents'; it does not reach score 2 which requires naming some actions.

1 / 3

Completeness

It states neither concrete 'what' actions nor any 'Use when...' trigger guidance, so both halves are weak and it cannot reach score 2.

1 / 3

Trigger Term Quality

The only keyword is 'Remotion' with no natural task-oriented variations a user would say (e.g. video, rendering, composition, animation), matching the overly-generic single-term anchor.

1 / 3

Distinctiveness Conflict Risk

'Remotion' is a fairly distinct product name so overlap risk is limited, but the description offers no distinguishing trigger context, fitting the 'somewhat specific but could still overlap' anchor rather than the clearly-niche score 3.

2 / 3

Total

5

/

12

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.

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

relative_links

Relative link issues: 10 missing

Warning

Total

14

/

16

Passed

Repository
remotion-dev/remotion
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.