CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

remotion-render

Export a Remotion video, still image, or editable OpenTimelineIO timeline

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-render/SKILL.md
SKILL.md
Quality
Evals
Security

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 efficient, highly actionable command reference that packs real gotchas into few tokens, with only a bare `npx remotion still` example and no output-verification guidance as minor weaknesses. Its main structural defect is that both referenced detail files (transparent-videos.md, opentimeline.md) are missing from the bundle, breaking progressive disclosure for those optional paths.

Suggestions

Add the missing transparent-videos.md and opentimeline.md bundle files (or inline/remove the references), since both links currently resolve to nothing.

Show a complete still-render example with composition ID and output path (e.g., `npx remotion still [composition-id] out/still.png`), consistent with the skill's own advice to always pass the composition ID.

Add a brief verification step after rendering, such as confirming the output file exists or checking the command's exit status before reporting success.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence: it never explains what Remotion is, and every section delivers executable commands plus genuinely non-obvious gotchas (interactive picker failure, zero-padded frame filenames, --is-production=false for test renders).

5 / 5

Actionability

Commands are copy-paste ready for the common cases (render with props, license key, multi-frame export), but `npx remotion still` is shown bare with no composition ID or output path, contradicting the skill's own "Always pass the composition ID" rule.

4 / 5

Workflow Clarity

The primary action is unambiguous and failure modes are pre-empted (list composition IDs, list the output folder instead of guessing filenames), but no verification step exists (e.g., confirm the output file was written or check the render exit status) and the batch --frames workflow has no validation checkpoint.

4 / 5

Progressive Disclosure

Sections are well organized with clearly signaled one-level references, but the referenced files ./transparent-videos.md and ./opentimeline.md do not exist in the bundle (only assets/remotion-icon.svg is present), so those navigation links dangle and the split content is unavailable.

3 / 5

Total

16

/

20

Passed

Description

57%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 concise, concrete, and highly distinctive thanks to the Remotion and OpenTimelineIO name-checks, but it completely lacks "when to use" guidance and omits the single most natural trigger term for this domain ("render"). Adding a Use-when clause with render/export phrasing would lift it substantially.

Suggestions

Add an explicit trigger clause, e.g. "Use when the user asks to render or export a Remotion composition, still frame, or editable timeline."

Include the natural term "render" (and variations like "frame" or editor names such as DaVinci Resolve/Premiere) since users of this skill will say "render" far more often than "export".

Consider mentioning input props or transparency support to broaden the specificity of capabilities listed.

DimensionReasoningScore

Specificity

The description names the domain and concrete output types ("Remotion video, still image, or editable OpenTimelineIO timeline") but relies on a single verb, so it reads as 1-2 concrete actions rather than the several distinct actions of anchor 4.

3 / 5

Completeness

The "what" is clear ("Export a Remotion video, still image, or editable OpenTimelineIO timeline"), but there is no "Use when..." clause or equivalent trigger guidance, which caps completeness at 3.

3 / 5

Trigger Term Quality

Relevant keywords like "Remotion", "video", "still image", and "timeline" are present, but the most natural trigger for this domain — "render" — is absent, along with common variations such as "frame", ".mp4", and editor names like DaVinci Resolve or Premiere.

3 / 5

Distinctiveness Conflict Risk

"Remotion" and "OpenTimelineIO" are niche-specific technology names, giving the skill a clear trigger niche with minimal risk of firing for unrelated skills.

5 / 5

Total

14

/

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, 1 suspicious

Warning

Total

14

/

16

Passed

Repository

remotion-dev/remotion

Path

packages/skills/skills/remotion-render/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.