CtrlK
BlogDocsLog inGet started
Tessl Logo

remotion-docs

Search Remotion documentation

61

Quality

73%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

High

Do not use without reviewing

Fix and improve this skill with Tessl

tessl review fix ./packages/codex-plugin/skills/remotion-docs/SKILL.md

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

SKILL.md
Quality
Evals
Security

Quality

Content

93%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 skill: fully executable search-and-fetch instructions with a token-saving .md trick and a crisp four-step workflow. The only gap is the absence of any fallback guidance when search results are empty or irrelevant, which keeps workflow clarity at 4 rather than 5.

DimensionReasoningScore

Conciseness

The body is ~40 lean lines with zero padding: it never explains what Remotion or Algolia is, states 'Append .md to any Remotion docs URL ... (saves tokens)', and jumps straight to the request. This matches anchor 5 (lean, assumes Claude's competence, every token earns its place); nothing to trim down to anchor 4.

5 / 5

Actionability

The Algolia block is a complete copy-paste HTTP request (endpoint, API key, application id, index name, attributes, JSON body) and three concrete example .md URLs are given. Anchor 5 (fully executable, covers common cases) fits; anchor 4 would require minor gaps, and the only unstated detail (the HTTP client) is immaterial.

5 / 5

Workflow Clarity

The four-step workflow (search, pick URLs, fetch .md, implement) is a clear, coherent sequence, matching anchor 4. It falls short of anchor 5 because no checkpoints or feedback loops exist — e.g., what to do when search returns no relevant hits or the .md fetch fails — though the read-only nature of the task keeps it above anchor 3.

4 / 5

Progressive Disclosure

The skill is under 50 lines with no need for external references (references/ and scripts/ directories do not exist), and per the rubric guideline such a skill scores 5 with well-organized sections, which it has. The single cross-skill pointer to ../remotion-best-practices/SKILL.md is one level deep and clearly signaled.

5 / 5

Total

19

/

20

Passed

Description

53%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 and names a distinct niche, but it is too thin: it omits any 'Use when...' trigger guidance and understates the skill's actual capabilities (search plus fetching docs as Markdown). Adding an explicit trigger clause and one more concrete action would lift specificity and completeness.

Suggestions

Add a 'Use when...' clause, e.g. 'Use when the user asks about Remotion, its APIs (Player, useCurrentFrame, Lambda), or React video rendering.'

Mention the additional concrete action of fetching doc pages as Markdown so the description covers what the skill actually does.

Include common trigger variations such as 'Remotion docs' or 'Remotion API' to improve natural keyword coverage.

DimensionReasoningScore

Specificity

The description 'Search Remotion documentation' names the domain and one concrete action (search), but does not mention the other capabilities the body provides (fetching pages as Markdown). This matches anchor 3 (domain plus 1-2 concrete actions, not comprehensive); it is above anchor 2 because 'search' is a concrete action rather than generic processing, and below anchor 4 because no list of several specific actions appears.

3 / 5

Completeness

The 'what' is clear (search Remotion documentation) but there is no 'Use when...' clause or equivalent trigger guidance, which caps completeness at 3 per the judging guidelines. Below 4 because the 'when' is entirely absent rather than merely imprecise.

3 / 5

Trigger Term Quality

'Remotion' and 'documentation' are relevant keywords, but common variations users would say are missing: 'Remotion docs', 'Remotion API', 'React video', '<Player>', 'useCurrentFrame'. Anchor 3 (some relevant keywords, missing variations) fits; not 4 since coverage is thin for a single-product niche, not 2 since 'Remotion' is a specific natural term rather than generic.

3 / 5

Distinctiveness Conflict Risk

'Remotion' carves out a clear niche with minimal conflict against unrelated skills, but the description gives no trigger distinguishing it from the sibling 'remotion-best-practices' skill referenced in the body, so anchor 4 (mostly distinct, minor overlap with a closely related skill) fits better than 5.

4 / 5

Total

13

/

20

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

relative_links

Relative link issues: 1 suspicious

Warning

Total

14

/

16

Passed

Repository
remotion-dev/remotion
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.