CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

remotion-render

Export a 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/codex-plugin/skills/remotion-render/SKILL.md

The canonical home for this skill is remotion-render in remotion-dev/skills

SKILL.md
Quality
Evals
Security

Quality

Content

85%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 exemplary lean overview: executable commands, pointers to full documentation, no padding, and unambiguous per-task routing. Its two real gaps are the bare commands lacking a fully-argumented example for the common render case, and a broken in-bundle reference — the transparent-videos.md file it links to is missing from the bundle.

Suggestions

Ship the referenced `transparent-videos.md` in the bundle (e.g. under `references/`) or inline its key guidance, since the body links to a file that is not present.

Add one fully-argumented example, e.g. `npx remotion render src/index.ts <composition-id> out/video.mp4`, alongside the bare commands to cover the common non-default render case.

DimensionReasoningScore

Conciseness

The ~15-line body gives the two commands directly ("npx remotion render", "npx remotion still"), links to the full option lists for everything else, and contains zero background explanation or padding — every token earns its place and it fully assumes Claude's competence. There is nothing to trim, so it matches the lean anchor exactly.

5 / 5

Actionability

Both commands are real, copy-paste-runnable CLI invocations, but they are bare: no example with the arguments the common case needs (entry point, composition id, output path, e.g. `npx remotion render src/index.ts MyComp out/video.mp4`). This matches "Mostly executable guidance; concrete code or commands with minor gaps"; it is not 5 because the commands only cover the zero-configuration default case.

4 / 5

Workflow Clarity

This is a simple single-action skill where each task maps to one unambiguous command — video to `npx remotion render`, still to `npx remotion still` — with transparent video explicitly routed to its own section; the simple-skill exception applies and the actions are unambiguous. Rendering a video is neither destructive nor a batch operation, so no validation cap applies.

5 / 5

Progressive Disclosure

The body itself is well-structured and clearly signals a one-level-deep reference ("See [Transparent videos](./transparent-videos.md) for rendering out a video with transparency"), but the referenced file does not exist in the bundle — there is no `references/` directory and no `transparent-videos.md` anywhere, only `assets/remotion-icon.png`. The organization gap is more than minor (the pointer resolves to nothing), so it falls to "Some structure but could be better organized" rather than 4.

3 / 5

Total

17

/

20

Passed

Description

52%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 admirably concise and carves out a distinctive, low-conflict niche (Remotion video export), but it is too sparse: a single action, no 'when to use' clause, and missing the natural synonym 'render' and output-format terms users would actually say. It sits at the 'clear what, missing when' level despite covering a well-defined capability.

Suggestions

Add an explicit trigger clause, e.g. "Use when the user wants to render or export a Remotion project to a video file (MP4/WebM) or a still image."

Include natural synonyms and concrete terms — 'render', 'MP4', 'still image' — so the description matches the phrasing users and Claude actually use.

Mention the still-rendering capability (the body documents `npx remotion still`), not just video export, so the description reflects what the skill covers.

DimensionReasoningScore

Specificity

"Export a Remotion video" names a specific domain but provides only a single minimal action ('Export'), with no mention of stills, output formats, or the other capabilities the skill covers — matching "Names the domain but actions are minimal or generic". It is not 3 because there is no second concrete action or expanded capability list, and not 1 because the domain and action are concrete rather than vague.

2 / 5

Completeness

It has a clear 'what' ("Export a Remotion video") but no 'when' guidance at all — no 'Use when...' clause or equivalent trigger phrase, which caps completeness at 3 per the judging guidelines. It is not 4 because there is zero when/trigger guidance, and not 2 because the 'what' is concrete and unambiguous.

3 / 5

Trigger Term Quality

The terms 'Remotion', 'video', and 'export' are relevant keywords a user might naturally say, but the description misses the most common synonym 'render' (the very verb the skill body leads with) plus format terms like 'MP4' or 'still'. This matches "Some relevant keywords but missing common variations or synonyms"; it is not 4 because coverage is only three words and the primary user phrasing ('render my video') is absent.

3 / 5

Distinctiveness Conflict Risk

'Remotion' is a highly distinctive niche trigger term that virtually no other skill would claim, and 'export a video' scopes it further — matching "Clear niche with distinct triggers; minimal conflict risk". It is not 4 because there is no realistic overlap with closely related skills.

5 / 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: 1 missing

Warning

Total

14

/

16

Passed

Repository

remotion-dev/remotion

Path

packages/codex-plugin/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.