remotion-create

Create a new Remotion video

Quality

63%

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 ./packages/skills/skills/remotion-create/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 efficiently written, executable walkthrough of the create-video workflow with concrete commands and sensible guardrails around folder selection and rendering. Its main weakness is bundle integrity: two referenced guidance files are missing from the skill directory, which undermines both navigation and the otherwise strong actionability.

Suggestions

Add the missing bundle files (video-layout.md and tailwind.md, conventionally under references/) or correct their paths, since the body currently links to files that do not exist in the skill.

Add a lightweight post-scaffold validation checkpoint (e.g. confirm package.json exists before proceeding to design) to close the workflow's validation gap.

Either reference assets/remotion-icon.svg where relevant (e.g. as the Studio favicon or a project asset) or remove it, so the bundle contains no orphaned files.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes Claude's competence throughout: no explanation of what Remotion is, why the blank template is used, or how npm works — every line is an instruction ("Inspect the current folder, including hidden files, before choosing where to scaffold", "Only render if the user explicitly asks for it"). It matches anchor 5 ("Lean and efficient; assumes Claude's competence; every token earns its place"); only trivia like "The video creation process has finished." is arguably trimmable, which is not enough to drop to anchor 4.	5 / 5
Actionability	Commands are copy-paste ready and complete ("npx create-video@latest --yes --blank --no-tailwind .", "npm i", "npx remotion studio --no-open", "npx remotion render") with concrete conditional branching for empty vs. non-empty folders. It falls short of anchor 5 because two referenced guidance files — [Video Layout Rules](video-layout.md) and [tailwind.md](tailwind.md) — do not exist in the bundle, so following those links fails, and "Keep the scaffold and add React Markup" delegates without a fallback.	4 / 5
Workflow Clarity	The sequence is clear and gated: scaffold (with a pre-flight folder inspection checkpoint and skip-if-exists guard) → design → preview → render-only-on-explicit-request. It is not anchor 5 because there are no post-action validation steps or feedback loops (e.g. confirming the scaffold succeeded by checking for package.json, or verifying the studio URL is reachable before reporting it); this keeps it at "most checkpoints present; minor validation gaps".	4 / 5
Progressive Disclosure	The overview/delegation pattern is well-signaled (one-level references to sibling skills for markup, interactivity, rendering, and best practices), but scoring against the actual bundle shows the two in-skill references [Video Layout Rules](video-layout.md) and [tailwind.md](tailwind.md) have no corresponding files — there is no references/ directory at all, and the only bundle asset (assets/remotion-icon.svg) is never referenced. That broken navigation leaves it at "some structure but could be better organized" rather than anchor 4.	3 / 5
	Total	16 / 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 is appropriately terse and unambiguous about the single core task, but it under-sells the skill and gives Claude no routing signal for when to invoke it. Adding a 'Use when...' clause and one or two more concrete actions (scaffold, design, render) would raise both completeness and specificity.

Suggestions

Add a 'Use when...' trigger clause, e.g. "Use when the user asks to create, scaffold, or start a new Remotion video or animation project."

Enumerate 1-2 more concrete capabilities to lift specificity above the single generic action, e.g. "Scaffolds a Remotion project, sets up compositions, and starts the Studio preview."

Include natural trigger synonyms such as "animation", "programmatic video", or "React video" so the skill fires on phrasings that omit the word "Remotion".

Dimension	Reasoning	Score
Specificity	The description "Create a new Remotion video" names the domain (Remotion video) but contains only a single generic action verb ("Create"), matching anchor 2 ("Names the domain but actions are minimal or generic"). It is not a 3 because it lacks the 1-2 additional concrete actions the anchor-3 example shows (e.g. scaffolding a project, designing compositions, rendering); the skill actually performs all of these but none is stated.	2 / 5
Completeness	The "what" is clear ("Create a new Remotion video") but there is no "Use when..." clause or equivalent trigger guidance anywhere in the description, which per the judging guidelines caps completeness at 3. It fits anchor 3 ("clear 'what' but 'when' is missing or only weakly implied") exactly; it is not a 4 because no 'when' is present even implicitly.	3 / 5
Trigger Term Quality	"Remotion" and "video" are the relevant keywords, on par with the anchor-3 example "Works with PDF files" — some relevant keywords but missing common variations. It is not a 4 because natural synonyms a user would say — "animation", "programmatic video", "React video", "motion graphics" — are absent, leaving only two trigger terms.	3 / 5
Distinctiveness Conflict Risk	"Remotion video" carves a clear niche with a distinct framework name, but the bare word "video" creates minor overlap risk with the sibling skills it links to (remotion-render, remotion-markup, remotion-best-practices) and with generic video-editing skills. This matches anchor 4 ("Mostly distinct; minor overlap risk with closely related skills"); it is not a 5 because the description gives no trigger phrasing to disambiguate creation from rendering or editing of existing videos.	4 / 5
	Total	12 / 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: 2 missing, 6 suspicious	Warning

	Total	14 / 16 Passed

Repository: remotion-dev/remotion
Path: packages/skills/skills/remotion-create/SKILL.md
Commit: 6f4e0d5

Reviewed: 5 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.