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.
Install with Tessl CLI
npx tessl i github:secondsky/claude-skills --skill dependency-upgradeOverall
score
88%
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Discovery
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.
This is a well-crafted skill description that follows best practices. It uses third person voice, lists specific capabilities, includes an explicit 'Use when...' clause with natural trigger terms, and carves out a distinct niche around major dependency upgrades rather than general package management.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'compatibility analysis', 'staged rollout', and 'comprehensive testing' for dependency upgrades. These are clear, actionable capabilities. | 3 / 3 |
Completeness | Clearly answers both what ('Manage major dependency version upgrades with compatibility analysis, staged rollout, and comprehensive testing') and when ('Use when upgrading framework versions, updating major dependencies, or managing breaking changes in libraries'). | 3 / 3 |
Trigger Term Quality | Includes natural keywords users would say: 'upgrading framework versions', 'updating major dependencies', 'breaking changes', 'libraries'. These are terms developers naturally use when facing upgrade tasks. | 3 / 3 |
Distinctiveness Conflict Risk | Clear niche focused specifically on major version upgrades and breaking changes. Distinct from general dependency management or package installation skills through its focus on compatibility analysis and staged rollout. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured, highly actionable skill with excellent workflow clarity and comprehensive testing strategies. The main weaknesses are verbosity (explaining concepts Claude knows, dual npm/bun examples throughout) and a monolithic structure that could benefit from moving detailed examples to reference files. The upgrade checklist and rollback plan are particularly strong.
Suggestions
Remove the semantic versioning review section - Claude already understands semver
Consolidate npm/bun examples by showing Bun as primary with a brief note that npm equivalents exist, rather than showing both every time
Move the detailed compatibility matrix JavaScript and testing strategy examples to reference files, keeping only quick-start examples inline
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is comprehensive but includes some unnecessary verbosity like the 'When to Use This Skill' section listing obvious use cases, and the semantic versioning review which Claude already knows. The dual npm/bun examples throughout add redundancy. | 2 / 3 |
Actionability | Provides fully executable code examples throughout - bash commands, JavaScript test files, configuration files (renovate.json, dependabot.yml), and migration scripts. All examples are copy-paste ready with specific package names and realistic scenarios. | 3 / 3 |
Workflow Clarity | Excellent multi-phase workflow (Planning → Incremental Updates → Validation) with explicit validation checkpoints ('Test again', 'Run test suite after each upgrade'). Includes rollback plan with conditional logic and comprehensive pre/during/post upgrade checklist. | 3 / 3 |
Progressive Disclosure | References external files (references/semver.md, assets/upgrade-checklist.md, scripts/) but the main content is quite long and monolithic. Some sections like the full compatibility matrix JavaScript and testing examples could be moved to reference files. | 2 / 3 |
Total | 10 / 12 Passed |
Validation
87%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 |
|---|---|---|
metadata_version | 'metadata' field is not a dictionary | Warning |
body_output_format | No obvious output/return/format terms detected; consider specifying expected outputs | Warning |
Total | 14 / 16 Passed | |
- Reviewed
Table of Contents
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.