CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

remotion-captions

Transcribing, displaying and animating captions

Quality

73%

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

Quality

Content

78%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 token-efficient, well-sectioned router that inlines only the essential Caption type and delegates each task to a dedicated file — a textbook progressive-disclosure design on paper. However, none of the three referenced files ship in the provided bundle, so the skill's navigation dead-ends and the actual task instructions are unreachable. Adding a minimal usage example and a verification step would round it out.

Suggestions

Ship the three referenced files (transcribe-captions.md, display-captions.md, import-srt-captions.md) in the bundle — currently the links are broken because no references/ directory or sibling .md files exist.

Inline a minimal concrete example of the core data format (e.g., a valid Caption JSON object) so the most common case is actionable without loading a reference file.

Add a post-render verification step to the Post-creation section (e.g., preview in Remotion Studio and confirm caption timing/sync before finishing).

DimensionReasoningScore

Conciseness

The body is a lean router: 'All captions must be processed in JSON', an exact import ('import type { Caption } from "@remotion/captions"'), and the full type definition — library-specific API Claude cannot know — with zero padding or explanation of known concepts. Matches the anchor 'Lean and efficient; assumes Claude's competence; every token earns its place'; not 4 because there is essentially nothing left to trim.

5 / 5

Actionability

Concrete, executable guidance: the exact package import path, the complete Caption type definition, and explicit per-task routing ('load the [transcribe-captions.md] file for more instructions'). Matches 'Mostly executable guidance; concrete code or commands with minor gaps'; not 5 because no worked example (e.g., a minimal valid Caption object or render snippet) is shown inline; not 3 because what is written is exact and complete, not pseudocode or vague hints.

4 / 5

Workflow Clarity

Task-based sections (Generating / Displaying / Importing) each give unambiguous routing, and the Post-creation section adds explicit sequencing ('After you're done, load this skill', 'open the Remotion Studio'). Matches 'Clear sequence with most checkpoints present; minor validation gaps'; not 5 because there are no validation/verification checkpoints (e.g., confirming caption timing renders correctly) and the multi-task body only partly qualifies for the simple-skill exception; not 3 because routing per task is unambiguous with no sequence gaps.

4 / 5

Progressive Disclosure

On paper the structure matches the top anchor (clear overview, one-level-deep, well-signaled references per section), but the three referenced files (transcribe-captions.md, display-captions.md, import-srt-captions.md) do not exist in the bundle — there is no references/ directory and no other .md files besides SKILL.md, so every navigation link dead-ends. Per the guideline to score against the actual bundle structure, this sits between anchors; not 4 because missing all three referenced files is more than a 'minor organization gap', not 2 because the overview itself is well-sectioned and nothing that belongs in separate files is inlined.

3 / 5

Total

16

/

20

Passed

Description

58%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 names three concrete, domain-specific actions but reads as a feature list rather than activation guidance: it has a clear 'what' and no 'when', and it misses the most natural user synonyms like 'subtitles' and '.srt'. It occupies a distinct niche, so conflict risk is low.

Suggestions

Add an explicit trigger clause, e.g., 'Use when the user mentions captions, subtitles, .srt files, or wants text synced to audio/video in Remotion.'

Include common synonyms and file extensions — 'subtitles', 'closed captions', '.srt' — so natural user phrasing reliably matches.

Mention importing captions from .srt files, since it is a supported capability the body documents but the description omits.

DimensionReasoningScore

Specificity

'Transcribing, displaying and animating captions' names the domain and lists three concrete actions. Matches 'Lists several specific actions; minor gaps in coverage'; not 5 because coverage is incomplete (e.g., importing captions from .srt files, a capability the body documents, is omitted); not 3 because it goes beyond 1-2 generic actions and the verbs are concrete rather than abstract.

4 / 5

Completeness

A clear 'what' is present (transcribing, displaying, animating captions) but there is no 'when' — no 'Use when...' clause or equivalent trigger guidance anywhere in the description, which the guidelines cap at 3. Not 4 because the 'when' is entirely absent rather than just imprecise; not 2 because the 'what' half is concrete and specific, not vague.

3 / 5

Trigger Term Quality

Relevant keywords are present ('Transcribing', 'captions') but common variations are missing — most notably 'subtitles', the synonym many users would naturally say, plus '.srt' and 'closed captions'. Matches 'Some relevant keywords but missing common variations or synonyms'; not 4 because the missing terms are central to this domain, not a few fringe ones; not 2 because 'captions' and 'transcribing' are genuinely natural domain terms, not generic filler.

3 / 5

Distinctiveness Conflict Risk

'Captions' carves out a clear niche that is unlikely to grab unrelated skills, though 'displaying and animating' could overlap with general video-animation or sibling Remotion skills. Matches 'Mostly distinct; minor overlap risk with closely related skills'; not 5 because no trigger scoping (e.g., 'in Remotion videos') further separates it from adjacent animation skills; not 3 because the domain is specific, not broad.

4 / 5

Total

14

/

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: 3 missing, 1 suspicious

Warning

Total

14

/

16

Passed

Repository

remotion-dev/remotion

Path

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