CtrlK
BlogDocsLog inGet started
Tessl Logo

remotion-best-practices

Best practices for Remotion - Video creation in React

49

Quality

55%

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

67%

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 an admirably lean, well-organized index that practices progressive disclosure by design. Its weakness is that the referenced rule files are not present in the bundle, so the disclosure chain is broken, and the body itself offers no concrete code or examples.

Suggestions

Ship the referenced rules/ files (e.g., rules/animations.md, rules/timing.md) so the one-level-deep references resolve; without them progressive disclosure is unverified.

Add a short inline quick-start snippet (e.g., a minimal Composition + interpolate example) so the body is actionable even before reading rule files.

For caption/subtitle work specifically, inline one concrete pointer beyond the subtitles.md link (e.g., the relevant hook name) to lift actionability.

DimensionReasoningScore

Conciseness

The body is extremely lean: a short "When to use" sentence and a flat list of one-line rule links, with no padding or explanation of concepts Claude already knows.

3 / 3

Actionability

Each rule entry gives a one-line description and a link, which is navigable guidance, but the body itself provides no executable code, commands, or concrete examples — action lives entirely behind the referenced files.

2 / 3

Workflow Clarity

It gives a clear single instruction ("Read individual rule files for detailed explanations") and a per-topic index, but there is no multi-step sequence or validation checkpoint; this simple-skill structure avoids score 1 but lacks explicit sequencing.

2 / 3

Progressive Disclosure

The body correctly acts as an overview pointing to one-level-deep rule files, but no rules/ bundle directory is present in the skill bundle, so the referenced files do not exist; structure is well-signaled but the underlying references cannot be verified, capping the score.

2 / 3

Total

9

/

12

Passed

Description

42%

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 clear, distinct niche (Remotion video in React) but is too generic about capabilities and lacks any explicit "Use when..." trigger guidance. Adding concrete actions and trigger phrases would substantially raise its score.

Suggestions

Add a "Use when..." clause naming trigger phrases (e.g., "Use when working with Remotion code, rendering React videos, or building animations and compositions").

Replace the generic "Best practices" framing with concrete capabilities (e.g., "Composes, animates, and renders videos in React using Remotion").

Mirror natural user terms like "render video", "animation", and "captions" that already appear as tags so the description covers common variations.

DimensionReasoningScore

Specificity

The phrase "Best practices for Remotion - Video creation in React" names the domain (Remotion, video, React) but describes no concrete actions or capabilities, only a generic "Best practices" framing.

2 / 3

Completeness

It states what the skill covers ("Best practices for Remotion") but entirely lacks any "Use when..." or equivalent explicit trigger guidance, so the "when" half is missing and completeness is capped at 2; with only a vague "what" it sits at the low end.

1 / 3

Trigger Term Quality

It surfaces "Remotion", "video", and "React" which a user may say, but omits common natural variations like "animation", "render video", "captions", or "composition" despite those being tags.

2 / 3

Distinctiveness Conflict Risk

Remotion is a clearly defined niche with distinct triggers unlikely to collide with other skills; the phrase scopes it to "Video creation in React" which is unmistakable.

3 / 3

Total

8

/

12

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.

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