CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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

73%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.claude/skills/remotion/SKILL.md

The canonical home for this skill is remotion in calesthio/OpenMontage

SKILL.md
Quality
Evals
Security

Quality

Content

71%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 reference: real imports, named options, and concrete frame timings dominate over prose. Its main defect is structural — the single advertised deep-reference (reference.md) is missing from the bundle, and component usage lacks prop-level examples.

Suggestions

Ship reference.md in the bundle (or remove the 'Advanced API' section) so the link 'see [reference.md](reference.md)' resolves — the advertised API documentation currently does not exist.

Add one short usage example with props for the most common shared component (e.g., <AnimatedBackground variant="tech" />) so component consumers have copy-paste-ready syntax.

Trim the 'Transition Examples' code block (it duplicates option names from the transitions table) and condense or drop the 'Feedback & Contributions' footer to save tokens.

DimensionReasoningScore

Conciseness

The body is dominated by lean tables and executable code with no explanation of concepts Claude already knows — every section carries toolkit-specific facts (30fps convention, frame durations, component inventory). It misses anchor 5 due to minor trimmable material: the 'Transition Examples' block largely restates option names already listed in the transitions table, and the closing 'Feedback & Contributions' section is meta-maintenance content rather than operational guidance.

4 / 5

Actionability

Guidance is mostly executable: a complete copy-paste TransitionSeries example with real imports and option calls, exact option names and values per transition, frame-based duration tables, and a runnable preview command (`cd showcase/transitions && npm run studio`). It falls short of anchor 5 on minor gaps: no usage/props example for any shared component beyond an import line, and the import path is left vague ('adjust path based on your project location').

4 / 5

Workflow Clarity

The usage sequence is clear and well-ordered — import from lib, compose with TransitionSeries, follow timing conventions, then preview via the showcase studio command, which acts as a verification checkpoint. It is below anchor 5 because there is no error-recovery or render-failure guidance (e.g., what to check when a render flickers despite the 'frame-based animations only' rule), though this reference-style skill carries no destructive or batch operations that would cap the score.

4 / 5

Progressive Disclosure

The SKILL.md is appropriately structured as an overview with tables and short code kept inline, and it correctly signals where bulk detail belongs ('see [reference.md](reference.md)'). However, that referenced file does not exist in the bundle — no references/ directory or reference.md is present — making the primary deep-dive pointer a broken link. A clearly signaled but nonexistent reference is a real navigation failure, placing this between the minor-gaps anchor (4) and the disorganized-references anchor (3); the dangling link tips it to 3.

3 / 5

Total

15

/

20

Passed

Description

65%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 distinctive and well-bounded, explicitly separating toolkit-specific patterns from the official framework skill. Its main weaknesses are the absence of any 'use when' trigger guidance and capabilities phrased as generic areas rather than concrete actions.

Suggestions

Add an explicit trigger clause, e.g. 'Use when building or editing videos in this Remotion toolkit — adding scene transitions, reusing shared video components, or following project timing conventions.'

Convert generic area nouns into concrete actions: instead of 'custom transitions, shared components, and project conventions', say 'add custom scene transitions (glitch, light leak, clock wipe), reuse shared components (AnimatedBackground, SplitScreen, NarratorPiP), and apply 30fps timing conventions'.

Include natural user vocabulary such as 'video', 'scene', 'programmatic video' to broaden trigger coverage.

DimensionReasoningScore

Specificity

The description names the domain and lists concrete areas ("custom transitions, shared components, and project conventions") but these are noun phrases rather than actions, and "project conventions" is generic — matching the anchor for domain plus 1-2 concrete items without comprehensive coverage. It is below anchor 4 because it does not enumerate several specific actions (e.g., 'create scene transitions', 'compose video components'), and above anchor 2 because transitions and components are genuinely concrete capabilities.

3 / 5

Completeness

The 'what' is clear (toolkit-specific Remotion patterns: custom transitions, shared components, project conventions) but there is no 'Use when...' clause or equivalent explicit trigger guidance — the boundary sentence about the remotion-official skill scopes what belongs elsewhere rather than stating when to use this skill. Per the judging guideline, a missing trigger clause caps completeness at 3.

3 / 5

Trigger Term Quality

Natural terms a user would say are present — "Remotion", "transitions", "components", plus "hooks, animations, rendering" — giving good keyword coverage. It falls short of anchor 5 because common variations like "video", "programmatic video", or file/extension terms are missing.

4 / 5

Distinctiveness Conflict Risk

The description carves out a clear niche ("Toolkit-specific Remotion patterns") and explicitly disambiguates against the nearest competing skill ("For core Remotion framework knowledge (hooks, animations, rendering, etc.), see the `remotion-official` skill"), giving minimal conflict risk. This fully matches the clear-niche anchor with explicit boundary triggers.

5 / 5

Total

15

/

20

Passed

Validation

93%

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

CriteriaDescriptionResult

relative_links

Relative link issues: 1 missing

Warning

Total

15

/

16

Passed

Repository

calesthio/OpenMontage

Path

.claude/skills/remotion/SKILL.md

Reviewed

Table of Contents

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.