CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

remotion-create

Create a new Remotion video

Quality

73%

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 ./packages/skills/skills/remotion-create/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

82%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.

A lean, well-sequenced routing skill: exact scaffold commands for both folder states, an install error-recovery fallback, and clearly signaled delegation to specialized sibling skills. The main gaps are the missing command for opening Remotion Studio and two referenced local files that do not exist in the bundle.

Suggestions

Include the command for starting the preview (e.g., npx remotion studio) so the "Open the preview" step is executable without consulting the remotion-studio skill.

Ship video-layout.md and tailwind.md in the bundle (or inline their essentials), since both are referenced but currently missing.

Add an explicit post-scaffold validation checkpoint, e.g. confirm the blank composition renders in Studio before writing markup.

DimensionReasoningScore

Conciseness

The body is lean and directive throughout — "Keep the scaffold and add React Markup", "If it logs an error while installing them, run `npm i` in the project" — with zero concept explanations and every section at 1-4 lines. Nothing explains what Remotion, Node.js, or React are; every token earns its place, matching the 5 anchor rather than the 4 anchor's 'minor instances of over-explanation'.

5 / 5

Actionability

Both scaffold paths give copy-paste-ready commands ("npx create-video@latest --yes --blank --no-tailwind ." and the subfolder variant with cd) plus an npm i fallback, and the routing conditions (empty vs non-empty folder, timeline, multi-scene) are concrete. It falls short of 5 because the critical Studio step says only "open Remotion Studio in the browser" with no command, deferring mid-workflow to another skill.

4 / 5

Workflow Clarity

The sequence (scaffold -> open preview -> design -> branch by video type -> follow-up) is clearly ordered, with a pre-flight check ("Inspect the current folder, including hidden files, before choosing where to scaffold") and an install error-recovery loop. It is not a 5 because there is no explicit validation that the scaffolded project actually runs before design begins — only the implicit "As soon as the project can run".

4 / 5

Progressive Disclosure

The body is a clean overview that routes to clearly signaled, one-level-deep references with descriptive labels ("[Video Layout Rules](video-layout.md)", "[Compositions and stills](../remotion-markup/compositions.md)", "[Multi-scene videos](../remotion-markup/multi-scene-video.md)"). It is not a 5 because two locally referenced files (video-layout.md and tailwind.md) are absent from the actual bundle, which contains only SKILL.md and assets/remotion-icon.svg, leaving those links dangling.

4 / 5

Total

17

/

20

Passed

Description

53%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 names a clear, distinctive capability but is minimal: it states a single action with no trigger guidance and no synonyms, leaving completeness capped and trigger coverage thin. Rewriting it in a what-plus-when format with natural trigger phrases would lift most dimensions substantially.

Suggestions

Add an explicit trigger clause, e.g. "Use when the user asks to create a new Remotion video, start a Remotion project, or scaffold a video composition from scratch."

Enumerate the concrete capabilities: scaffolding a project with create-video, registering compositions, and opening the Remotion Studio preview.

Include natural trigger variations such as "Remotion project", "video animation", or "React video" to broaden keyword coverage and reduce misrouting to sibling Remotion skills.

DimensionReasoningScore

Specificity

"Create a new Remotion video" names the domain ("Remotion video") and exactly one concrete action ("Create"), matching the anchor 'Names domain and 1-2 concrete actions, but not comprehensive'. It is not a 2 because 'Create' is a real, specific action rather than a generic verb like 'Processes', and not a 4 because no further actions (scaffolding a project, registering compositions, opening a preview) are listed.

3 / 5

Completeness

It answers 'what' clearly ("Create a new Remotion video") but contains no 'Use when...' clause or any equivalent trigger guidance, capping completeness at 3 per the judging guidelines. A 4 would require both what and when to be present, even imperfectly.

3 / 5

Trigger Term Quality

The phrase "Create a new Remotion video" is itself a natural thing a user would say, but it is the only trigger phrase present — common variations like 'Remotion project', 'video animation', 'motion graphics', or 'React video' are missing. This matches 'Some relevant keywords but missing common variations or synonyms' rather than the good coverage of a 4.

3 / 5

Distinctiveness Conflict Risk

"Remotion" carves out a clear niche and "Create a new" distinguishes it from closely related sibling skills (remotion-best-practices, remotion-markup, remotion-studio) that this skill's own body references, fitting 'Mostly distinct; minor overlap risk with closely related skills'. It is not a 5 because a request like 'make me a Remotion video' could plausibly route to the best-practices sibling instead.

4 / 5

Total

13

/

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.

Validation — 14 / 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: 2 missing, 8 suspicious

Warning

Total

14

/

16

Passed

Repository

remotion-dev/remotion

Path

packages/skills/skills/remotion-create/SKILL.md

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.