CtrlK
BlogDocsLog inGet started
Tessl Logo

mediabunny

Multimedia handling with the Mediabunny library

43

Quality

45%

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

Quality

Content

50%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is admirably concise and well-organized into per-task sections, but it delegates all actual instruction to reference files that are missing, leaving it without executable guidance. The progressive-disclosure structure is correct in form but broken in practice.

Suggestions

Provide the referenced bundle files (get-audio-duration.md, get-video-dimensions.md, get-video-duration.md) so the disclosure chain resolves.

Add a minimal executable code snippet per task directly in the body so the skill is actionable even before following a reference.

Include a short validation/verification note for each task (e.g. how to confirm a returned duration is plausible) to strengthen workflow clarity.

DimensionReasoningScore

Conciseness

The body is lean — a one-line intro plus a compact llms.txt overview pointer and brief per-task sections — with no padding or explanation of concepts Claude already knows, matching the 'lean and efficient' anchor.

3 / 3

Actionability

No executable code or commands appear in the body; each section only directs to a reference file ('See [get-audio-duration.md]...'), and those referenced files do not exist, so there is no concrete, executable guidance.

1 / 3

Workflow Clarity

The three tasks are clearly labeled and unambiguous as single actions, but the actual procedure lives only in missing reference files, so the sequence/steps a user would follow are not present in the content.

2 / 3

Progressive Disclosure

Structure is clean with well-signaled, one-level-deep references per task, but the referenced files (get-audio-duration.md, get-video-dimensions.md, get-video-duration.md) are absent, so navigation leads to dead ends rather than the 'easy navigation' required for a 3.

2 / 3

Total

8

/

12

Passed

Description

40%

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 third-person but vague: it names the domain and library without listing concrete capabilities or any usage triggers. It reads more like a label than an actionable skill description.

Suggestions

Replace 'Multimedia handling' with concrete actions, e.g. 'Get audio/video duration and video dimensions in the browser with the Mediabunny library'.

Add an explicit trigger clause such as 'Use when the user asks for media duration, video dimensions, or browser audio/video processing'.

Include natural trigger terms like 'audio duration', 'video dimensions', and 'seconds' so the skill surfaces for common user phrasings.

DimensionReasoningScore

Specificity

The phrase 'Multimedia handling' names only a domain and a library with no concrete actions, matching the vague/abstract anchor ('Helps with documents') rather than the score-2 anchor which requires 'some actions'.

1 / 3

Completeness

It states a (weak) 'what' — multimedia handling — but provides no 'Use when...' or equivalent trigger guidance, so per the judging guidelines completeness is capped at 2.

2 / 3

Trigger Term Quality

'multimedia' and 'Mediabunny' are relevant terms a user might say, but common natural variations like 'audio', 'video', 'duration', or 'dimensions' are absent from the description, fitting the 'some relevant keywords but missing common variations' anchor.

2 / 3

Distinctiveness Conflict Risk

Naming the specific 'Mediabunny library' gives it a niche, but 'Multimedia handling' is generic enough to overlap with other media skills, matching the 'somewhat specific but could still overlap' anchor.

2 / 3

Total

7

/

12

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

metadata_version

'metadata.version' is missing

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.