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:Dicklesworthstone/pi_agent_rust --skill dependency-upgrade90
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 simple 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 solid, actionable skill with excellent workflow clarity and executable examples. The main weakness is verbosity - it includes content Claude already knows (semver basics, obvious use cases) and could benefit from moving detailed sections like the compatibility matrix and testing examples to reference files. The three-phase upgrade strategy with validation checkpoints is well-designed.
Suggestions
Remove the 'When to Use This Skill' section and semantic versioning review - Claude knows these concepts
Move the detailed compatibility matrix, testing strategy examples, and automated update configurations to separate reference files to reduce main file length
Consolidate 'Best Practices' and 'Common Pitfalls' into the checklist to avoid redundancy
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is comprehensive but includes some unnecessary content like the 'When to Use This Skill' section listing obvious use cases, and the semantic versioning review which Claude already knows. The best practices and common pitfalls sections are somewhat redundant with the checklist. | 2 / 3 |
Actionability | Provides fully executable code examples throughout - bash commands, JavaScript code, configuration files (renovate.json, dependabot.yml), and shell scripts. Commands are copy-paste ready with specific package names and flags. | 3 / 3 |
Workflow Clarity | Clear three-phase upgrade strategy (Planning, Incremental Updates, Validation) with explicit validation steps after each upgrade. The rollback plan includes conditional logic for failure handling, and the checklist provides explicit checkpoints for pre/during/post upgrade phases. | 3 / 3 |
Progressive Disclosure | References external files (references/semver.md, assets/upgrade-checklist.md, scripts/) which is good, but the main file is quite long (~300 lines) with content that could be split out. The compatibility matrix and testing strategy sections could be separate reference files. | 2 / 3 |
Total | 10 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- 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.