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/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 content is highly actionable with concrete commands and a staged, validated upgrade workflow, but it is padded with redundant sections and explains concepts Claude already knows. More critically, its progressive disclosure is broken: referenced bundle files do not exist and paths are inconsistent while the same content is inlined.

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) or remove the broken 'Resources' section, and fix the inconsistent resources/ vs references/ path on line 23.

Move the inlined compatibility-matrix code, detailed test examples, and the upgrade checklist into the referenced files so SKILL.md stays a lean overview pointing one level deep.

Trim concepts Claude already knows (the semver ^/~/exact primer) and merge the overlapping 'Best Practices', 'Upgrade Checklist', and 'Common Pitfalls' sections to reduce padding.

Dimension	Reasoning	Score
Conciseness	The body is noticeably verbose: it explains semver basics Claude already knows (^/~ semantics), and the 'Best Practices', 'Upgrade Checklist', and 'Common Pitfalls' sections overlap heavily, plus generic 'Use this skill when'/'Do not use' filler.	2 / 5
Actionability	It provides mostly executable, concrete commands and config (npm outdated/audit, npm install react@17, renovate.json, dependabot.yml, rollback.sh), with minor gaps such as the empty checkCompatibility stub and illustrative-only test snippets.	4 / 5
Workflow Clarity	The Staged Upgrade Strategy gives a clear Phase 1/2/3 sequence with test checkpoints after each upgrade and a rollback feedback loop (test -> roll back on failure), but the validation phase leaves a stubbed peer-dep check and checkpoints are scattered rather than one integrated loop.	4 / 5
Progressive Disclosure	The Resources section references files in references/, assets/, and scripts/ that do not exist, and line 23 points to resources/implementation-playbook.md (inconsistent path); meanwhile compatibility matrices, test examples, and checklists that belong in those files are inlined into SKILL.md.	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 conveys a clear domain and several specific facets of dependency upgrades but omits any explicit "use when" trigger guidance and lacks the natural phrasings a user would actually say. It is a solid but incomplete description capped by the missing trigger clause.

Suggestions

Append a 'Use when...' clause with concrete trigger phrases, e.g. 'Use when upgrading major framework versions, resolving peer dependency conflicts, or planning incremental package upgrades.'

Add natural user-facing terms and synonyms (e.g. 'update packages', 'npm/yarn upgrade', 'breaking changes', 'peer dependencies', 'Renovate/Dependabot') to improve trigger term coverage.

Drop the filler verb 'Master' and lead with concrete third-person actions ('Upgrades major dependency versions, analyzes compatibility, plans staged upgrades...') to sharpen specificity.

Dimension	Reasoning	Score
Specificity	Lists several specific actions/aspects ("major dependency version upgrades, compatibility analysis, staged upgrade strategies, and comprehensive testing approaches") rather than vague language, though they read as phase categories more than granular concrete actions.	4 / 5
Completeness	It clearly states what the skill does but contains no "Use when..." clause or equivalent trigger guidance, so per the rubric cap completeness is held at 3.	3 / 5
Trigger Term Quality	It names relevant keywords ("dependency version upgrades", "compatibility", "staged upgrade", "testing") but misses common natural phrasings users actually say ("update packages", "npm upgrade", "breaking changes", "peer dependencies", "renovate/dependabot").	3 / 5
Distinctiveness Conflict Risk	The dependency-upgrade niche is mostly distinct with only minor overlap risk against general package-management or testing skills; not a 5 because the broad framing could still overlap with those.	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/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.