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

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

Quality

Content

65%

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 with concrete code, parameter tables, and timing conventions, and it appropriately avoids re-explaining core Remotion concepts. It is held back by some redundancy across the transitions sections, a referenced reference.md that is absent from the bundle, and the lack of validation checkpoints in any workflow.

Suggestions

Provide or remove the referenced reference.md so the 'Advanced API' link resolves to a real bundle file.

Consolidate the 'Available Custom Transitions' table and 'Transition Examples' block to remove duplicated option/invocation information.

Add an explicit build/preview validation step (e.g., 'run npm run studio and confirm the transition renders without flicker') to give the preview workflow a checkpoint.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean and defers core knowledge to remotion-official, but the 'Transition Examples' block re-lists invocations already implied by the options table, and three transitions sections overlap somewhat.	2 / 3
Actionability	Provides concrete executable TSX imports, TransitionSeries usage, transition calls with specific parameters, and a runnable preview command — copy-paste ready and specific.	3 / 3
Workflow Clarity	The TransitionSeries example is sequenced and best practices form a checklist, but this is a reference/catalog skill with no multi-step workflow containing explicit validation checkpoints or feedback loops.	2 / 3
Progressive Disclosure	Sections are clearly organized and the 'Advanced API' reference to reference.md is well-signaled and one level deep, but reference.md is not present in the bundle and large component/transition catalogs are inline.	2 / 3
	Total	9 / 12 Passed

Description

57%

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 scopes the skill to toolkit-specific Remotion patterns and usefully disambiguates it from the remotion-official skill, but it lists categories rather than concrete actions and lacks an explicit 'Use when...' trigger clause. Adding trigger guidance and action verbs would raise specificity and completeness.

Suggestions

Add an explicit 'Use when...' clause naming natural triggers (e.g., 'Use when building toolkit video templates, custom scene transitions, or reusable video components in Remotion').

Replace category nouns with concrete actions (e.g., 'Compose scenes with custom transitions, reuse shared video components, and follow project timing conventions').

Broaden trigger terms to include user-natural phrasing like 'video', 'scenes', and 'templates'.

Dimension	Reasoning	Score
Specificity	Names the domain and categories ('custom transitions, shared components, and project conventions') but these are noun-phrases rather than concrete actions like 'extract' or 'merge', so it falls short of the multi-action anchor.	2 / 3
Completeness	The 'what' is stated clearly ('Toolkit-specific Remotion patterns...'), but there is no explicit 'Use when...' trigger clause, capping completeness at 2 per the guideline.	2 / 3
Trigger Term Quality	'Remotion', 'transitions', 'animations', and 'rendering' are natural terms, but coverage is thin on common variations a user might actually say (e.g., 'video', 'scenes', 'components').	2 / 3
Distinctiveness Conflict Risk	The explicit cross-reference routing core knowledge to 'remotion-official' carves a clear toolkit-specific niche and actively reduces conflict risk with the sibling skill.	3 / 3
	Total	9 / 12 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: 0af32ce

Reviewed: 1 day 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.