remotion-markup

Content, animation and effects best practices

Quality

45%

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-markup/SKILL.md

Quality

Content

65%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 well-organized, actionable Remotion markup reference with strong code examples and clean progressive-disclosure intent, but it is undermined by a missing bundle (none of the referenced detail files ship alongside it), a duplicated section, and the absence of any validation/feedback workflow.

Suggestions

Ship the referenced detail files (sfx.md, transitions.md, effects.md, timing.md, etc.) in the bundle, or inline the essential guidance and drop the dead links so navigation actually resolves.

Remove the duplicated '## Maps' section (lines ~213 and ~272) and fix typos ('refactored', 'timelien', 'useCurrenFrame', 'wrap it in`<Sequence>`') that hurt clarity.

Add an explicit validate-then-fix loop to the render-check step, e.g. 'run `npx remotion still`, inspect the frame, fix markup, re-render'.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes Claude's competence with React/Remotion, leading with executable rules and code rather than concept explanations; only minor trimming is needed (a duplicated '## Maps' section and a few typos like 'refactored'/'timelien').	4 / 5
Actionability	It provides concrete, mostly copy-paste-ready code (FadeIn, scale/translate/rotate, media components, example scene) and specific CLI commands (npx remotion add/studio/still), with only small gaps such as `fps` being used before useVideoConfig is shown in the first example.	4 / 5
Workflow Clarity	This is a best-practices reference rather than a sequenced workflow; guidance is grouped by topic but there is no explicit step sequence or validation checkpoint, and the 'one-frame render check' section offers no validate-then-fix feedback loop.	3 / 5
Progressive Disclosure	The overview is well structured and clearly signals one-level-deep references (e.g. 'See [sfx.md](sfx.md)'), but the bundle contains only assets/remotion-icon.png — none of the ~27 referenced .md files exist, so the navigation points to missing files and discovery is broken.	3 / 5
	Total	14 / 20 Passed

Description

25%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 a terse domain label with a generic "best practices" action and no trigger guidance, so it fails to tell Claude when to invoke this skill over its siblings. It scores uniformly low across specificity, triggers, completeness, and distinctiveness.

Suggestions

Add a concrete 'Use when...' clause naming natural triggers, e.g. 'Use when writing or editing Remotion React markup — adding animations, transitions, media, or visual effects to a composition.'

Replace the generic 'best practices' with 2-3 concrete actions (e.g. 'drive animations with useCurrentFrame/interpolate, add media components, apply visual effects').

Differentiate from sibling skills by anchoring on 'React markup / JSX' specifically rather than the broad 'content, animation and effects'.

Dimension	Reasoning	Score
Specificity	The description "Content, animation and effects best practices" names the domain (content, animation, effects) but the only action named is the generic phrase "best practices", matching the anchor where actions are minimal or generic.	2 / 5
Completeness	It offers only a vague "what" ("best practices" for content/animation/effects) and entirely omits any "when"/"Use when..." guidance, matching the anchor for a vague what with no when.	2 / 5
Trigger Term Quality	"animation" and "effects" are a couple of generic domain keywords, but the description lacks the natural trigger phrases a user would actually say (e.g. "add animation", "animate", "visual effects") and includes no synonyms or variants.	2 / 5
Distinctiveness Conflict Risk	The phrasing is very broad and overlaps heavily with sibling skills the body itself references (remotion-best-practices, remotion-interactivity), giving high overlap risk with many similar skills.	2 / 5
	Total	8 / 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: 30 missing, 3 suspicious	Warning

	Total	14 / 16 Passed

Repository: remotion-dev/remotion
Path: packages/skills/skills/remotion-markup/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.