CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

remotion-docs

Search Remotion documentation

Quality

77%

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

Fix and improve this skill with Tessl

tessl review fix ./packages/skills/skills/remotion-docs/SKILL.md
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, fully executable skill: a ready-to-use Algolia search request, a token-saving Markdown-fetch trick, and a crisp workflow, all with no padding. The only minor gap is the absence of any fallback guidance when search returns nothing useful or a fetch fails.

DimensionReasoningScore

Conciseness

The ~42-line body is lean and assumes Claude's competence — it gives the Algolia endpoint, the '.md' suffix trick with a one-phrase rationale ("saves tokens"), and a 4-step workflow with zero padding or explanations of known concepts, matching the 'every token earns its place' anchor.

5 / 5

Actionability

The Algolia POST block is copy-paste ready with a real endpoint, API key, index name, and params, and the '.md' fetch pattern includes three concrete example URLs; this fully matches the 'fully executable, copy-paste ready' anchor.

5 / 5

Workflow Clarity

The 4-step workflow (search, pick URLs, fetch with '.md', implement) is clearly sequenced, but there are no checkpoints for failure cases such as empty search results or a 404 on a fetched page, fitting 'clear sequence with most checkpoints; minor validation gaps' rather than the explicit-feedback-loops anchor.

4 / 5

Progressive Disclosure

The skill is under 50 lines, needs no external reference files, and is organized into three clear sections (Searching the docs, Fetching a page as Markdown, Workflow); the single cross-reference to the sibling best-practices skill is clearly signaled and one level deep, so per the rubric's simple-skill guideline this earns a 5.

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 minimal to a fault: it states a single action and provides no 'when to use' guidance or natural trigger terms. Adding an explicit 'Use when...' clause covering Remotion, docs, and React video work would substantially raise completeness and trigger quality.

Suggestions

Add an explicit 'Use when...' clause, e.g. "Use when the user asks about Remotion, React video rendering, or needs current Remotion API/docs information."

Mention the full capability set in the description — both searching the docs and fetching pages as Markdown — so the 'what' is comprehensive, not just 'Search'.

Include natural trigger terms and synonyms users would actually say ("Remotion", "docs", "Remotion API", "React video") to improve trigger term quality and disambiguation from the sibling remotion-best-practices skill.

DimensionReasoningScore

Specificity

"Search Remotion documentation" names the domain and one concrete action (search), matching the anchor for 1-2 concrete actions without comprehensive coverage; it stays below 4 because actions like fetching or reading pages are absent from the description.

3 / 5

Completeness

The description gives a clear 'what' ("Search Remotion documentation") but includes no 'Use when...' clause or equivalent trigger guidance, which the rubric explicitly caps at 3; it is not a 2 because the 'what' is concrete, not vague.

3 / 5

Trigger Term Quality

"Remotion" and "documentation" are relevant keywords, but common natural variations users would say — "docs", "Remotion API", "React video" — are missing, matching the 'some relevant keywords but missing variations' anchor rather than the good-coverage anchor.

3 / 5

Distinctiveness Conflict Risk

"Remotion documentation" carves out a clear niche with minimal conflict against unrelated skills, but the closely related sibling skill (remotion-best-practices) creates minor overlap risk and the description offers no trigger phrases to disambiguate, fitting anchor 4 rather 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

Path

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