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

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/AI-Agents-Safe-Coding-Skills-claude/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

67%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 concise, well-organized index pointing to per-topic rule files — good design in principle. However, the entire referenced bundle is absent, so the progressive-disclosure structure does not actually resolve, which is its dominant weakness.

Suggestions

Ship the missing rules/*.md bundle files (all 27 referenced paths under rules/ are absent), or remove links to files that are not included.

Add brief guidance on which rule file(s) to consult for common task types (e.g., 'For a new composition start with compositions.md and sequencing.md') so the index doubles as a routing guide.

Verify each link path resolves to a real file in the bundle so navigation is not broken at runtime.

DimensionReasoningScore

Conciseness

The body is lean — two short sections plus a one-line-per-rule link list with brief topic descriptions, no padded explanations of concepts Claude already knows — fitting 'Efficient; minor instances of over-explanation that could be trimmed' (the 'When to Use' sentence is slightly redundant).

4 / 5

Actionability

It gives concrete, specific navigation ('Read individual rule files' plus 27 named links each annotated with its topic), which is actionable guidance with minor gaps, though no inline code examples are provided.

4 / 5

Workflow Clarity

As a simple navigation skill the single action (read the relevant rule file for your Remotion task) is clear and unambiguous with a descriptive index, but the body does not guide selection among the 27 files for a given task, leaving a minor gap.

4 / 5

Progressive Disclosure

The overview is well-designed with one-level-deep, clearly signaled references, but every one of the 27 referenced rules/*.md files is missing from the bundle, so the actual navigation is broken — scored against the real bundle structure per the rubric guideline.

2 / 5

Total

14

/

20

Passed

Description

48%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 correctly names a distinct domain but is terse: it states a vague 'what' and omits any explicit 'when to use' trigger guidance, which caps completeness. Trigger-term coverage is adequate but lacks synonyms or extensions.

Suggestions

Add an explicit 'Use when...' clause listing concrete triggers (e.g., 'Use when writing or debugging Remotion code — compositions, sequences, animations, audio, or rendering video').

Replace the generic 'Best practices' framing with 2-3 concrete capabilities (e.g., 'Author compositions, sequence animations, sync audio, and render video with Remotion in React').

Include natural variations users might say, such as 'Remotion', 'React video', '.tsx composition', 'programmatic video', and 'render'.

DimensionReasoningScore

Specificity

The description names the domain ('Best practices for Remotion - Video creation in React') but lists no concrete actions — 'best practices' is generic rather than a specific capability, matching the 'Names the domain but actions are minimal or generic' anchor.

2 / 5

Completeness

A clear 'what' is present (best practices for Remotion video creation) but there is no 'Use when...' clause or equivalent trigger guidance, which per the rubric caps completeness at 3.

3 / 5

Trigger Term Quality

It surfaces natural terms ('Remotion', 'video', 'React') a user would say, but misses common variations, synonyms, and file extensions, fitting 'Some relevant keywords but missing common variations or synonyms.'

3 / 5

Distinctiveness Conflict Risk

Remotion is a distinct niche with its own trigger term and minimal overlap with other skills, fitting 'Mostly distinct; minor overlap risk'; not a 5 because the thin description does not fully sharpen the trigger.

4 / 5

Total

12

/

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.

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

relative_links

Relative link issues: 28 missing

Warning

Total

14

/

16

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.