Name: dependency-upgrade
Rating: 50.4 (1 reviews)
Author: administrakt0r

dependency-upgrade

Master major dependency version upgrades, compatibility analysis, staged upgrade strategies, and comprehensive testing approaches.

Quality

55%

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 ./plugins/AI-Agents-Safe-Coding-Skills-claude/skills/dependency-upgrade/SKILL.md

The canonical home for this skill is dependency-upgrade in administrakt0r/AI-Agents-Safe-Coding-Skills

Quality

Content

52%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 skill is highly actionable with concrete, executable commands and a well-sequenced staged upgrade workflow, but it is verbose and inlines substantial content that should live in separate reference files that do not actually exist in the bundle.

Suggestions

Move the inlined compatibility matrix, migration script, renovate/dependabot configs, full test suites, and checklist into the referenced files under references/ and assets/, keeping SKILL.md a lean overview — and actually create those files so the references resolve.

Remove the basic semver tutorial (MAJOR/MINOR/PATCH, ^/~ semantics) that Claude already knows, or relocate it to references/semver.md.

Reconcile the reference path mismatch: the Instructions section says 'resources/implementation-playbook.md' while the Resources section lists 'references/*.md' — pick one consistent directory naming scheme.

Dimension	Reasoning	Score
Conciseness	The ~425-line body inlines entire config files (renovate.json, dependabot.yml), full test suites, a migration script, and a compatibility matrix, and explains semver basics ('MAJOR: Breaking changes', '^2.3.1 = >=2.3.1 <3.0.0') that Claude already knows — matching the score-2 anchor 'Noticeably verbose; several unnecessary explanations or padded sections'; not a 1 because most code is concrete and useful rather than pure padding.	2 / 5
Actionability	Provides copy-paste-ready commands (npm outdated, npx npm-check-updates, codemod invocations) and complete config snippets, matching score-4 'Mostly executable guidance; concrete code or commands with minor gaps'; kept off 5 by incomplete pseudocode such as checkCompatibility's '// Validate package versions against matrix' stub.	4 / 5
Workflow Clarity	The Staged Upgrade Strategy sequences Planning -> Incremental Updates -> Validation with explicit 'Test' checkpoints after each step, and the Rollback Plan branches on `if npm run test`, satisfying validation for these destructive/batch operations — matching score-4 'Clear sequence with most checkpoints present'; not 5 because some phases rely on comments ('# Test again') rather than explicit validate-then-fix feedback loops.	4 / 5
Progressive Disclosure	The body inlines large reference-type content (full configs, test files, matrices, checklist) that clearly belongs in separate files, and its Resources section lists references/, assets/, scripts/ paths plus an instruction to open 'resources/implementation-playbook.md' — but none of those directories or files exist and the path prefix is inconsistent ('resources/' vs 'references/'), matching score-2 'content that clearly belongs in separate files is inlined'.	2 / 5
	Total	12 / 20 Passed

Description

58%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 clearly communicates what the skill does with several concrete capability areas, but lacks an explicit 'Use when...' trigger clause, which caps completeness. Trigger term coverage is decent but missing common user phrasings.

Suggestions

Add an explicit 'Use when...' clause naming concrete trigger scenarios, e.g. 'Use when upgrading major framework versions, resolving npm peer-dependency conflicts, or migrating past breaking changes.'

Include natural user-facing keywords and synonyms like 'npm', 'package.json', 'security vulnerability', and 'breaking changes' to improve trigger matching.

Convert the thematic capability areas into more enumerated concrete operations to push specificity toward 5.

Dimension	Reasoning	Score
Specificity	Quotes 'major dependency version upgrades, compatibility analysis, staged upgrade strategies, and comprehensive testing approaches' — lists several concrete capability areas, matching the score-4 anchor 'Lists several specific actions; minor gaps in coverage'; not a 5 because the actions are stated as themes rather than fully enumerated concrete operations.	4 / 5
Completeness	The 'what' is clearly stated but there is no 'Use when...' clause or equivalent explicit trigger guidance, so per the rubric guideline completeness is capped at 3 ('Has a clear what but when is missing or only weakly implied').	3 / 5
Trigger Term Quality	Contains relevant natural terms like 'dependency version upgrades' and 'compatibility analysis' but misses common variations users actually say (npm, package.json, security vulnerability, breaking changes, migration); fits the score-3 anchor 'Some relevant keywords but missing common variations or synonyms'.	3 / 5
Distinctiveness Conflict Risk	'Major dependency version upgrades' is a fairly clear niche with minor overlap risk against generic package-management skills, matching the score-4 anchor 'Mostly distinct; minor overlap risk with closely related skills'; not a 5 because the phrasing stays somewhat thematic.	4 / 5
	Total	14 / 20 Passed

Validation

87%

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

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning
referenced_paths_exist	Referenced path issues: 7 missing	Warning

	Total	14 / 16 Passed

Repository: administrakt0r/AI-Agents-Safe-Coding-Skills
Path: plugins/AI-Agents-Safe-Coding-Skills-claude/skills/dependency-upgrade/SKILL.md
Commit: 57c135b

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