remotion-best-practices

Best practices for Remotion - Video creation in React

Quality

59%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/design/capabilities/remotion-best-practices/SKILL.md

Quality

Content

78%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 an exemplary lean routing index — concise, well-organized, and clearly dispatching to per-topic rule files — with strong conciseness and workflow clarity. The main weakness is that none of the referenced rules/*.md files exist in the provided bundle, so the progressive-disclosure structure is asserted but unverifiable.

Suggestions

Include the referenced rules/*.md files (or place them under ./references/) so the body's links resolve and progressive disclosure is real rather than aspirational.

Add a one-line note clarifying the relationship between the inline 'Captions/FFmpeg/Audio visualization' sections and the rule-file list to avoid perceived duplication.

Optionally surface 1–2 inline code snippets for the highest-frequency tasks (e.g. a minimal Composition + Sequence) so actionability reaches fully executable without leaving SKILL.md.

Dimension	Reasoning	Score
Conciseness	The body is lean: short section intros like 'When dealing with captions or subtitles, load the ./rules/subtitles.md file for more information' followed by a compact annotated link list, with zero explanation of what Remotion/React/FFmpeg are; every token earns its place.	5 / 5
Actionability	It gives concrete, executable routing — named rule files with one-line descriptions of exactly what each covers (e.g. 'trimming, volume, speed, looping, pitch' for videos.md) — but the inline body itself contains no copy-paste code or commands, relying on the referenced files for executable detail.	4 / 5
Workflow Clarity	The dispatch pattern is clear: a 'When to use' gate plus per-topic sections each telling Claude which rule file to load, giving an unambiguous single-action routing flow; it stops short of 5 because there are no explicit validation checkpoints, though none are required for this non-destructive reference skill.	4 / 5
Progressive Disclosure	References are one level deep and well-listed, but the rule files (rules/*.md) referenced in the body are not present in the bundle (no ./references, ./scripts, ./assets, or ./rules directory exists), so navigation signals point to missing targets and the actual bundle structure cannot confirm the split; this caps the score at 'structure present but references not verifiable'.	3 / 5
	Total	16 / 20 Passed

Description

40%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 identifies a specific niche (Remotion for React video creation) but is terse and lacks concrete actions and any explicit 'Use when...' trigger guidance, which caps completeness. It is distinctive yet under-specified for routing.

Suggestions

Add 2–3 concrete capabilities (e.g. 'sequences, captions, audio visualization, rendering') to the description so specificity rises above the generic 'video creation'.

Append an explicit 'Use when working with Remotion code, rendering React videos, or adding captions/animations/transitions' clause to satisfy the 'when' half of completeness.

Include natural synonyms a user might say (subtitles, transitions, FFmpeg, .tsx video) to broaden trigger-term coverage.

Dimension	Reasoning	Score
Specificity	The phrase 'Best practices for Remotion - Video creation in React' names the domain but the only action verb is the generic 'creation', with no concrete actions like rendering, sequencing, captions, or interpolation; it sits at 'names the domain but actions are minimal or generic'.	2 / 5
Completeness	There is a vague 'what' (best practices / video creation) but no 'when' / 'Use when...' clause, so per the rubric a missing explicit trigger guidance caps completeness low; it falls just above score 1 because a domain is at least named.	2 / 5
Trigger Term Quality	It surfaces the natural product keyword 'Remotion' and the phrase 'Video creation in React', which a user might say, but it omits common variations users actually utter (subtitles/captions, animations, FFmpeg, audio visualization) and any file extensions.	3 / 5
Distinctiveness Conflict Risk	'Remotion' is a specific, recognizable product niche and 'Video creation in React' further scopes it, so overlap risk with other skills is low; the only thing keeping it below 5 is the absence of explicit trigger phrasing that fully disambiguates use cases.	4 / 5
	Total	11 / 20 Passed

Validation

87%

Warnings & errors only

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

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning
relative_links	Relative link issues: 33 missing	Warning

	Total	14 / 16 Passed

Repository: gooseworks-ai/goose-skills
Path: skills/design/capabilities/remotion-best-practices/SKILL.md
Commit: 2523432

Reviewed: 7 days ago

Table of Contents

Discovery Implementation Validation

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.