upgrade-mediabunny

Upgrade Mediabunny and related @mediabunny packages across the Remotion repo. Use when asked to update Mediabunny to the latest version.

Quality

76%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/upgrade-mediabunny/SKILL.md

Quality

Content

80%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.

A tight, repo-specific runbook that gets straight to exact paths and commands with no wasted tokens. It loses points for missing validation on a batch multi-file edit and for leaving the compatibility-table and extraPackages edits underspecified.

Suggestions

Add a verification step after the edits, e.g. grep the repo for stale Mediabunny versions ("grep -rn '<old-version>' packages/ package.json") or re-run "npm view mediabunny version" and diff against every updated file, so the batch edit is validated before finishing.

Specify the shape of the compatibility-table row in packages/docs/docs/mediabunny/version.mdx (what columns/entries to add and which version to pair with the incremented patch version) so that step is unambiguous.

Clarify what the extraPackages entries in packages/studio-shared/src/package-info.ts and packages/cli/src/extra-packages.ts should look like after the edit (a concrete before/after example would close the remaining actionability gap).

Dimension	Reasoning	Score
Conciseness	Eight lean bullets with zero padding — every line carries non-obvious repo-specific knowledge (catalog vs. explicit versions, the extra-packages.ts and package-info.ts locations, the patch-increment rule). It fully assumes Claude's competence and explains nothing it already knows.	5 / 5
Actionability	Concrete commands ("npm view mediabunny version", "bun i") and exact file paths ("packages/cli/src/extra-packages.ts", "packages/template-*/package.json") make most steps executable. Not a 5 because the compatibility-table step ("Update the compatibility table in packages/docs/docs/mediabunny/version.mdx") and the extraPackages edits leave the exact edit shape unspecified — minor gaps.	4 / 5
Workflow Clarity	The steps are listed in a coherent order, but this is a batch operation editing at least five locations across many template packages with no validation or verification step (no grep to confirm all versions match, no build/test after "bun i"). Per the rubric, a batch workflow without validation is capped at 3, which overrides the simple-skill exception.	3 / 5
Progressive Disclosure	Under 50 lines, single-purpose, no bundle files exist and none are needed; the flat ordered checklist is appropriately organized for a skill of this size, matching the rubric's simple-skill exception for progressive disclosure.	5 / 5
	Total	17 / 20 Passed

Description

73%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.

A strong description with an explicit trigger clause, correct imperative voice, and excellent distinctiveness from the specific package and repo names. Its main weaknesses are single-verb coverage of the 'what' and missing natural trigger variations such as 'bump'.

Dimension	Reasoning	Score
Specificity	"Upgrade Mediabunny and related @mediabunny packages across the Remotion repo" names the domain and essentially one action (upgrade) with concrete targets, but does not list several distinct actions — closer to the 'names domain and 1-2 concrete actions, but not comprehensive' anchor than to the 'lists several specific actions' anchor.	3 / 5
Completeness	Both halves are present: a clear 'what' ("Upgrade Mediabunny and related @mediabunny packages across the Remotion repo") and an explicit 'when' ("Use when asked to update Mediabunny to the latest version"). Not a 5 because the 'when' is narrow (only the update-to-latest phrasing) and the 'what' omits scope elements like the docs compatibility table and dependency reinstall.	4 / 5
Trigger Term Quality	"Use when asked to update Mediabunny to the latest version" captures the natural phrases a user would say ("update Mediabunny", "upgrade Mediabunny", "latest version"), but misses common variations like "bump", "bump the mediabunny dependency", or "mediabunny is out of date" — a few natural terms missing, matching the anchor-4 example.	4 / 5
Distinctiveness Conflict Risk	"Mediabunny", "@mediabunny packages", and "Remotion repo" form a clear niche with distinct triggers that no generic dependency-management or versioning skill would collide with — minimal conflict risk.	5 / 5
	Total	16 / 20 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: remotion-dev/remotion
Path: .agents/skills/upgrade-mediabunny/SKILL.md
Commit: 6f4e0d5

Reviewed: 5 days ago

Table of Contents

Discovery Implementation Validation

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.