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.75x

Quality

—

Does it follow best practices?

Impact

79%

1.75x

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.

The body is rich with executable commands and a well-sequenced staged-upgrade workflow with rollback, but it is verbose with concept restatements, contains a few incomplete code stubs, and references bundle files that are absent while duplicating that content inline.

Suggestions

Remove or relocate the 'Semantic Versioning Review' basics block — Claude already knows MAJOR.MINOR.PATCH and the ^/~ ranges; keep only non-obvious project-specific guidance.

Complete or delete the stubbed code: fill in checkCompatibility and the empty test bodies, or replace them with concrete executable commands.

Either create the referenced bundle files (references/*.md, assets/*, scripts/audit-dependencies.sh) and move the inline semver/compatibility/testing detail into them, or remove the Resources section so links are not broken.

Dimension	Reasoning	Score
Conciseness	The body is mostly commands, but the "Semantic Versioning Review" section restates basics Claude already knows ("MAJOR: Breaking changes", "^2.3.1 = >=2.3.1 <3.0.0"), and the ~430-line sprawl could be tightened, matching 'mostly efficient but includes some unnecessary explanation'.	2 / 3
Actionability	Many copy-paste-ready commands exist (npm outdated, npx jscodeshift), but incomplete stubs like "function checkCompatibility(packages) { // Validate package versions against matrix }" and test bodies with only "// Run npm ls and check for warnings" keep it from fully executable, matching 'some concrete guidance but incomplete'.	2 / 3
Workflow Clarity	The Staged Upgrade Strategy sequences Phase 1/2/3 with explicit test checkpoints after each step ("npm run test", "npm run build"), the rollback.sh provides a test-fail feedback loop, and an Upgrade Checklist is included, matching 'clear sequence with explicit validation steps; feedback loops; checklists'.	3 / 3
Progressive Disclosure	A Resources section lists references/assets/scripts, but those directories and files do not exist, so the links are broken; meanwhile content that should live in those references (semver guide, compatibility matrix, testing strategy) is duplicated inline, matching 'content that should be separate is inline' and references that are not reliably signaled.	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 strong, third-person description that clearly states concrete capabilities and provides explicit 'Use when' triggers with natural language. It answers both what the skill does and when to invoke it without fluff or over-claims.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — "compatibility analysis", "staged rollout", and "comprehensive testing" — rather than vague language, matching the 'lists multiple specific concrete actions' anchor.	3 / 3
Completeness	It explicitly answers both what ("Manage major dependency version upgrades with compatibility analysis, staged rollout, and comprehensive testing") and when ("Use when upgrading framework versions...") 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 uses natural phrasings a user would actually say, giving good coverage of common variations.	3 / 3
Distinctiveness Conflict Risk	The major-version-upgrade niche with breaking-change triggers is clearly distinguishable from general package management skills and unlikely to fire for the wrong skill.	3 / 3
	Total	12 / 12 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
referenced_paths_exist	Referenced path issues: 7 missing	Warning

	Total	15 / 16 Passed

Repository: Dicklesworthstone/pi_agent_rust
Commit: e9f9b67

Reviewed: 4 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.