CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

remotion-multimedia

Interacting with Mediabunny

Quality

48%

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/codex-plugin/skills/remotion-multimedia/SKILL.md

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

SKILL.md
Quality
Evals
Security

Quality

Content

46%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 SKILL.md body is a clean, minimal index page whose entire instructional payload lives in three referenced files — but none of those files are included in the bundle, making every link dead and leaving the skill with no usable guidance. The structure and brevity are good; the missing content layer is fatal to actionability and progressive disclosure.

Suggestions

Include the three referenced files (get-audio-duration.md, get-video-dimensions.md, get-video-duration.md) in the bundle, or inline their essential code snippets directly into SKILL.md.

Add a minimal copy-paste-ready example for each task (e.g., the Mediabunny call that returns audio duration in seconds) so the skill remains actionable even if a reference file fails to load.

Clarify what the external llms.txt URL is for relative to the bundle references, so it does not read as a substitute for the missing local content.

DimensionReasoningScore

Conciseness

The body is lean — a one-line intro ("Mediabunny is a multimedia library for dealing with audio and video in the browser"), an external overview link, and three short pointer sections. It falls short of anchor 5 because each "See [X](X) for getting the duration of an audio file in seconds..." line merely restates its heading, and the intro sentence is marginal padding for a skill whose tasks are self-explanatory from the section titles. It is above anchor 3 because there is no real over-explanation or concept-teaching.

4 / 5

Actionability

As written, the body offers only task-level pointers ("See [get-audio-duration.md](get-audio-duration.md) for getting the duration of an audio file in seconds") with zero code, commands, or steps — anchor 2's "high-level hints but missing the specific steps to execute." Critically, none of the three referenced .md files exist in the bundle (only assets/remotion-icon.png is present), so there is no executable guidance anywhere. It is above anchor 1 because the pointers are concrete, file-per-task navigation rather than abstract advice, and below anchor 3 because no partial executable code or commands exist.

2 / 5

Workflow Clarity

The three single-task sections (audio duration, video dimensions, video duration) are cleanly separated and trivially sequenced, and the operations are read-only so no validation loop is required. However, every task dead-ends at a missing reference file, so the simple-skill exception (score 5 for an unambiguous single action) cannot apply — the action cannot actually be completed from the bundle. Anchor 3 fits: structure present, but the guidance cannot be executed as delivered; it is above anchor 2 because sections are clear and well-defined, not vague.

3 / 5

Progressive Disclosure

The pattern attempted is ideal (concise overview plus clearly signaled, one-level-deep references per task), but scored against the actual bundle structure, all three referenced files are absent — every reference is a dead link, leaving no instructional content at any level. This matches anchor 2's "minimal structure" outcome: navigation as delivered is broken and delivers no content. It is above anchor 1 because the SKILL.md itself is well-sectioned with clearly signaled (if non-existent) targets, and below anchor 3/4 because the referenced detail layer simply does not exist.

2 / 5

Total

11

/

20

Passed

Description

28%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 "Interacting with Mediabunny" is barely above the bad-overall example tier: it names the library but states no concrete capability, includes no natural trigger terms, and omits any 'when to use' guidance. It reads like a placeholder rather than a functional skill description.

Suggestions

List the concrete actions the skill performs, e.g., "Get audio duration in seconds, read video dimensions (width/height), and get video duration from media files using Mediabunny."

Add an explicit trigger clause, e.g., "Use when working with audio/video files in the browser, or when the user mentions media durations, video dimensions, or Mediabunny."

Resolve the name/description mismatch (frontmatter name "remotion-multimedia" vs. description about Mediabunny) so the skill is distinct from any Remotion-related skill.

DimensionReasoningScore

Specificity

The entire description is "Interacting with Mediabunny" — it names the domain (the Mediabunny library) but the sole action, "Interacting with", is more generic than the anchor-2 example "Processes PDF files". It does not reach anchor 3 because no concrete action (e.g., extracting audio duration, reading video dimensions) is stated, and it is above anchor 1 because the domain is at least explicitly named.

2 / 5

Completeness

The 'what' is vague ("Interacting with Mediabunny" states no capability) and the 'when' is entirely absent — there is no 'Use when...' clause or equivalent, which alone caps completeness at 3 per the judging guidelines, and the vague 'what' pushes it to anchor 2. It is above anchor 1 because a domain is at least identifiable, and below anchor 3 because the stated capability is not concrete.

2 / 5

Trigger Term Quality

The only keyword is the library's proper name "Mediabunny", which is technical jargon users would only say if they already knew the library. All natural phrases users would actually say when needing this skill — "audio duration", "video dimensions", "get video length", "media files", file extensions like .mp4/.wav — are missing, matching anchor 2 ("one or two generic keywords; missing the natural phrases users say").

2 / 5

Distinctiveness Conflict Risk

Naming a specific library ("Mediabunny") makes it somewhat distinguishable, fitting anchor 3 ("somewhat specific but could still overlap with similar skills") — a generic action verb plus a broad audio/video/browser domain means any Mediabunny or media-file task would trigger it, and the frontmatter name "remotion-multimedia" vs. the description's "Mediabunny" introduces further ambiguity against sibling media skills. It is below anchor 4, whose example distinguishes by naming the concrete formats worked on.

3 / 5

Total

9

/

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

Warning

Total

14

/

16

Passed

Repository

remotion-dev/remotion

Path

packages/codex-plugin/skills/remotion-multimedia/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.