remotion-create

Creating a new Remotion video

Quality

68%

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

80%

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

The skill body is concise and actionable with copy-paste-ready commands and a clear section sequence. Its main weaknesses are missing verification checkpoints in the workflow and two broken local file references that undermine the progressive-disclosure structure.

Suggestions

Add an explicit verification checkpoint after scaffolding, e.g. confirm `npm i` completed without errors and that the studio printed a server URL before proceeding.

Fix or remove the broken local references (video-layout.md and tailwind.md) — either create the referenced files or point to the correct existing paths.

Clarify the design step with a minimal concrete example of adding React markup so the workflow does not rely solely on an external reference.

Dimension	Reasoning	Score
Conciseness	The body is lean and efficient with short scaffold/preview command blocks and no padding or explanation of concepts Claude already knows (e.g. what Remotion, React, or Node are), matching the anchor for lean content where every token earns its place.	3 / 3
Actionability	It provides copy-paste-ready, fully executable commands ("npx create-video@latest --yes --blank --no-tailwind my-video", "npm i", "npx remotion studio --no-open") with a concrete example, matching the anchor for fully executable guidance.	3 / 3
Workflow Clarity	Steps are sequenced (Scaffold, Design, Interactivity, Tailwind, Preview, Follow-up) with one conditional ("If a project already exists, skip this"), but there are no explicit verification checkpoints such as confirming the install succeeded or the studio actually started, matching the anchor with a sequence present but checkpoints missing or implicit.	2 / 3
Progressive Disclosure	The body is under 50 lines, well-organized into sections, and uses one-level-deep inline references, but two local references ([Video Layout Rules](video-layout.md) and [tailwind.md](tailwind.md)) point to files that do not exist in the skill directory and no references/, scripts/, or assets/ bundles are present, a structural defect that keeps it from the top anchor.	2 / 3
	Total	10 / 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 correctly identifies a distinct niche (Remotion) but is thin, naming only a single action and omitting any "Use when..." trigger guidance. It reads more like a title than a capability description with explicit trigger terms.

Suggestions

Expand to name multiple concrete actions, e.g. "Scaffold a Remotion project, design compositions with React markup, and start the preview studio."

Add an explicit trigger clause such as "Use when the user wants to create a new Remotion video or start a Remotion project."

Include natural trigger variations like "Remotion", "Remotion project", "composition", and "Remotion Studio" to improve trigger-term coverage.

Dimension	Reasoning	Score
Specificity	The description "Creating a new Remotion video" names a concrete domain (Remotion video) and one action (creating), matching the anchor that names a domain and some actions without being comprehensive; it is not vague enough for a 1 but lacks multiple listed actions needed for a 3.	2 / 3
Completeness	It weakly answers what the skill does ("Creating a new Remotion video") but provides no "Use when..." trigger, and per the guidelines a missing explicit trigger clause caps completeness at 2.	2 / 3
Trigger Term Quality	"Remotion" is a natural keyword a user would say, but the description omits common variations like "Remotion project", "composition", or "render", matching the anchor with some relevant keywords but missing common variations.	2 / 3
Distinctiveness Conflict Risk	"Remotion video" is a clear, named niche with distinct triggers that would not realistically conflict with other skills, matching the anchor for a clear niche unlikely to trigger the wrong skill.	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
metadata_version	'metadata.version' is missing	Warning
relative_links	Relative link issues: 2 missing, 4 suspicious	Warning

	Total	14 / 16 Passed

Repository: remotion-dev/remotion
Path: packages/skills/skills/remotion-create/SKILL.md
Commit: 06f2fd7

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