remotion-saas

Building video apps with Remotion - framework, rendering and Player advice

Quality

50%

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

Quality

Content

50%

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

The body is admirably concise and well-organized as an overview/index, but it offers almost no executable guidance — every section defers to other files that are not actually present in the bundle. It works as a launcher but fails to instruct, and its broken reference links undermine progressive disclosure.

Suggestions

Provide at least one concrete, executable snippet or command per section (e.g. a minimal render command or Player embed code) rather than only pointing to other files.

Either ship the referenced bundle files (framework.md, player.md, rendering.md) under references/ or inline the essential guidance so navigation is not broken.

For the rendering section, add a short decision rule or comparison (Lambda vs Vercel vs Node.js vs Cloudflare) so Claude can act without loading the external file.

Dimension	Reasoning	Score
Conciseness	The body is short and lean, mostly signposting with no padding of concepts Claude already knows; every section earns its place, matching the 'lean and efficient; every token earns its place' anchor.	3 / 3
Actionability	Almost all guidance is vague pointers ("See [framework.md] for help choosing", "See [rendering.md] for advice on how to choose") with no code, commands, or concrete steps, matching the 'vague or abstract; describes rather than instructs' anchor.	1 / 3
Workflow Clarity	Sections are organized topically but there is no real sequence or validation; it functions as a topical index rather than a workflow, so it sits at 'sequence present but checkpoints missing'.	2 / 3
Progressive Disclosure	References are one-level-deep and clearly signaled (framework.md, player.md, rendering.md), which is the right shape, but no bundle files exist in references/scripts/assets so the referenced paths are missing, breaking navigation and capping this below 3.	2 / 3
	Total	8 / 12 Passed

Description

50%

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 names a specific niche (Remotion video apps) and lists several relevant areas, but it reads as a terse label rather than an explicit trigger: it lacks concrete actions and any 'Use when...' guidance. It is adequate but generic enough to land at the middle of the scale across all dimensions.

Suggestions

Add an explicit 'Use when...' trigger clause, e.g. 'Use when building or debugging video apps with Remotion, choosing a rendering target, or embedding the Remotion Player'.

Replace category nouns ('framework, rendering and Player advice') with concrete verbs/actions to lift specificity, e.g. 'Choose a Remotion template, configure server- or client-side rendering, and embed the Player'.

Include natural keyword variations users might say ('Remotion', 'video rendering', 'programmatic video', 'Remotion Player', 'Remotion Lambda') to improve trigger coverage.

Dimension	Reasoning	Score
Specificity	"Building video apps with Remotion" names the domain and "framework, rendering and Player advice" lists some areas, but these are categories rather than concrete actions like extract/fill/merge, so it matches the 'names domain and some actions' anchor.	2 / 3
Completeness	It answers what the skill does (building video apps with Remotion; framework, rendering and Player advice) but contains no 'Use when...' clause or equivalent explicit trigger guidance, which caps completeness at 2 per the judging guidelines.	2 / 3
Trigger Term Quality	"Remotion", "video apps", "Player", and "rendering" are relevant keywords a user might say, but coverage is thin with no common variations or trigger phrasing, matching the 'some relevant keywords but missing common variations' anchor.	2 / 3
Distinctiveness Conflict Risk	"Remotion" with "Player" and "rendering" is a fairly distinct niche unlikely to conflict broadly, but the description is terse with no explicit triggers to lock in distinctiveness, so it sits at 'somewhat specific but could still overlap' rather than a clear 3.	2 / 3
	Total	8 / 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: 3 missing	Warning

	Total	14 / 16 Passed

Repository: remotion-dev/remotion
Path: packages/skills/skills/remotion-saas/SKILL.md
Commit: 03df8b0

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.