remotion-saas

Build an app with Remotion

Quality

40%

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

43%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 a concise topical index with clear section headers, but it provides no executable guidance and its progressive disclosure is broken — the referenced detail files (framework.md, player.md, rendering.md) are absent from the bundle. It reads as a stub rather than an actionable skill.

Suggestions

Add the missing referenced files (framework.md, player.md, rendering.md) to the bundle, or remove the dead links and inline the essential guidance.

Include at least one concrete, executable example (e.g., a minimal <Player> embedding snippet or a render command) so the skill is actionable without chasing references.

Tighten the opening lines: drop 'One can build apps with Remotion.' and the 'It is possible to have...' sentence, which restate the description without adding information.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean pointers with section headers and minimal prose, but the opening lines ("One can build apps with Remotion." and "It is possible to have a simple form...") are mild filler that restates the description. This fits 'Efficient; minor instances of over-explanation that could be trimmed.' It is not a 5 because those introductory tokens do not all earn their place.	4 / 5
Actionability	The body offers only high-level pointers ("See [Player](player.md)", "See [Rendering](rendering.md)") with no executable code, commands, or concrete steps, fitting 'Minimal concrete guidance; high-level hints but missing the specific steps to execute.' Named platforms (Lambda, Vercel, Node.js, Cloudflare) add slight concreteness above a 1, but there is nothing executable.	2 / 5
Workflow Clarity	There is no sequenced workflow, numbered steps, or validation; the sections are parallel topics (templates, Player, rendering, alternative frameworks) with only a loose implicit order. This fits 'Rough sequence present but many gaps; steps poorly defined; validation absent.' It is not a 1 because the topical structure is coherent, but no real process is presented.	2 / 5
Progressive Disclosure	Section structure is clean and references are clearly signaled one level deep, but the referenced files framework.md, player.md, and rendering.md do not exist in the bundle (only assets/remotion-icon.png is present), so the disclosure is broken. Per the rubric's guidance to score against the actual bundle structure, this fits 'Some structure but could be better organized' rather than a 4, because navigation leads to missing files.	3 / 5
	Total	11 / 20 Passed

Description

36%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 a terse five-word phrase that names the tool but gives only a single generic action and no usage trigger. It is too thin on both 'what' specifics and 'when' guidance to score well.

Suggestions

Add a 'Use when...' clause stating when Claude should invoke this skill (e.g., 'Use when the user wants to build, scaffold, or render video apps with Remotion').

Replace the single generic action with 2-3 concrete capabilities (e.g., scaffold SaaS templates, embed the <Player>, render client- or server-side).

Include natural synonyms users say, such as 'video', 'render', and 'programmatic video', to improve trigger coverage.

Dimension	Reasoning	Score
Specificity	The phrase "Build an app" names the domain (Remotion) but offers only a single, generic action with no concrete specifics, matching the anchor 'Names the domain but actions are minimal or generic.' It is not a 1 because it does name a concrete tool, and not a 3 because there is no second concrete action.	2 / 5
Completeness	The description gives a vague 'what' ("Build an app") and has no 'when' / 'Use when' trigger clause at all, fitting 'Has a vague what and no when.' Per the rubric cap it cannot exceed 3, and the thin 'what' keeps it at 2 rather than 3.	2 / 5
Trigger Term Quality	"Remotion" is a natural keyword a user would actually say, but the description omits common variations and synonyms (video, render, video editor, programmatic video). This fits 'Some relevant keywords but missing common variations or synonyms.' It clears 2 because Remotion is a real natural term, not generic jargon, but lacks the breadth for 4.	3 / 5
Distinctiveness Conflict Risk	The named tool "Remotion" is a fairly specific trigger, but the generic "Build an app" framing overlaps with general app/web-development skills, fitting 'Somewhat specific but could still overlap with similar skills.' It is not a 4 because the broad framing leaves real overlap risk.	3 / 5
	Total	10 / 20 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
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	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: 77354de

Reviewed: about 20 hours 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.