remotion-docs

Search Remotion documentation

Quality

73%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

High

Do not use without reviewing

Fix and improve this skill with Tessl

tessl review fix ./packages/skills/skills/remotion-docs/SKILL.md

Quality

Content

93%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 tight, fully executable guide with concrete API examples and a clear workflow. The only minor gap is the absence of error-handling guidance for failed searches or fetches.

Dimension	Reasoning	Score
Conciseness	Lean and efficient with no padding or explanation of concepts Claude already knows; every section (Algolia query, .md fetch, workflow) earns its tokens.	5 / 5
Actionability	Provides a copy-paste-ready Algolia POST request with full URL, headers, and JSON body, plus concrete .md URL examples covering the common cases.	5 / 5
Workflow Clarity	A clear 4-step sequence (search, pick URL, fetch .md, implement) but lacks validation checkpoints for empty results or failed fetches; the read-only nature means the destructive-cap does not apply.	4 / 5
Progressive Disclosure	Under 50 lines with well-organized sections and a single clearly-signaled one-level reference to a sibling skill; self-contained, so the simple-skill exception applies.	5 / 5
	Total	19 / 20 Passed

Description

53%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 clearly Remotion-specific but stops at a single action and omits any explicit trigger guidance. Adding a 'Use when...' clause and a few natural synonyms would meaningfully raise completeness and trigger-term quality.

Suggestions

Add an explicit 'Use when...' trigger clause, e.g. 'Use when the user asks about Remotion APIs, rendering, Remotion Lambda/Player, or needs current Remotion docs.'

Broaden specificity beyond 'Search' to name concrete actions such as 'Search, fetch, and read current Remotion documentation pages.'

Include natural trigger terms and synonyms users would actually say, such as 'Remotion docs', 'remotion.dev', 'Remotion Lambda', and 'Remotion Player'.

Dimension	Reasoning	Score
Specificity	Names the domain ('Remotion documentation') and one concrete action ('Search'), matching the anchor for 1-2 concrete actions without comprehensive coverage.	3 / 5
Completeness	Has a clear 'what' (search Remotion documentation) but no explicit 'Use when...' trigger clause, which caps completeness at 3 per the judging guidelines.	3 / 5
Trigger Term Quality	Includes the relevant keywords 'Remotion' and 'documentation' but lacks common variations or synonyms users might say (e.g. 'Remotion docs', 'remotion.dev').	3 / 5
Distinctiveness Conflict Risk	'Remotion' is a clear, specific niche with minimal conflict risk, though a sibling 'remotion-best-practices' skill creates minor overlap risk, keeping it just below 5.	4 / 5
	Total	13 / 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: 1 suspicious	Warning

	Total	14 / 16 Passed

Repository: remotion-dev/remotion
Path: packages/skills/skills/remotion-docs/SKILL.md
Commit: 77354de

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