CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

remotion-best-practices

Guides implementation of Remotion video compositions, animations, transitions, audio/video embedding, captions, and rendering in React. Covers frame-based timing with interpolate() and useCurrentFrame(), media trimming and looping, scene sequencing, 3D content, chart animations, text effects, and Tailwind integration. Use when the user mentions Remotion, programmatic video, React video, video composition, video rendering, frame animation, MP4 export, or works with .remotion files.

Quality

84%

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

SKILL.md
Quality
Evals
Security

Quality

Content

65%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-written overview with an exemplary quick-start example and correctly framed critical rules, but it functions purely as an index to 27 rule files that are absent from the bundle. As shipped, the skill delivers only the minimal composition example while promising detailed guidance it cannot provide. Shipping the rules/ files (or inlining the most essential patterns) would lift the workflow, actionability, and disclosure scores substantially.

Suggestions

Ship the rules/*.md files referenced by the 'How to use' index — all 27 links are currently dangling, which makes the skill's core workflow unexecutable and its progressive-disclosure structure nominal.

Add a short decision guide (e.g., 'task type → rule file' mapping) so navigating the 27-file index doesn't rely solely on one-line labels.

Remove or condense the 'When to use' section, which duplicates the frontmatter description's trigger list almost verbatim.

DimensionReasoningScore

Conciseness

The body is lean — a compact quick-start code block, one line of critical rules, and a tight 27-entry index — but the 'When to use' section ('creating compositions, animating scenes, embedding audio/video, adding captions...') restates the frontmatter description's trigger list, which is trimmable duplication. Not 5 because not every token earns its place; not 3 because there is no padding or explanation of concepts Claude already knows.

4 / 5

Actionability

The quick start is complete, executable copy-paste code (useCurrentFrame, interpolate, Composition with real props) and 'Always use useCurrentFrame()... Never use CSS transitions' is a concrete do/don't. Not 5 because everything beyond the basic case is delegated to the rules/*.md files, none of which exist in the bundle, so actionable guidance for audio, captions, 3D, etc. is only promised, not delivered.

4 / 5

Workflow Clarity

The usage pattern is present ('Read individual rule files for detailed explanations and code examples' after the quick start) but the primary instructed step cannot be executed — the bundle contains no rules/ directory, so all 27 links are dead ends. Not 4 because this is more than a minor gap: following the workflow as written fails at its first step, and there is no guidance for choosing among the 27 files beyond their one-line labels.

3 / 5

Progressive Disclosure

The in-text structure mirrors a top-anchor pattern — an overview with well-signaled, one-level-deep references ('[rules/animations.md](rules/animations.md) - Fundamental animation skills...') — but scored against the actual bundle structure, the split is unrealized: none of the 27 referenced rule files exist (no rules/, references/, scripts/, or assets/ directories). Not 4/5 because 'content appropriately split' and 'easy navigation' fail when every reference target is missing; not 2 because references are clearly labeled, not buried, and nothing that belongs in separate files is inlined.

3 / 5

Total

14

/

20

Passed

Description

100%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 a model example: third-person, dense with concrete named capabilities, and closed by an explicit trigger clause with synonyms and file extensions. Both 'what' and 'when' are answered clearly and specifically. No changes needed.

DimensionReasoningScore

Specificity

It lists many concrete actions with named APIs: 'video compositions, animations, transitions, audio/video embedding, captions, and rendering', plus 'frame-based timing with interpolate() and useCurrentFrame(), media trimming and looping, scene sequencing, 3D content, chart animations, text effects, and Tailwind integration' — comprehensive coverage in third-person voice. Not 4 because there are no meaningful gaps in the capability enumeration.

5 / 5

Completeness

It explicitly answers 'what' ('Guides implementation of Remotion video compositions... in React') and 'when' with an explicit 'Use when...' clause containing concrete trigger phrases. Not 4 because the 'when' is already fully explicit and specific — nothing is merely implied.

5 / 5

Trigger Term Quality

'Use when the user mentions Remotion, programmatic video, React video, video composition, video rendering, frame animation, MP4 export, or works with .remotion files' covers synonyms, natural phrasings, and a file extension — the terms a user would actually say. Not 4 because common variations are comprehensively represented.

5 / 5

Distinctiveness Conflict Risk

'Remotion' names a specific framework niche and the triggers (programmatic video, React video, MP4 export, .remotion files) are unlikely to fire for unrelated skills; generic terms like 'animation' are consistently scoped to the Remotion/React video context. Not 4 because overlap risk with other skills is minimal.

5 / 5

Total

20

/

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

Warning

Total

14

/

16

Passed

Repository

bap-jorkim/agent-skills-fork-feb-25

Path

skills/remotion/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.