CtrlK
BlogDocsLog inGet started
Tessl Logo

remotion-best-practices

Best practices for Remotion - Video creation in React

44

Quality

46%

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 ./plugins/AI-Agents-Safe-Coding-Skills/skills/remotion-best-practices/SKILL.md

The canonical home for this skill is remotion-best-practices in administrakt0r/AI-Agents-Safe-Coding-Skills

SKILL.md
Quality
Evals
Security

Quality

Content

53%Scale 1-5

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

This skill functions as a well-organized index/table of contents for Remotion best practices, with clear one-level-deep references to topic-specific rule files. Its main weakness is the complete absence of any actionable content in the body itself—no code examples, no quick-start guidance, no common patterns. It relies entirely on external files for substance, making the SKILL.md alone insufficient for Claude to act on without reading additional files.

Suggestions

Add a brief 'Quick Start' section with a minimal executable Remotion example (e.g., a simple composition with an animation) so Claude has immediately actionable guidance without needing to read sub-files.

Group the rule file links into logical categories (e.g., 'Media Assets', 'Animation & Timing', 'Captions & Text', 'Advanced') to improve navigability of the 28+ links.

Include 2-3 common workflow patterns inline (e.g., 'To add captions to a video: 1. Transcribe audio → 2. Import captions → 3. Display captions') with references to the relevant rule files at each step.

DimensionReasoningScore

Conciseness

The content is fairly lean—it's essentially a brief usage note followed by a well-organized index of rule files. The 'When to Use' section is slightly unnecessary (Claude can infer when to use Remotion skills), but overall it's efficient and doesn't over-explain.

4 / 5

Actionability

The SKILL.md itself provides no concrete code, commands, or executable guidance. It is purely a directory of links to other files. Without the bundle files to verify those references contain actionable content, the skill body alone offers only high-level pointers with no directly usable instructions.

2 / 5

Workflow Clarity

There is no multi-step workflow described—just a flat list of topics. For a reference/index skill this is acceptable, but there's no guidance on how to combine these rules, no sequencing of steps for common tasks, and no validation checkpoints. The single instruction ('read individual rule files') is unambiguous but minimal.

3 / 5

Progressive Disclosure

The skill is structured as a clear overview with one-level-deep references to individual rule files, each with a descriptive summary. This is good progressive disclosure. However, without bundle files to verify the referenced paths exist and contain appropriate content, and without any grouping or categorization of the 28+ links (e.g., by topic area), it falls slightly short of a 5.

4 / 5

Total

13

/

20

Passed

Description

39%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 specific technology (Remotion) which helps with distinctiveness, but it is otherwise too vague. It lacks concrete actions, provides no 'when to use' guidance, and 'best practices' is a generic framing that doesn't help Claude understand what this skill actually enables.

Suggestions

Replace 'Best practices' with specific capabilities, e.g., 'Guides creation of video compositions, animations, and rendering pipelines using Remotion in React.'

Add a 'Use when...' clause with trigger terms like 'Use when the user asks about Remotion, React video rendering, programmatic video creation, or animation compositions.'

Include additional natural keywords and synonyms such as 'animation', 'render', 'composition', 'programmatic video', and 'motion graphics' to improve trigger term coverage.

DimensionReasoningScore

Specificity

Names the domain ('Remotion - Video creation in React') but provides no concrete actions. 'Best practices' is vague and doesn't describe what the skill actually does (e.g., create compositions, render videos, configure timelines).

2 / 5

Completeness

The 'what' is vaguely stated as 'best practices' without specifying concrete capabilities. There is no 'when' clause or trigger guidance at all, which per the rubric should cap completeness at 3, and the weak 'what' brings it down further.

2 / 5

Trigger Term Quality

Includes 'Remotion', 'Video creation', and 'React' which are relevant keywords a user might mention. However, it misses natural variations like 'animation', 'render video', 'video editing', 'composition', or file-related terms.

3 / 5

Distinctiveness Conflict Risk

The mention of 'Remotion' is a specific technology name that creates a fairly distinct niche. However, 'Video creation in React' could potentially overlap with other React media or video-related skills. The specificity of 'Remotion' reduces conflict risk significantly.

4 / 5

Total

11

/

20

Passed

Validation

90%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation10 / 11 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

10

/

11

Passed

Repository
administrakt0r/AI-Agents-Safe-Coding-Skills
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.