Skill package dependency management

Skill zavora-ai/skill-package-dependency-management

Manage package dependencies — lookup packages, check versions, review changelogs, assess compatibility, analyze lockfiles, and propose upgrades. Use when updating dependencies, checking for outdated packages, planning major upgrades, reviewing changelogs, or auditing dependency health.From its SKILL.md

Install

npx -y skills add zavora-ai/skill-package-dependency-management

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its file declares

Copied from the file, not written here

The file declares its own license as Apache-2.0. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.

SKILL.md

2.1 KB, 325 tokens by cl100k_base, as published. Nobody here has run it

Package & Dependency Management

You manage dependencies safely. Check changelogs before upgrading, verify compatibility, and prioritize security fixes over feature upgrades.

Decision Tree

├── "outdated", "update", "upgrade"? → analyze_lockfile + propose_upgrades
├── "changelog", "what changed"? → get_changelog
├── "compatible", "will it break"? → check_compatibility
├── "vulnerable", "advisory"? → check_advisories
├── "info", "about package"? → lookup_package / list_versions

Key Workflows

Safe Upgrade Plan (3 calls)

analyze_lockfile(path: "Cargo.lock") → outdated + vulnerable deps
propose_upgrades(strategy: "security_first") → prioritized upgrade plan
check_compatibility(package, from_version, to_version) → breaking changes?

Changelog Review (2 calls)

list_versions(package: "serde") → all versions
get_changelog(package: "serde", from: "1.0.190", to: "1.0.200") → what changed

MUST DO

Review changelogs for breaking changes before major upgrades
Prioritize security advisories over feature upgrades
Pin exact versions in production
Check transitive dependency impact

MUST NOT DO

Never upgrade production deps without testing
Don't use floating version ranges in production
Don't ignore breaking change warnings

What ships with it: 8 files

6.2 KB alongside SKILL.md, 1 of them executable

assets/

dependency-report.md797 B

references/

scripts/

upgrade_plan.pyruns872 B