remotion-interactivity

Structure Remotion markup for interactivity

Quality

61%

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

Quality

Content

75%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 a strong, well-organized best-practices guide: lean rule-plus-example sections, executable code with counterexamples, and clearly signaled follow-up references. Its main weaknesses are mild — some snippets lack surrounding context, one section defers entirely to an external link, and the one relative cross-reference points outside the bundle.

Dimension	Reasoning	Score
Conciseness	The body is efficient: each section states one rule in a sentence or two, then shows paired good/bad code, with no explanation of concepts Claude already knows. It is not level 5 because a few sections repeat the same rule the adjacent bad example already demonstrates (e.g. the double bad-examples under composition metadata), which could be trimmed slightly.	4 / 5
Actionability	Guidance is highly concrete and mostly executable: copy-paste-ready JSX for Interactive elements, interpolate() rules with exact supported expressions, an install command, and ❌-annotated counterexamples covering the common cases. It stops short of level 5 because several snippets are fragments without imports/component context, and one section ('Making your own component interactive') offers only an external link with no inline guidance.	4 / 5
Workflow Clarity	This is a best-practices skill, not a multi-step pipeline, and each section gives one unambiguous directive with do/don't examples; no validation checkpoints are needed since nothing destructive or batch-oriented is performed. Scored 4 rather than 5 because the sections are presented as a flat list with no ordering or grouping to help a reader apply them systematically when authoring a composition.	4 / 5
Progressive Disclosure	Good single-file structure with clear section headers per topic, and end-matter links that are clearly signaled and only one level deep (a remotion.dev doc and a sibling skill). Minor gaps keep it from level 5: the relative reference '../remotion-markup/video-editing.md' does not resolve inside this bundle (only an assets/remotion-icon.png exists), and ~310 lines of per-topic detail (e.g. path interpolation) could arguably live in reference files.	4 / 5
	Total	16 / 20 Passed

Description

48%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 specific domain, but it is one terse clause: it states what the skill does only at the highest level, lists none of the concrete interactive capabilities, and includes no 'use when' trigger guidance. It would benefit most from an explicit trigger clause and 2-3 concrete capability keywords.

Suggestions

Add an explicit 'Use when...' trigger clause, e.g. 'Use when writing Remotion components that should be editable in Remotion Studio (interactive elements, keyframes, timeline).'

Enumerate 2-3 concrete capabilities to lift specificity, e.g. 'Make elements selectable and drag/drop/resize-able, keep CSS styles and keyframes editable, and keep SVG paths morphable in Remotion Studio.'

Include natural trigger terms users would actually say: 'Remotion Studio', 'timeline', 'keyframes', 'interactive', 'editable', 'Video composition'.

Dimension	Reasoning	Score
Specificity	The description "Structure Remotion markup for interactivity" names the domain (Remotion markup) and a single generic action (structure it), closely matching the level-2 anchor "Processes PDF files". It does not enumerate any of the concrete capabilities the skill actually covers (selectable elements, drag/resize, editable styles, keyframes), so it falls short of the level-3 anchor's '1-2 concrete actions'.	2 / 5
Completeness	The 'what' is clear (structure Remotion markup so it becomes interactive), but there is no 'Use when...' clause or any trigger guidance, capping completeness at 3 per the judging guidelines. It clearly matches the level-3 anchor (clear what, when missing) and not level 4, which requires both what and an explicit when.	3 / 5
Trigger Term Quality	Relevant keywords are present ("Remotion", "markup", "interactivity") but common natural variations a user would say are missing: "Remotion Studio", "timeline", "keyframes", "editable". This matches the level-3 anchor "Works with PDF files" — some relevant keywords, missing variations and synonyms — rather than level 4's good-but-incomplete coverage.	3 / 5
Distinctiveness Conflict Risk	"Remotion markup for interactivity" carves a fairly specific niche tied to the Remotion Studio toolchain, giving mostly distinct triggers with only minor overlap risk against closely related Remotion skills (e.g., general Remotion markup/best-practices skills referenced in the body). It is not level 5 because the single short sentence shares trigger space with sibling Remotion skills.	4 / 5
	Total	12 / 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/codex-plugin/skills/remotion-interactivity/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.