CtrlK
BlogDocsLog inGet started
Tessl Logo

remotion-best-practices

Best practices for Remotion - Video creation in React

52

Quality

58%

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

70%

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 admirably lean, well-organized routing index with a clear navigation workflow, but it is fundamentally undermined because all ~30 referenced ./rules/*.md files are missing, making the progressive-disclosure structure and the concrete guidance it depends on non-functional.

Suggestions

Ship the referenced ./rules/*.md bundle (or whichever rule files exist) so the one-level-deep references actually resolve; a routing index with no targets fails its core purpose.

Remove the duplication between the four highlighted topic sections (Captions, FFmpeg, Audio visualization, Sound effects) and the bottom catalog, or fold the highlights into the catalog to avoid restating 'load the [./rules/X.md] file for more information'.

Add a brief one-line note on how to choose among rules when a task spans multiple concerns, so the routing step is unambiguous for overlapping topics.

DimensionReasoningScore

Conciseness

The body is a lean routing index that assumes Claude's competence, with one-line pointers and a compact catalog of rule files; it avoids explaining concepts Claude already knows and is not padded, fitting the score-3 lean/efficient anchor. It is not score 2 because there is no unnecessary explanation, only minor templated phrasing.

3 / 3

Actionability

It gives concrete routing guidance (specific named file paths plus one-line descriptions of each rule), but the instruction is incomplete because the referenced ./rules/*.md files do not exist, so the 'load this file' direction leads nowhere; this fits the score-2 anchor of concrete-but-incomplete guidance rather than score 1's purely abstract direction.

2 / 3

Workflow Clarity

This is a simple single-purpose routing skill whose workflow (identify the topic, then load the matching rule file) is unambiguous and aided by both highlighted topic sections and a full catalog; per the simple-skills scoring note, a clear single-action workflow scores 3 without needing validation checkpoints.

3 / 3

Progressive Disclosure

Although the body is well-organized as an overview with clearly signaled one-level-deep references, every referenced ./rules/*.md file is absent, so scored against the actual (empty) bundle structure the progressive disclosure is non-functional; it fails the score-3 anchor of appropriately split content and lands at score 1 because there is nothing to progress to.

1 / 3

Total

9

/

12

Passed

Description

47%

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 cleanly identifies a distinct niche (Remotion video creation in React) but is framed as vague 'best practices' with no concrete actions and no 'Use when...' trigger guidance, leaving it terse rather than activation-ready.

Suggestions

Replace the abstract 'Best practices for' framing with concrete actions, e.g. 'Render, animate, sequence, and compose videos in React using Remotion'.

Add an explicit trigger clause such as 'Use when writing or debugging Remotion code, or when the user mentions video rendering, compositions, or Remotion animations'.

Surface common user terms (animation, composition, timeline, rendering) currently only present in the metadata tags.

DimensionReasoningScore

Specificity

The phrase 'Best practices for Remotion - Video creation in React' names the domain but uses the abstract framing 'Best practices' and lists no concrete actions (e.g. render, animate, compose, sequence), matching the score-1 anchor of vague/abstract language rather than the score-2 anchor which requires named actions.

1 / 3

Completeness

It states what the skill covers (best practices for Remotion video creation in React) but includes no 'Use when...' clause or explicit trigger guidance, so per the judging guideline completeness is capped at 2.

2 / 3

Trigger Term Quality

'Remotion', 'Video creation', and 'React' are natural terms a user would say, but the description omits common variations and specifics (animation, composition, rendering) that the metadata tags actually capture, fitting the score-2 anchor of some relevant keywords with missing variations.

2 / 3

Distinctiveness Conflict Risk

'Remotion' is a specific, well-defined niche with distinct triggers that would not plausibly fire for unrelated skills, matching the score-3 anchor of a clear niche unlikely to conflict.

3 / 3

Total

8

/

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

Warning

Total

14

/

16

Passed

Repository
calesthio/OpenMontage
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.