CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

remotion-docs

Search Remotion documentation

Quality

82%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

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 an exemplary lean, single-purpose skill: a fully executable search request, a clever token-saving fetch technique, and a clear workflow, with zero verbosity or padding. No changes needed.

DimensionReasoningScore

Conciseness

The ~40-line body is lean and assumes competence: a one-line purpose statement ("This skill teaches you how to discover and read current Remotion documentation"), a complete API request, URL examples, and a 4-step workflow with zero padding. Every token earns its place, matching anchor 5; there is nothing to trim for a 4-vs-5 distinction.

5 / 5

Actionability

The Algolia POST block is fully executable with a real endpoint, API key, application ID, and request body, and the ".md" suffix trick is shown with three concrete URL examples — copy-paste ready covering the common cases, matching anchor 5. Not a 4 because there are no gaps: the response shape ("Each hit contains a `url` field") is also explained.

5 / 5

Workflow Clarity

The 4-step workflow (search → pick URLs → fetch .md → implement) is clearly sequenced and each step maps to a concrete technique described above; it even includes routing guidance ("If this is not relevant, load Remotion Best Practices instead"). This is a simple, read-only lookup skill with no destructive or batch operations, so the simple-skill exception applies and the unambiguous sequence earns 5.

5 / 5

Progressive Disclosure

The skill is under 50 lines with no need for external references, organized into three clear sections (Searching the docs, Fetching a page as Markdown, Workflow), which per the guideline scores 5 for simple skills with well-organized sections. The only bundle file is an icon asset, appropriately kept out of the body.

5 / 5

Total

20

/

20

Passed

Description

57%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 identifies a clear, distinct niche but is underwritten: it states a single action with no trigger guidance and minimal keyword variation. Adding an explicit 'Use when...' clause and a couple of concrete actions and synonyms would raise most dimensions.

Suggestions

Add an explicit trigger clause, e.g. "Use when working with Remotion, the React framework for programmatic video, or when questions arise about Remotion APIs, @remotion/* packages, or video rendering."

Enumerate concrete actions beyond search: "Search the Remotion docs via Algolia, fetch any docs page as Markdown, and verify API usage against current documentation."

Include natural synonym terms users would say — "Remotion docs", "React video", "Remotion Player", "Remotion Lambda" — to improve trigger term coverage.

DimensionReasoningScore

Specificity

"Search Remotion documentation" names the domain and one concrete action (search), matching the anchor 'Names domain and 1-2 concrete actions, but not comprehensive'. It is not a 4 because it does not list several specific actions (e.g., fetching pages, verifying APIs), and not a 2 because a concrete action is explicitly stated rather than generic.

3 / 5

Completeness

It has a clear 'what' (search Remotion documentation) but no 'when'/trigger clause at all, exactly matching anchor 3 and capped there by the guideline 'A missing Use when... clause should cap completeness at 3'. Not a 4 because 'when' is entirely absent rather than just implicit.

3 / 5

Trigger Term Quality

The only natural keywords are "Remotion" and "documentation"; common variations users would say — "Remotion docs", "React video", "video rendering", "@remotion packages" — are missing, matching 'Some relevant keywords but missing common variations or synonyms'. Not a 4 because keyword coverage is thin beyond the single product name.

3 / 5

Distinctiveness Conflict Risk

"Remotion" is a highly specific product niche with a distinct trigger term, so it is clearly distinguishable from other skills with minimal conflict risk, matching anchor 5. Not a 4 because there is no meaningful overlap with other domains — the product name alone disambiguates.

5 / 5

Total

14

/

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/skills

Path

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