scaffold-element

Scaffold a new Remotion Element for development in the docs Remotion Studio.

Quality

70%

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

Quality

Content

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

This is a well-executed short, single-purpose skill: it delegates design guidance to the authoritative repo docs via clear one-level-deep links and provides a copy-paste command for launching the preview studio. The only real gap is that the actual scaffolding mechanics live entirely in an external document, so the skill offers no fallback or summary of those steps.

Dimension	Reasoning	Score
Conciseness	The body is ~13 lines and every sentence carries an instruction: where to read guidance, which section to follow, the preview command, and how to surface the URL. No concepts Claude already knows are explained, matching anchor 5 (lean, every token earns its place).	5 / 5
Actionability	The studio launch is fully executable and copy-paste ready ("cd packages/docs" / "bunx remotion studio --no-open") with concrete follow-up steps ("Read the URL from the command output and open that URL in the available browser"). The core scaffolding steps themselves are delegated to the external "Develop the Element" doc section rather than inlined, which is a minor gap versus anchor 5's 'specific examples cover the common cases'.	4 / 5
Workflow Clarity	The sequence is clear: read guidelines and contribution guide → follow the "Develop the Element" section → suggest previewing → start the studio → read URL → open the browser. It falls just short of anchor 5 because there is no checkpoint confirming the Element was scaffolded/registered before launching the preview, and the initial steps depend on an external document. Not destructive or batch, so the cap of 3 does not apply.	4 / 5
Progressive Disclosure	There are no bundle files, and the skill is well under 50 lines, so per the rubric's simple-skill guidance 5 is attainable with well-organized sections. Both external references (guidelines.mdx, contributing.mdx with the anchored "Develop the Element" section) are clearly signaled markdown links, one level deep, with no inlined bulk content.	5 / 5
	Total	18 / 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 states a single concrete capability in an appropriately terse, third-person voice, but it does not tell Claude when to invoke the skill, which caps completeness at 3. It would benefit from an explicit 'Use when...' trigger clause with natural synonyms such as 'create a new element', 'scaffold a component', or 'add an Element to the gallery'.

Suggestions

Append a trigger clause, e.g. "Use when the user asks to scaffold, create, or add a new Remotion Element, or to preview an Element in the docs Remotion Studio."

Add natural synonyms and file/repo terms users would actually say — "new element", "element template", "element gallery", "docs studio" — to improve trigger term coverage.

Mention the follow-on capabilities the skill actually performs (previewing the Element in Docs Studio, opening the browser) so the 'what' is more comprehensive.

Dimension	Reasoning	Score
Specificity	"Scaffold a new Remotion Element for development in the docs Remotion Studio" names the domain and one concrete action (scaffolding an Element) plus its context (docs Remotion Studio), but lists no further actions such as previewing, validating, or submitting to the gallery. It matches anchor 3 (domain plus 1-2 concrete actions, not comprehensive) and not 4, which requires several specific actions, nor 2, since the action given is concrete rather than generic.	3 / 5
Completeness	The 'what' is clear (scaffold a new Remotion Element for development in the docs Remotion Studio), but there is no 'Use when...' clause or equivalent trigger guidance, so per the rubric completeness is capped at 3. It is not a 2 because the 'what' is concrete, and not a 4 because no 'when' is present even weakly.	3 / 5
Trigger Term Quality	Relevant keywords are present ("Scaffold", "Remotion Element", "Remotion Studio", "docs"), but natural variations users would say are missing — e.g. "create", "new element", "component", "template", "gallery". This fits anchor 3 (some relevant keywords, missing common variations/synonyms) rather than 4, whose example shows broader natural-term coverage.	3 / 5
Distinctiveness Conflict Risk	The niche is quite specific (Remotion Elements, docs Studio), so overlap risk is minor — mainly with other Remotion scaffolding/preview skills. It fits anchor 4 (mostly distinct, minor overlap risk) rather than 5 because it lacks explicit distinct trigger phrases, and not 3 because the domain terms are far more specific than generic examples like "Works with document files".	4 / 5
	Total	13 / 20 Passed

Validation

93%

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

Validation for skill structure

Criteria	Description	Result
relative_links	Relative link issues: 3 suspicious	Warning

	Total	15 / 16 Passed

Repository: remotion-dev/remotion
Path: .agents/skills/scaffold-element/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.