remotion

Remotion renderer for json-render that turns JSON timeline specs into videos. Use when working with @json-render/remotion, building video compositions from JSON, creating video catalogs, or rendering AI-generated video timelines.

Quality

80%

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

Quality

Content

80%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A tight, code-first reference: executable examples and compact tables deliver strong conciseness and actionability with no concept bloat. The main gap is the absence of a sequenced render workflow with validation checkpoints, which leaves workflow clarity at the mid level.

Suggestions

Add a short numbered 'Rendering workflow' section with explicit steps (define spec → assemble catalog → render/preview) and a validation checkpoint (e.g. confirm output duration/audio before final render) to raise workflow clarity.

Include one complete end-to-end example tying the catalog, custom component, and Player/Renderer wiring together so a single snippet can be run as-is.

Add brief error-recovery guidance for common rendering failures (e.g. missing component in catalog, duration mismatches) to support the feedback loop the rubric expects for rendering operations.

Dimension	Reasoning	Score
Conciseness	The body is lean — quick-start code, brief sections, and two compact tables — with no padding explaining what Remotion or JSON is; every line earns its place, matching the efficient anchor.	3 / 3
Actionability	Provides complete, copy-pasteable TypeScript snippets for the core tasks (Player wiring, catalog setup, custom components) plus a concrete timeline spec example and export/component tables, hitting the executable-code anchor.	3 / 3
Workflow Clarity	Sections cover the main tasks but there is no sequenced workflow with validation checkpoints — e.g. no render/preview steps or error-recovery guidance for the rendering pipeline — so it falls in the 'sequence present but checkpoints missing' band.	2 / 3
Progressive Disclosure	No references/ or scripts/ bundle exists, and the body is a well-organized single-file overview with clear sections and tables; per the rubric's simple-skill note this merits a 3 without external file references.	3 / 3
	Total	11 / 12 Passed

Description

80%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, third-person description that states concrete capabilities and gives explicit 'Use when...' triggers tied to a specific rendering stack. It is slightly held back by trigger terms that lean on package names and technical phrasing rather than the most natural user language.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'turns JSON timeline specs into videos', 'building video compositions from JSON', 'creating video catalogs', 'rendering AI-generated video timelines' — matching the multi-action anchor rather than naming only a domain.	3 / 3
Completeness	Explicitly answers both what ('turns JSON timeline specs into videos') and when ('Use when working with @json-render/remotion, building video compositions...'), satisfying the explicit-trigger anchor.	3 / 3
Trigger Term Quality	Includes natural phrases a user might say ('video compositions', 'video catalogs', 'AI-generated video timelines') but the dominant triggers lean on the package name '@json-render/remotion' and the somewhat technical 'JSON timeline specs', missing common user variations like 'make a video' or 'render to MP4'.	2 / 3
Distinctiveness Conflict Risk	The niche is narrow and clearly tied to the Remotion/json-render stack, with distinct triggers unlikely to collide with unrelated skills.	3 / 3
	Total	11 / 12 Passed

Validation

100%

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

Validation for skill structure

No warnings or errors.

Repository: vercel-labs/json-render
Path: skills/remotion/SKILL.md
Commit: 9d3dfc8

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