CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

scaffold-element

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

Quality

75%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/scaffold-element/SKILL.md
SKILL.md
Quality
Evals
Security

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.

The body is a model of token-efficient delegation: a single ordered flow, one owned executable command, and clearly labeled one-level-deep references to project docs. Its only soft spot is that the scaffolding specifics live entirely in external documentation, leaving inline actionability one notch below fully copy-paste ready.

DimensionReasoningScore

Conciseness

The ~15-line body is lean and assumes Claude's competence — it delegates design guidance to external docs via a single sentence and provides only the one command it actually owns ('bunx remotion studio --no-open'), with every token earning its place. It is clearly the 'lean and efficient' anchor, not the 4 anchor which expects trimmable over-explanation.

5 / 5

Actionability

The Studio launch command is concrete and copy-paste ready, and the conditional flow (suggest preview, if agreed start without opening a browser, read the URL, open it) is executable. It falls short of 5 because the core scaffolding steps themselves are delegated to an external doc section rather than covered by concrete inline guidance — a minor but real gap.

4 / 5

Workflow Clarity

A clear sequence is present: read guidelines and contribution guide, follow the 'Develop the Element' section, then post-scaffolding preview steps with an explicit conditional checkpoint ('If the user agrees'). It matches the 'clear sequence with most checkpoints' anchor; it is not 5 because there is no validation or error-recovery loop around the Studio launch, and not 3 because the steps and conditionals are explicit rather than implicit.

4 / 5

Progressive Disclosure

The skill is a concise overview with well-signaled, one-level-deep references — each external doc link is labeled with its purpose ('design and implementation guidance', 'official gallery submission process') and points at a specific section anchor. There is no nested referencing and no content inlined that belongs in a separate file, fitting the top anchor exactly.

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 clear, specific 'what' in an appropriately terse form, but it entirely lacks a 'when to use' trigger clause and offers few natural trigger synonyms. Adding a 'Use when...' clause would resolve the main weakness.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user wants to create or scaffold a new Remotion Element for the docs gallery or preview it in the Studio.'

Include natural trigger variations users would actually say, such as 'create', 'add', 'new Element', or 'Element contribution'.

Briefly enumerate what scaffolding covers (e.g. generating boilerplate files, registering the Element) to raise specificity from one action to several.

DimensionReasoningScore

Specificity

The description names the domain ('Remotion Element', 'docs Remotion Studio') and one concrete action ('Scaffold'), matching the 'domain plus 1-2 concrete actions' anchor; it does not list multiple specific actions that would warrant a 4.

3 / 5

Completeness

The 'what' is clear (scaffold a new Remotion Element for the docs Studio), but there is no 'Use when...' clause or equivalent trigger guidance, so 'when' is only weakly implied — this caps completeness at 3 per the judging guidelines.

3 / 5

Trigger Term Quality

'Scaffold a new Remotion Element' and 'docs Remotion Studio' are relevant natural terms, but common variations users would say ('create', 'add', 'new Element', 'Element gallery') are missing, fitting the 'some relevant keywords but missing variations' anchor.

3 / 5

Distinctiveness Conflict Risk

'Remotion Element' plus 'docs Remotion Studio' carves out a distinct niche with minimal conflict risk; only closely related Remotion docs/contribution skills could overlap, fitting the 'mostly distinct' anchor rather than the fully distinct 5 anchor which expects explicit distinct triggers.

4 / 5

Total

13

/

20

Passed

Validation

93%

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

CriteriaDescriptionResult

relative_links

Relative link issues: 3 suspicious

Warning

Total

15

/

16

Passed

Repository

remotion-dev/remotion

Path

.agents/skills/scaffold-element/SKILL.md

Reviewed

Table of Contents

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.