remotion

Toolkit-specific Remotion patterns — custom transitions, shared components, and project conventions. For core Remotion framework knowledge (hooks, animations, rendering, etc.), see the `remotion-official` skill.

Quality

59%

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 ./.agents/skills/remotion/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 highly actionable with executable code and a well-organized component/transition catalog, but it is a reference catalog rather than a sequenced workflow and points to a missing reference.md file. Removing the dead reference and tightening the redundant example section would improve conciseness and progressive disclosure.

Suggestions

Resolve the reference.md link: either add the bundled file or remove the 'Advanced API' section pointing to it so navigation is not broken.

Trim the redundant 'Transition Examples' block whose calls repeat options already enumerated in the 'Available Custom Transitions' table.

Add a short, explicit workflow for authoring a new template (import shared components -> compose with TransitionSeries -> preview with npm run studio) with a verification step to raise workflow clarity.

Dimension	Reasoning	Score
Conciseness	Mostly efficient tables and examples with no beginner-concept padding, but the Transition Examples section duplicates options already in the table and the Best Practices and Feedback/License sections add tokens that could be trimmed.	3 / 5
Actionability	Fully executable, copy-paste-ready code with real import paths, a complete TransitionSeries example, a runnable preview command, and example calls covering the common cases.	5 / 5
Workflow Clarity	As a patterns/reference catalog there is no real multi-step process with validation checkpoints; the implied import-compose-preview sequence is present but lacks explicit sequencing and checkpoints.	3 / 5
Progressive Disclosure	Section structure is clear with headers, but the one-level reference to reference.md points to a file that does not exist in any bundle directory, leaving navigation partially broken.	3 / 5
	Total	14 / 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 clearly defines a niche and disambiguates from the sibling remotion-official skill, but lacks an explicit "Use when..." trigger clause and uses category nouns instead of concrete action verbs. Adding natural trigger phrases and concrete actions would lift the specificity and completeness dimensions.

Suggestions

Add an explicit 'Use when...' clause naming natural user triggers, e.g. 'Use when building toolkit-specific Remotion videos: adding custom transitions, reusing shared components, or following project timing conventions.'

Convert the category nouns into concrete actions (e.g. 'Apply custom transitions like glitch and lightLeak, reuse shared components like AnimatedBackground and SlideTransition').

Include a few natural synonyms or file extensions users might say (e.g. '.tsx video templates', 'Remotion transitions') to broaden trigger-term coverage.

Dimension	Reasoning	Score
Specificity	Names three concrete capability areas ("custom transitions, shared components, and project conventions") but presents them as category nouns rather than concrete actions, fitting between the 1-2-actions anchor and the several-specific-actions anchor.	3 / 5
Completeness	A clear "what" is stated and a boundary to remotion-official is explicit, but there is no "Use when..." clause or equivalent explicit trigger guidance, which caps completeness at 3 per the rubric.	3 / 5
Trigger Term Quality	Domain-relevant keywords ("Remotion," "transitions," "components") are present but lack natural "Use when..." trigger phrasing and common synonyms or file extensions.	3 / 5
Distinctiveness Conflict Risk	Carves a clear toolkit-specific niche and explicitly redirects core Remotion knowledge to remotion-official, leaving only minor overlap risk with that closely related skill.	4 / 5
	Total	13 / 20 Passed

Validation

93%

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

Validation for skill structure

Criteria	Description	Result
relative_links	Relative link issues: 1 missing	Warning

	Total	15 / 16 Passed

Repository: calesthio/OpenMontage
Path: .agents/skills/remotion/SKILL.md
Commit: 1bab711

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