CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

remotion-license

Find Remotion license information, FAQs, terms, and where to buy a license.

Quality

87%

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

The canonical home for this skill is remotion-license in remotion-dev/skills

SKILL.md
Quality
Evals
Security

Quality

Content

100%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 a model of minimal, effective design: it dispatches licensing questions to three clearly labeled official resources and points to the purchase site with no wasted tokens. Structure, actionability, and disclosure are all fully appropriate for a simple link-dispatch skill.

DimensionReasoningScore

Conciseness

"For questions about Remotion licensing, read the relevant resource" followed by three labeled links and one purchase line is lean with zero padding and no explanation of concepts Claude already knows — every token earns its place, matching anchor 5.

5 / 5

Actionability

The body gives exact, copy-paste-ready URLs (including .md variants for token-efficient fetching) for each question type plus a specific purchase site, fully covering the common cases for this instruction-only skill — anchor 5 rather than 4 because no concrete step is missing.

5 / 5

Workflow Clarity

This is a simple single-purpose skill where the single action — read the relevant labeled resource for the user's licensing question — is unambiguous, so it qualifies for 5 under the simple-skill exception; no destructive or batch operations are involved so no validation steps are required.

5 / 5

Progressive Disclosure

The skill is under 50 lines with no need for bundle reference files: it is a clear overview with well-signaled, one-level-deep references. The only bundle file (assets/remotion-icon.svg) is an unreferenced branding asset and does not constitute a content-organization gap.

5 / 5

Total

20

/

20

Passed

Description

70%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 concise, third-person, and highly distinct thanks to the named product, but it lacks an explicit 'Use when...' trigger clause and misses several natural trigger synonyms such as pricing or commercial use. Adding trigger guidance would raise completeness and trigger coverage.

Suggestions

Add an explicit trigger clause, e.g. "Use when the user asks about Remotion licensing, pricing, commercial use, or whether they need to buy a license."

Include natural synonyms users would say — "pricing", "commercial use", "free tier" — to broaden trigger term coverage.

Mention distinguishing what the skill covers for each resource (e.g., license text vs. FAQ answers) to sharpen the 'what' portion of the description.

DimensionReasoningScore

Specificity

"Find Remotion license information, FAQs, terms, and where to buy a license" lists several concrete items (license, FAQs, terms, purchase) in a clearly named domain, matching anchor 4; it is not comprehensive enough for 5 since it uses a single verb and omits items like pricing or commercial-use terms.

4 / 5

Completeness

The 'what' is clear (find license info, FAQs, terms, purchase location) but there is no 'Use when...' clause or equivalent explicit trigger guidance, which caps completeness at 3 per the judging guidelines; the 'when' is only weakly implied by the topic.

3 / 5

Trigger Term Quality

Natural phrases like "Remotion license", "FAQs", "terms", and "buy a license" give good keyword coverage, but common variations users would say — "pricing", "commercial use", "free tier" — are missing, placing it at anchor 4 rather than 5.

4 / 5

Distinctiveness Conflict Risk

Naming a specific product (Remotion) and a specific concern (licensing) creates a clear niche with distinct triggers and minimal conflict risk with other skills, matching anchor 5.

5 / 5

Total

16

/

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

frontmatter_unknown_keys

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

Warning

Total

15

/

16

Passed

Repository

remotion-dev/remotion

Path

packages/skills/skills/remotion-license/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.