remotion-interactivity

Structure Remotion markup for interactivity

Quality

68%

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

Quality

Content

82%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 an efficient, highly actionable set of Remotion interactivity rules with comprehensive copy-paste-ready examples and clear sectioning. Main room for improvement is tightening a few prose sentences and consolidating the long interpolate() example.

Dimension	Reasoning	Score
Conciseness	The body is code-forward with short imperative headers and inline 👍/❌ annotations, with only minor sentences that could be trimmed (e.g. "Be sensible, if a component has many elements..."), matching the score-4 efficient anchor.	4 / 5
Actionability	It provides copy-paste-ready TSX for interactive elements, interpolate() animations, <Composition> metadata, and effects arrays, with both good and bad executable examples covering the common cases, matching the score-5 anchor.	5 / 5
Workflow Clarity	This is a multi-rule guidance skill rather than a sequenced process; each rule is an unambiguous single action with before/after examples, fitting the score-4 clear-guidance anchor with minor sequencing gaps.	4 / 5
Progressive Disclosure	Content is organized into focused ## sections with two clearly-signaled one-level-deep outbound references, but references point to external docs rather than a local bundle and a couple of sections could be trimmed, matching score-4.	4 / 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 clear niche, but it states only one action and omits any "Use when..." trigger guidance. Adding concrete actions and an explicit trigger clause would lift specificity, completeness, and trigger-term quality.

Suggestions

Add an explicit "Use when..." clause naming trigger situations, e.g. "Use when writing Remotion components that need to be editable or interactive in the Remotion Studio."

List 2-3 concrete actions (e.g. make elements selectable, enable drag/resize/rotate, expose keyframes and easing) to raise specificity from 3 toward 4-5.

Include natural trigger synonyms users would say ("interactive", "editable", "Remotion Studio", "timeline") to broaden trigger-term coverage.

Dimension	Reasoning	Score
Specificity	"Structure Remotion markup for interactivity" names the domain and one concrete action but is not comprehensive; it matches the score-3 anchor of naming a domain with 1-2 concrete actions.	3 / 5
Completeness	It gives a clear "what" (structure markup for interactivity) but no "Use when..." trigger clause; per the guidelines a missing trigger clause caps completeness at 3.	3 / 5
Trigger Term Quality	"Remotion" is a relevant natural keyword but there are no synonyms or common variations (interactive, editable, Studio, timeline), matching the score-3 anchor of some relevant keywords missing variations.	3 / 5
Distinctiveness Conflict Risk	"Remotion markup for interactivity" is a clear niche with minimal conflict risk, mostly distinct from other skills with only minor overlap risk, fitting the score-4 anchor.	4 / 5
	Total	13 / 20 Passed

Validation

87%

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

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning
relative_links	Relative link issues: 1 suspicious	Warning

	Total	14 / 16 Passed

Repository: remotion-dev/remotion
Path: packages/skills/skills/remotion-interactivity/SKILL.md
Commit: 77354de

Reviewed: about 20 hours 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.