Tessl • The package manager for agent skills

SkillPublic

remotion

Programmatic video creation with React. Useful for branded explainers, social cuts, dashboards-to-video, and reproducible motion graphics.

Quality

64%

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 ./skills/remotion/SKILL.md

Quality

Content

47%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 lean and well organized as a catalogue stub, but it provides almost no executable guidance: the sole command opens a browser, and the essential 'install the upstream bundle' step has no actual instruction. As a result actionability and workflow clarity sit well below the midpoint.

Suggestions

Replace the browser-open with an executable step, e.g. `npx create-video@latest` or a concrete git-clone/copy command for installing the upstream bundle into the skills directory.

Define the install workflow explicitly (1. fetch upstream, 2. copy into <skills-dir>/remotion, 3. verify the skill is discoverable) instead of deferring everything to "inspect the upstream README".

If local reference/script files are meant to exist, include them in the bundle rather than advertising "original assets, scripts, and references" that are not present.

Dimension	Reasoning	Score
Conciseness	The body is short (~30 lines) with no explanations of concepts Claude already knows; every section is brief. Minor waste keeps it below the 'every token earns its place' anchor: the description text and the upstream URL/category from the frontmatter are duplicated in 'What it does' and 'Source'.	4 / 5
Actionability	The only concrete command is `open https://github.com/remotion-dev/remotion`, which merely opens a browser and accomplishes none of the described task; "install the upstream bundle into your active agent's skills directory" has no actual command. This matches 'minimal concrete guidance; high-level hints but missing the specific steps to execute' rather than anchor 3, which requires some usable (even if incomplete) concrete guidance.	2 / 5
Workflow Clarity	A rough sequence is present (inspect README → install bundle → invoke by name/triggers), but the critical step (installing the bundle) is undefined and no checkpoints exist. This matches 'rough sequence present but many gaps; steps poorly defined'; the skill is not destructive/batch, so no validation cap applies.	2 / 5
Progressive Disclosure	Sections (What it does, Source, How to use) are well organized, the body is under 50 lines, and there are no nested references or inline reference dumps. It falls below the anchor-5 clean split because the skill's actual payload (upstream assets, scripts, and references) is entirely deferred to an external URL with no local files, leaving the pointer structure somewhat hollow.	4 / 5
	Total	12 / 20 Passed

Description

65%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 and distinctive with a clear 'what' and reasonably natural trigger terms, but it lacks an explicit 'Use when...' clause and states no concrete actions beyond generic 'creation'. Adding explicit trigger guidance and 1-2 concrete capability verbs would lift it from good to excellent.

Suggestions

Append an explicit trigger clause, e.g. "Use when the user wants to generate videos with code, render React components to MP4, or create data-driven motion graphics."

State concrete actions instead of only output categories, e.g. "Compose video sequences as React components, animate with useCurrentFrame, and render to MP4/WebM."

Add a few natural trigger synonyms such as "render video", "video with code", or "animate with React" to the description/triggers.

Dimension	Reasoning	Score
Specificity	"Programmatic video creation with React" names the domain, and "branded explainers, social cuts, dashboards-to-video, and reproducible motion graphics" enumerates concrete output types, but no concrete actions (render, compose, export, animate) are stated. This matches the anchor 'names domain and 1-2 concrete actions, but not comprehensive'; it is above anchor 2 because the use-case enumeration is specific rather than generic.	3 / 5
Completeness	The 'what' is clear ("Programmatic video creation with React"), but there is no explicit 'Use when...' clause; "Useful for branded explainers..." is only weakly implied when-guidance. Per the judging guideline, a missing explicit 'Use when...' clause caps completeness at 3, which fits the 'clear what but when weakly implied' anchor.	3 / 5
Trigger Term Quality	The description contains natural phrases users would say ("programmatic video", "video creation with React", "motion graphics") and the frontmatter adds "react video", "video composition", "remotion". A few common variations are missing (e.g. "render video", "make videos with code", file formats), matching the 'good keyword coverage; a few natural terms missing' anchor rather than the comprehensive anchor 5.	4 / 5
Distinctiveness Conflict Risk	React-based programmatic video is a clear niche, and the named triggers ("remotion", "react video", "motion graphics", "video composition") are unlikely to fire for unrelated skills. It matches the 'clear niche with distinct triggers; minimal conflict risk' anchor; it is above anchor 4 because overlap with generic video-editing skills is negligible.	5 / 5
	Total	15 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: nexu-io/open-design
Path: skills/remotion/SKILL.md
Revision: 78d5637

Reviewed: 18 days ago

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.

remotion

Table of Contents

Is this your skill?