remotion-best-practices

Best practices for Remotion - Video creation in React

Quality

61%

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

65%

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

The skill is a well-organized, token-efficient index pointing to per-topic rule files, but it provides no executable guidance inline and its progressive-disclosure links are broken because the referenced ./rules/ files are absent from the bundle.

Suggestions

Ship the referenced ./rules/*.md files (subtitles, ffmpeg, audio-visualization, and the 27 cataloged rules) so the progressive-disclosure links resolve; broken references undermine the otherwise ideal structure.

Add a short, concrete code snippet or two representative commands in SKILL.md (e.g. a minimal Composition/render example) so the skill is actionable without first loading a rule file.

Add a brief selection workflow — e.g. 'Identify the task type, match it to a rule above, load that file, then apply its example' — to give the single action an explicit, unambiguous sequence.

Dimension	Reasoning	Score
Conciseness	The body is a lean index: each line is navigation (filename plus a one-line topic description) with no padding of concepts Claude already knows, so every token earns its place as discovery aid.	3 / 3
Actionability	It gives specific file references and per-topic descriptions, but contains no executable code, commands, or examples inside SKILL.md — all concrete guidance is deferred to the rule files, matching the 'some concrete guidance but incomplete' anchor.	2 / 3
Workflow Clarity	Sections are organized by topic, but there is no explicit step sequence beyond 'Read individual rule files', and no guidance on how to select or combine the 30+ rules for a given task, so checkpoints/sequence remain implicit.	2 / 3
Progressive Disclosure	The text structure is ideal (clear overview with well-signaled one-level-deep references), but the referenced ./rules/*.md files do not exist in the bundle, so navigation leads nowhere — scoring against the actual bundle drops it below level 3.	2 / 3
	Total	9 / 12 Passed

Description

57%

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, distinctive niche (Remotion video creation in React) but lacks concrete action verbs and any 'Use when...' trigger guidance, leaving it middling on specificity, trigger coverage, and completeness.

Suggestions

Add concrete actions to the description, e.g. 'Render, compose, animate, and sequence programmatic videos in React using Remotion' to reach the specificity level-3 anchor.

Append an explicit trigger clause such as 'Use when working with Remotion compositions, rendering videos, or React-based video/animation tasks' to satisfy the completeness 'what AND when' requirement.

Broaden trigger keywords to cover natural variations users would say (video, render video, animation, React video) rather than relying on the single term 'Remotion'.

Dimension	Reasoning	Score
Specificity	The phrase 'Best practices for Remotion - Video creation in React' names a concrete domain and one broad action ('Video creation'), but does not list multiple specific concrete actions (e.g. render, compose, animate), falling short of the level-3 anchor.	2 / 3
Completeness	It states what the skill provides (Remotion best practices / domain knowledge) but gives no 'Use when...' trigger or equivalent, so the 'when' is missing entirely; the judging guideline caps completeness at 2 for a missing explicit trigger clause.	2 / 3
Trigger Term Quality	'Remotion' and 'video creation' are natural terms a user would say, but coverage is thin and misses common variations like 'video', 'render video', 'animation', or 'React video', matching the 'some relevant keywords but missing common variations' anchor.	2 / 3
Distinctiveness Conflict Risk	Being tied to a specific named library (Remotion) carves out a clear niche that is unlikely to fire for unrelated skills, matching the 'clear niche with distinct triggers; unlikely to conflict' anchor.	3 / 3
	Total	9 / 12 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: 8866b2a

Reviewed: 1 day 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.