CtrlK
BlogDocsLog inGet started
Tessl Logo

remotion

Programmatic video creation with React. Useful for branded explainers, social cuts, dashboards-to-video, and reproducible motion graphics.

48

Quality

51%

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

Quality

Content

45%

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

The content is concise and well-structured as a catalogue pointer, but it provides no executable guidance, no real install steps, and defers everything to an external GitHub repo rather than bundling actionable references — leaving actionability weak.

Suggestions

Add concrete, executable instructions instead of only linking upstream (e.g., a real install command and a minimal render example) to raise actionability.

Provide a genuine install/invoke workflow with a validation checkpoint (e.g., verify the skill is registered) rather than "inspect the upstream README".

Bundle key references locally (a quickstart or example reference) so progressive disclosure points to real one-level-deep files instead of an external URL.

DimensionReasoningScore

Conciseness

The body is short and lean with no padding or explanations of concepts Claude already knows; every line serves the catalogue-entry purpose, matching "Lean and efficient; assumes Claude's competence."

3 / 3

Actionability

The only "command" is `open https://github.com/...` followed by "ask the agent to invoke this skill" — vague direction with no executable rendering/composition guidance, matching "Vague or abstract; no concrete code/commands; describes rather than instructs."

1 / 3

Workflow Clarity

It lists a loose sequence (inspect upstream, install bundle, invoke by name/trigger) but offers no validation, no concrete install commands, and no checkpoints; the sequence is present but checkpoints are missing, fitting "Steps listed but validation gaps."

2 / 3

Progressive Disclosure

It is a brief overview that defers all detail to an external upstream repo rather than to organized bundle files (none of references/scripts/assets exist); structure is present but navigation is an external link rather than well-signaled one-level-deep references, fitting "Some structure but could be better organized."

2 / 3

Total

8

/

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 is clear and domain-specific with good distinctiveness, but it lists use-case categories rather than concrete actions and lacks an explicit "Use when..." trigger clause, which caps both completeness and specificity at 2.

Suggestions

Add an explicit "Use when..." trigger clause (e.g., "Use when generating video programmatically with React, rendering motion graphics, or producing social/branded video cuts") to raise completeness to 3.

Replace generic use-case categories with concrete actions (e.g., "compose sequences, render frames, export MP4, schedule animations") to improve specificity.

Include natural user-facing keyword variations in the description body (e.g., "React video", "video composition", "motion graphics") to strengthen trigger-term coverage.

DimensionReasoningScore

Specificity

Names the domain (programmatic video with React) and concrete use-case categories ("branded explainers, social cuts, dashboards-to-video, and reproducible motion graphics"), but does not list specific executable actions like rendering, composing sequences, or exporting — stopping at the level of "Names domain and some actions, but not comprehensive."

2 / 3

Completeness

It states what the skill does but only implies when via "Useful for..." rather than an explicit "Use when..." clause; per the guidelines, a missing explicit trigger guidance caps completeness at 2.

2 / 3

Trigger Term Quality

The frontmatter triggers ("remotion", "react video", "programmatic video", "motion graphics", "video composition") are relevant and natural, but the description body itself lacks explicit "Use when..." keyword coverage, missing common variations; it sits at "Some relevant keywords but missing common variations."

2 / 3

Distinctiveness Conflict Risk

"Programmatic video creation with React" is a clear niche with distinct triggers unlikely to conflict with other skills, matching the top anchor for distinctiveness.

3 / 3

Total

9

/

12

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.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
nexu-io/open-design
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.