scaffold-element

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

Quality

66%

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

78%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 token-efficient and well-structured as a lean overview that defers detail to one clearly-signaled external reference. Its main weakness is actionability: the central scaffolding task is delegated to the external guide rather than surfaced with concrete inline steps.

Suggestions

Add a brief inline summary of the key scaffolding steps (e.g. file location, naming convention, registration) so the core task is actionable without first reading the external guide.

Clarify how to confirm the Element was scaffolded correctly (e.g. expected file paths or a quick check) as a lightweight validation checkpoint.

Make the link to the contribution guide more discoverable by giving the section a short inline orientation of what 'Develop the Element' covers.

Dimension	Reasoning	Score
Conciseness	The body is lean with no concept explanations Claude already knows; every line earns its place by either pointing to the source of truth or giving the concrete preview command.	5 / 5
Actionability	The preview step is fully executable (cd packages/docs; bunx remotion studio --no-open), but the core scaffolding procedure is deferred to an external guide rather than given as concrete steps, leaving a significant gap.	3 / 5
Workflow Clarity	There is a clear sequence (read guide → scaffold → offer preview → run studio → open URL) and scaffolding is non-destructive, but the scaffolding step itself is delegated to the external reference rather than sequenced inline.	4 / 5
Progressive Disclosure	The SKILL.md is a concise overview with a single, clearly-signaled one-level-deep reference (the Element contribution guide) used as the source of truth, with navigation to a specific section via anchor.	5 / 5
	Total	17 / 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 names a concrete, well-scoped action in a distinct niche, but it lacks any explicit "when to use" trigger guidance, which caps its completeness. Adding a Use-when clause with natural trigger phrases would materially improve it.

Suggestions

Add a 'Use when...' clause, e.g. 'Use when creating a new Remotion Element or when the user asks to scaffold an Element for the docs Studio.'

Include common synonyms/variations like 'create' or 'new component' alongside 'scaffold' to broaden trigger coverage.

Optionally list 1-2 more concrete sub-actions of scaffolding to lift specificity toward comprehensive coverage.

Dimension	Reasoning	Score
Specificity	It names a concrete action ("Scaffold a new Remotion Element") and a well-scoped domain ("docs Remotion Studio"), but coverage is limited to a single action rather than a comprehensive list.	3 / 5
Completeness	The "what" is clear (scaffold a Remotion Element) but there is no "Use when..." or equivalent trigger guidance, so per the judging guidelines completeness is capped at 3.	3 / 5
Trigger Term Quality	Relevant natural terms are present ("scaffold", "Remotion Element", "Remotion Studio") but common variations or synonyms (e.g. "create", "new component") are missing.	3 / 5
Distinctiveness Conflict Risk	The Remotion Element / docs Remotion Studio niche is specific and largely distinct from other skills, though the absence of an explicit trigger phrase leaves minor overlap risk.	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: 2 suspicious	Warning

	Total	15 / 16 Passed

Repository: remotion-dev/remotion
Path: .agents/skills/scaffold-element/SKILL.md
Commit: dbb2c0a

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