docs-demo

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

Quality

83%

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

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.

An exemplary compact skill: repo-specific, executable, and tightly organized, with a correct early note distinguishing effect demos from generic demos. The only improvement would be a light verification step at the end of the workflow.

Dimension	Reasoning	Score
Conciseness	The body is lean with zero padding: no explanation of what Remotion or React is, and every line carries repo-specific facts (file paths, registry fields, option type specs). Matches anchor 5's 'every token earns its place'.	5 / 5
Actionability	Fully executable guidance: exact file paths (packages/docs/components/demos/types.ts, index.tsx), a complete DemoType field list, per-option required props (min/max/step/default, values), and a copy-paste-ready registration example. The common case (create, register, use in MDX) is completely covered, matching anchor 5.	5 / 5
Workflow Clarity	A clear, correctly sequenced 4-step workflow (create → register → add to array → use in MDX) with concrete artifacts per step, but no verification checkpoint (e.g., confirming the demo renders in the docs page), which anchor 4 describes as 'clear sequence with minor validation gaps'. The operation is non-destructive, so the batch/destructive cap does not apply.	4 / 5
Progressive Disclosure	A ~50-line single-file skill with well-organized sections (intro, effects-demo boundary note, steps, options, example) and no bundle files — per the under-50-lines exception, well-organized sections alone warrant a 5, and nothing here needs to be split out.	5 / 5
	Total	19 / 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, third-person description with an explicit what-and-when structure and a distinct niche. Its main weaknesses are limited action coverage (only one concrete action) and trigger keywords that could include more natural synonyms and related terms.

Suggestions

List 2-3 concrete actions to raise specificity, e.g., 'Add an interactive demo to the Remotion documentation: create the demo component, register it in the demos registry, and add interactive option controls.'

Broaden trigger terms with natural synonyms users would say, such as 'when the user mentions a docs demo, an interactive player example, or <EffectsDemo> registrations.'

Add a distinguishing cue for the effects-demo variant (e.g., 'for effect demos use <EffectsDemo> instead') so the description itself covers the boundary the body draws.

Dimension	Reasoning	Score
Specificity	Names the domain ('Remotion documentation', 'interactive demo') and one concrete action ('Add an interactive demo'), which matches anchor 3's '1-2 concrete actions, but not comprehensive'. It does not list several specific actions (e.g., registering demos, adding option controls), so it is not a 4.	3 / 5
Completeness	Both 'what' ('Add an interactive demo to the Remotion documentation') and 'when' ('Use when creating a new <Demo> component for docs pages') are explicit, matching anchor 4. Not a 5 because the when-clause offers a single trigger phrasing rather than multiple concrete trigger phrases including synonyms.	4 / 5
Trigger Term Quality	Includes good natural keywords a user would say — 'interactive demo', 'Remotion documentation', 'docs pages', '<Demo> component' — but misses common variations like 'effects demo', '@remotion/player', or 'Remotion player', so it falls just short of comprehensive anchor 5.	4 / 5
Distinctiveness Conflict Risk	A clear niche (Remotion docs <Demo> components) with distinct triggers ('<Demo> component', 'docs pages'), giving minimal overlap risk with other skills — a clean match for anchor 5.	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: 6f4e0d5

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