upgrade-caniuse

Upgrade the caniuse-lite override in the Remotion repo. Use when asked to update caniuse-lite to the latest npm version.

Quality

81%

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

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.

An admirably lean, actionable checklist for a narrow task, hurt mainly by sequencing and validation gaps: the version lookup is ordered after the edit it depends on, and there is no verification step between installing and committing/pushing to main. Progressive disclosure is a non-issue at this size.

Suggestions

Reorder the steps so the npm version lookup (e.g. `npm view caniuse-lite version`) comes before editing `package.json`, since the edit depends on the discovered version.

Add a validation checkpoint before committing, e.g. confirm `bun i` succeeded and `bun pm ls caniuse-lite` shows the overridden version resolved.

Make the version lookup and commit steps copy-paste ready with concrete commands (`npm view caniuse-lite version`, `git commit -m "Upgrade caniuse-lite to <version>"`).

Dimension	Reasoning	Score
Conciseness	Five terse bullets with zero padding and no explanation of concepts Claude already knows (no "what is caniuse-lite" filler). Every token earns its place, matching the 'lean and efficient' anchor exactly.	5 / 5
Actionability	Most steps are executable (edit `overrides` in root `package.json`, run `bun i`, commit with a given message format), but "Look up the latest version with npm" gives no command (e.g. `npm view caniuse-lite version`), and no git command is spelled out. This is the 'concrete commands with minor gaps' of anchor 4 rather than the copy-paste-ready coverage of anchor 5.	4 / 5
Workflow Clarity	Steps are listed but the sequence is flawed: it says to update `caniuse-lite` to the latest version (bullet 2) before looking up what the latest version is (bullet 3). There are also no validation checkpoints (e.g. confirm `bun i` succeeds and the override resolves) before committing and pushing to main, which fits anchor 3 rather than 4.	3 / 5
Progressive Disclosure	This is a simple, single-purpose skill well under 50 lines with no bundle files, and the flat bullet list is clear and appropriately sized for SKILL.md. Per the simple-skill note, it earns a 5 with no external references needed.	5 / 5
	Total	17 / 20 Passed

Description

82%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 tight, well-formed description: explicit what and an explicit 'Use when' trigger with natural user phrasing, plus a distinct niche that is unlikely to misfire. The only weakness is that it names a single action rather than enumerating the upgrade workflow's capabilities.

Dimension	Reasoning	Score
Specificity	"Upgrade the caniuse-lite override in the Remotion repo" names the domain and one concrete action but lists nothing further (no mention of running installs, committing, etc.). It matches anchor 3 ('names domain and 1-2 concrete actions') rather than 4, which requires several specific actions.	3 / 5
Completeness	It explicitly answers both questions: the what is "Upgrade the caniuse-lite override in the Remotion repo" and the when is a literal "Use when..." clause with a concrete trigger phrase. This matches anchor 5; anchor 4 would require the 'when' to be less explicit than it is.	5 / 5
Trigger Term Quality	"Use when asked to update caniuse-lite to the latest npm version" contains the natural phrases a user would actually say ("update caniuse-lite", "latest npm version"). A few natural terms are missing (e.g. "browserslist", "override", "bump"), so it stops short of the comprehensive synonym coverage of anchor 5.	4 / 5
Distinctiveness Conflict Risk	The description is tied to a uniquely named package (caniuse-lite) in a named repo (Remotion), giving it a clear niche with distinct triggers and minimal conflict risk, matching anchor 5. There is no plausible overlap with a neighboring skill given this specificity.	5 / 5
	Total	17 / 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-caniuse/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.