dependency-upgrade

Manage major dependency version upgrades with compatibility analysis, staged rollout, and comprehensive testing. Use when upgrading framework versions, updating major dependencies, or managing breaking changes in libraries.

1.05x

Quality

—

Does it follow best practices?

Impact

91%

1.05x

Average score across 3 eval scenarios

Securityby

Advisory

Suggest reviewing before use

Quality

Content

62%

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

A well-organized, mostly actionable reference with strong workflow sequencing and rollback feedback loops. Its main weaknesses are a redundant semver tutorial, a few incomplete code stubs, and a monolithic structure that would benefit from splitting detailed material into reference files.

Suggestions

Remove or shrink the "Semantic Versioning Review" section and the duplicated "When to Use This Skill" list — Claude already knows semver and the frontmatter already states triggers.

Fill in the stubbed examples (checkCompatibility body and the peer-dependency-warning test) or drop them, so every code block is fully executable.

Move the large detailed blocks (compatibility matrix, testing examples, Renovate/Dependabot configs) into reference files under references/ and link to them one level deep from SKILL.md.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient command/code blocks, but the "Semantic Versioning Review" section explains MAJOR.MINOR.PATCH and ^/~ operators that Claude already knows, and the "When to Use This Skill" list restates the frontmatter — unnecessary padding that keeps it below level 3.	2 / 3
Actionability	Most sections give concrete, copy-paste commands, but several examples are incomplete stubs — checkCompatibility has only "// Validate package versions against matrix" and the peer-dependency test body is an empty comment — so the code is not fully executable as the level-3 anchor requires.	2 / 3
Workflow Clarity	The Staged Upgrade Strategy sequences Planning → Incremental Updates → Validation with test checkpoints after each step, and the Rollback Plan provides an explicit feedback loop (run tests; on failure, revert branch and restore lockfile), matching the level-3 anchor of clear sequence with validation and error recovery.	3 / 3
Progressive Disclosure	The ~360-line body is a monolithic single file with no bundle references; content that could be split (compatibility matrix, testing strategy, automated-update configs) is all inline, fitting the level-2 anchor of present structure but content that should be separate kept inline.	2 / 3
	Total	9 / 12 Passed

Description

100%

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 concise, third-person description that cleanly states both capability and explicit triggers. It is specific, uses natural trigger terms, and occupies a distinct niche with low conflict risk.

Dimension	Reasoning	Score
Specificity	"Manage major dependency version upgrades with compatibility analysis, staged rollout, and comprehensive testing" names the domain plus multiple concrete actions (compatibility analysis, staged rollout, testing), matching the level-3 anchor of listing several specific concrete actions.	3 / 3
Completeness	It explicitly answers both what (manage upgrades with compatibility analysis, staged rollout, testing) and when (Use when upgrading framework versions, updating major dependencies, managing breaking changes), satisfying the level-3 anchor with an explicit trigger clause.	3 / 3
Trigger Term Quality	The "Use when upgrading framework versions, updating major dependencies, or managing breaking changes in libraries" clause covers natural phrasings a user would actually say, giving good coverage of common variations rather than jargon.	3 / 3
Distinctiveness Conflict Risk	The major-version-upgrade niche with breaking-change triggers is clearly distinguishable from adjacent skills and unlikely to fire for the wrong skill, matching the level-3 clear-niche anchor.	3 / 3
	Total	12 / 12 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: wshobson/agents
Commit: d7cf7dc

Reviewed: 1 day 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.