CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

remotion-interactivity

Structures Remotion markup so layers, timing and styles are editable in Remotion Studio. Use when writing a new composition or restructuring existing markup.

Quality

83%

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

SKILL.md
Quality
Evals
Security

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 content is highly actionable and token-efficient: concrete rules with executable good/bad code examples throughout, and it includes validation where it matters (connected compositions). Its main weakness is navigation: two of the referenced reference files are missing from the actual bundle, undermining the progressive-disclosure structure.

Suggestions

Add the missing timeline-structure.md and inline-effects.md files to the bundle (e.g. in references/), or remove/fix the links pointing to them, since the skill directs the reader to read timeline-structure.md before writing any scene.

Consider moving the 16-row schema field type table into a reference file (e.g. references/schema-types.md) and keeping only the most common types inline with a pointer.

Give the sibling-skill references (../remotion-markup/video-editing.md, ../remotion-markup/connected-compositions.md) a brief label of what each covers so readers can decide whether to load them without opening the files.

DimensionReasoningScore

Conciseness

The body is dense with Studio-specific rules Claude would not know, each earning its place with good/bad code pairs and a properly flagged deprecated alias ("text-content is a deprecated alias"), though a few passages (the childrenSchema explanation, the schema fragment listing) could be trimmed.

4 / 5

Actionability

Every rule comes with copy-paste-ready executable code, contrasting ❌ examples, install commands for all four package managers, and exact statements of which interpolate() input forms are supported ("Bare identifiers ... multiplication with a number such as 2 * fps ... are supported").

5 / 5

Workflow Clarity

There is a clear entry directive ("Before writing a scene or refactoring its layers, read editable timeline structure") and a validation checkpoint for connected compositions ("Validate both its standalone view and the full parent timeline"), but the rest of the body is a set of parallel style rules rather than a sequenced workflow.

4 / 5

Progressive Disclosure

References are well-signaled and one level deep with context for each, but the bundle contains only SKILL.md and assets/remotion-icon.svg — the referenced files timeline-structure.md and ./inline-effects.md do not exist in the bundle, so the primary "read this first" pointer is broken; the 16-row schema type table is also inline API-reference material.

3 / 5

Total

16

/

20

Passed

Description

83%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 strong description: it states a specific capability in third person and gives an explicit, concrete 'Use when' trigger clause. Keyword coverage is good, with only minor gaps in natural synonyms and slight overlap risk with a sibling Remotion skill.

DimensionReasoningScore

Specificity

"Structures Remotion markup so layers, timing and styles are editable in Remotion Studio" names the domain and a concrete capability covering three distinct targets (layers, timing, styles), though it omits other covered areas like animations, SVG paths, and schema fields.

4 / 5

Completeness

Explicitly answers both what ("Structures Remotion markup so layers, timing and styles are editable in Remotion Studio") and when ("Use when writing a new composition or restructuring existing markup") with concrete trigger phrases.

5 / 5

Trigger Term Quality

Includes natural terms a user would say — "Remotion", "Remotion Studio", "composition", "layers", "timing", "styles" — but misses common variations like "video", "animation", or "React video".

4 / 5

Distinctiveness Conflict Risk

The Remotion/Studio-editability niche is highly distinct, but the trigger "writing a new composition" could overlap with a closely related general Remotion markup skill, giving minor conflict risk.

4 / 5

Total

17

/

20

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

relative_links

Relative link issues: 2 missing, 3 suspicious

Warning

Total

14

/

16

Passed

Repository

remotion-dev/remotion

Path

packages/skills/skills/remotion-interactivity/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.