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.

Quality

88%

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

77%

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 in executable, actionable guidance with a clear staged workflow and validation checkpoints, but it is verbose with redundant/generic sections and relies on a monolithic structure whose advertised bundle files are missing.

Suggestions

Move the semantic-versioning primer, compatibility matrix, and detailed test strategy into the referenced files (references/semver.md, references/compatibility-matrix.md, references/testing-strategy.md) and either create those files or remove the dangling 'Resources' entries.

Trim generic filler — the 'Do not use this skill when', 'Instructions', 'Best Practices', and 'Common Pitfalls' sections repeat content already conveyed by the staged workflow and checklist.

Remove or justify the duplicated 'Upgrade Checklist' section that reiterates the Pre/During/Post steps already covered in 'Staged Upgrade Strategy'.

Dimension	Reasoning	Score
Conciseness	Mostly concrete but padded: the 'Semantic Versioning Review' explains MAJOR.MINOR.PATCH and ^/~ semantics Claude already knows, and generic boilerplate sections ('Do not use this skill when', 'Instructions', 'Best Practices', 'Common Pitfalls') plus a duplicate 'Upgrade Checklist' could be tightened.	2 / 3
Actionability	Provides numerous copy-paste-ready commands and configs (npm audit/install, react-codeshift codemods, renovate.json, dependabot.yml, rollback.sh, test suites); a couple of minor stubs (checkCompatibility, an empty peer-dep test) do not undermine the overall executability.	3 / 3
Workflow Clarity	The Staged Upgrade Strategy sequences Planning → Incremental Updates → Validation with explicit 'Test' checkpoints after each upgrade and a rollback.sh feedback loop (test fails → restore), matching the level-3 anchor.	3 / 3
Progressive Disclosure	Content that belongs in separate files (semver guide, compatibility matrix, full test strategy) is inlined into one ~420-line SKILL.md, and the 'Resources' section lists references/, assets/, and scripts/ files that do not exist on disk — broken, dangling references despite clear signaling.	2 / 3
	Total	10 / 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.

The description is concise, specific, and includes an explicit 'Use when' trigger clause covering natural phrasings. It clearly states both capabilities and invocation conditions with no over-claims.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'Manage major dependency version upgrades with compatibility analysis, staged rollout, and comprehensive testing' — matching the level-3 anchor of several specific actions.	3 / 3
Completeness	Explicitly answers both what (manage upgrades, compatibility analysis, staged rollout, testing) and when via the 'Use when...' clause, matching the level-3 anchor.	3 / 3
Trigger Term Quality	Natural trigger phrases users would say are well covered: 'upgrading framework versions', 'updating major dependencies', and 'managing breaking changes in libraries'.	3 / 3
Distinctiveness Conflict Risk	Occupies a clear niche (major dependency upgrades) with distinct triggers unlikely to fire for unrelated skills.	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: rmyndharis/antigravity-skills
Path: skills/dependency-upgrade/SKILL.md
Commit: e63f7dd

Reviewed: about 3 hours 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.