CtrlK
BlogDocsLog inGet started
Tessl Logo

remotion-captions

Transcribing, displaying and animating captions

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

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./packages/skills/skills/remotion-captions/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

88%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 content is a tight, well-structured overview that delegates detail to three clearly signaled reference files, with a complete Caption type definition as the actionable core. Its main weakness is that the referenced bundle files are missing, slightly undermining progressive disclosure.

Suggestions

Add the referenced files (transcribe-captions.md, display-captions.md, import-srt-captions.md) to the bundle, or inline a minimal executable snippet for the most common task so the skill stands alone.

Keep the version number ('4.0.515') out of the body or move it to a 'Version' note, since it is package version metadata rather than skill guidance.

Optionally add a one-line validation hint (e.g., confirming caption startMs < endMs) given batch caption processing is a multi-record operation.

DimensionReasoningScore

Conciseness

The body is lean — a type definition, an import, and three short pointer sections — with no padding or explanation of concepts Claude already knows, so every token earns its place.

5 / 5

Actionability

The Caption type and import are concrete and copy-paste ready, but the per-task sections only dispatch to other files ('load the X file for more instructions') rather than giving executable transcribe/display code inline.

4 / 5

Workflow Clarity

Three clearly labeled single-action pathways (generating, displaying, importing) each dispatch unambiguously to one reference; as a simple skill with no destructive or batch operations, the sequence is fully clear.

5 / 5

Progressive Disclosure

The body is a clean overview with three one-level-deep, clearly signaled references, but the referenced files (transcribe-captions.md, display-captions.md, import-srt-captions.md) are not present in the bundle, leaving a minor organization gap.

4 / 5

Total

18

/

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 concisely names three concrete caption actions but omits any explicit 'Use when' trigger guidance and lacks natural synonyms like 'subtitles' or '.srt'. It is distinct yet somewhat under-specified on when to invoke it.

Suggestions

Add an explicit 'Use when...' clause naming concrete triggers (e.g., 'Use when the user wants to transcribe audio/video, render or animate on-screen captions, or import .srt files').

Include natural synonyms and file extensions such as 'subtitles', 'SRT', and '.srt' to improve trigger-term coverage.

Keep third person but expand the action list slightly (e.g., 'styling', 'positioning') to strengthen specificity.

DimensionReasoningScore

Specificity

Lists three concrete actions — 'Transcribing, displaying and animating captions' — covering the domain with only minor gaps, matching the 'several specific actions' anchor rather than the 1-2 action anchor.

4 / 5

Completeness

The 'what' is clear (three caption actions) but there is no 'Use when...' clause or equivalent trigger guidance, which per the guidelines caps completeness at 3.

3 / 5

Trigger Term Quality

The single keyword 'captions' is present but natural synonyms like 'subtitles', 'SRT', or '.srt' are missing, fitting the 'some relevant keywords but missing common variations' anchor.

3 / 5

Distinctiveness Conflict Risk

'Captions' carves a distinct niche with minimal overlap risk against other skills, though the bare phrasing could marginally overlap with general transcription skills.

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.

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

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.