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

73%

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 ./skills/dependency-upgrade/SKILL.md

Quality

Content

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

The body is rich with executable examples and a well-sequenced staged-upgrade workflow, but it is undermined by generic boilerplate sections and references to bundle files that do not actually exist. Delivering the referenced files and trimming boilerplate would meaningfully raise quality.

Suggestions

Create the referenced bundle files (references/semver.md, references/compatibility-matrix.md, references/staged-upgrades.md, references/testing-strategy.md, assets/upgrade-checklist.md, assets/compatibility-matrix.csv, scripts/audit-dependencies.sh) and move the inline tables/checklists into them so progressive disclosure is real rather than promised.

Remove the generic 'Instructions' boilerplate ('Clarify goals... Apply relevant best practices... Provide actionable steps') and the 'Do not use this skill when'/'Use this skill when' sections that duplicate the description's triggers.

Complete the stub code blocks: implement checkCompatibility() and fill in the 'should not have peer dependency warnings' test, and fix the rollback block which is bash mislabeled as a JavaScript snippet.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with concrete code blocks, but it includes padded boilerplate ('Clarify goals, constraints... Apply relevant best practices...') and duplicate trigger lists ('Use this skill when' mirrors the description) that could be trimmed.	3 / 5
Actionability	Provides many concrete, executable commands and configs, but a few blocks are stubs (empty 'checkCompatibility' body, an empty peer-dependency test body) leaving minor gaps.	4 / 5
Workflow Clarity	The staged upgrade strategy has a clear three-phase sequence with test-after-each-step checkpoints and a rollback plan with validation feedback, though some checkpoints are implicit rather than bolded validation gates.	4 / 5
Progressive Disclosure	The Resources section references references/.md, assets/, and scripts/audit-dependencies.sh, but none of these bundle files exist, so the promised one-level-deep structure is not delivered and large reference material is inlined.	2 / 5
	Total	13 / 20 Passed

Description

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

The description is specific, third-person, and explicitly pairs what the skill does with concrete when-to-use triggers. It is a strong, well-scoped description with only minor room for broader keyword coverage.

Dimension	Reasoning	Score
Specificity	Names the domain and three concrete actions ('compatibility analysis, staged rollout, and comprehensive testing') rather than vague language, but coverage is not fully comprehensive.	4 / 5
Completeness	Clearly answers 'what' (manage major dependency version upgrades with compatibility analysis, staged rollout, testing) and explicitly answers 'when' with a 'Use when' clause and concrete trigger phrases.	5 / 5
Trigger Term Quality	Includes natural phrases users would say ('upgrading framework versions', 'updating major dependencies', 'breaking changes in libraries'), though it misses common synonyms like 'package updates' or ecosystem names like npm/yarn.	4 / 5
Distinctiveness Conflict Risk	Occupies a clear niche (major dependency upgrades) with distinct triggers unlikely to collide with other skills, and minimal overlap risk.	5 / 5
	Total	18 / 20 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: 3eff4af

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.