docs-demo

Add an interactive demo to the Remotion documentation. Use when creating a new <Demo> component for docs pages.

Quality

74%

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 ./.agents/skills/docs-demo/SKILL.md

Quality

Content

75%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.

A well-structured, actionable skill body with concrete paths, a field reference, and a working registration example. It is efficient and clearly sequenced, with only minor room to tighten explanations and show a full component example.

Suggestions

Add a minimal complete component example (MyDemo.tsx using useCurrentFrame/useVideoConfig) so the create step is fully copy-paste ready.

Trim the explanatory clause in step 1 to assume Claude's competence with React/Remotion hooks.

Dimension	Reasoning	Score
Conciseness	Mostly lean with concrete file paths and a tight registration example; minor explanatory phrases such as 'It should be a standard React component using Remotion hooks...' could be trimmed since Claude already knows React/Remotion.	4 / 5
Actionability	Provides concrete file paths, a full field list for DemoType registration, and an executable code example; the component-creation step is described rather than shown as complete copy-paste code, leaving a minor gap.	4 / 5
Workflow Clarity	Clear four-step sequence (create component, register in types.ts, add to demos array, use in MDX) with real paths; no validation checkpoints, but the task is non-destructive and non-batch so they are not critical.	4 / 5
Progressive Disclosure	Well-organized into Steps, Options, and Example registration sections and self-contained with no external references needed; slightly over the 50-line simple-skill threshold, otherwise a 5.	4 / 5
	Total	16 / 20 Passed

Description

73%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.

A concise, well-targeted description that names its niche and provides an explicit 'Use when' trigger. It is slightly thin on action variety and trigger synonyms but carries very low conflict risk.

Suggestions

Add 1-2 more concrete actions (e.g., 'configure interactive controls', 'register effect demos') to broaden specificity beyond a single action.

Expand trigger phrases with synonyms users might say (e.g., 'embed a player', 'add an interactive preview', 'add controls to a demo').

Dimension	Reasoning	Score
Specificity	Names the Remotion-docs domain and one concrete action ('Add an interactive demo to the Remotion documentation'), but offers only a single action rather than the several concrete actions expected for higher scores.	3 / 5
Completeness	Clearly states both what (add an interactive demo to Remotion docs) and when ('Use when creating a new <Demo> component for docs pages'); the 'when' is explicit and concrete but could add more trigger variations to reach 5.	4 / 5
Trigger Term Quality	Includes natural trigger terms a user would plausibly say ('interactive demo', 'Remotion documentation', '<Demo> component', 'docs pages'); a few synonyms (e.g. 'embed a player', 'preview') are missing.	4 / 5
Distinctiveness Conflict Risk	Targets a highly specific niche (Remotion documentation <Demo> components) with distinct triggers and minimal realistic overlap with other skills.	5 / 5
	Total	16 / 20 Passed

Validation

100%

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

Validation for skill structure

No warnings or errors.

Repository: remotion-dev/remotion
Path: .agents/skills/docs-demo/SKILL.md
Commit: a1011d6

Reviewed: 4 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.