Skip to content
TrustedSkillsbeta
Back to all skills

Dependency Upgrade

Checked
wshobson·vlatest·backend·MIT

Automatically identifies and suggests upgrading outdated dependencies in your project for improved security and stability.

Repository

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

  1. 1

    Run this in your project

    terminal
    $ npx skills add wshobson/agents --skill dependency-upgrade -a claude-code

  2. Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

wshobson

Taken from the source listing. We haven't verified who controls this account.

Install target

Live repository

Not pinned. Installing fetches whatever the repository holds at the time you run the command.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.

  • Declares what it does: passed

    SKILL.md parses and declares a name and a description.

    SKILL.md exists, its frontmatter parses, and it declares a name and a description.

  • No undeclared network calls: passed

    Only contacts known or declared hosts: raw.githubusercontent.com.

    Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.

    Hosts contacted

    raw.githubusercontent.comsource host

  • No obfuscated payloads: passed

    No encoded or obfuscated payloads.

    No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.

  • No credential access: passed

    Reads no keys, tokens, keychains or credential files.

    Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.

  • No pipe-to-shell installers: passed

    No pipe-to-shell or download-and-run installers.

    No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.

  • Pinned to a commit: passed

    Scanned wshobson/agents at 46891e7e60.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Commit
46891e7e60
Manifest
plugins/framework-migration/skills/dependency-upgrade/SKILL.md
Scanned
1 file, 329 lines
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

What it does

The dependency-upgrade skill helps identify and upgrade outdated dependencies in software projects, ensuring compatibility with newer versions of libraries or frameworks. It scans project files to detect current dependency versions and suggests updated alternatives that maintain functionality while improving performance or security.

When to use it

  • Before deploying a new version of an application to ensure all dependencies are up-to-date.
  • After identifying vulnerabilities in third-party libraries through a security audit.
  • When integrating a new feature that requires a newer version of a library.
  • During continuous integration pipelines to automate dependency management.

Key capabilities

  • Scans project files for existing dependencies.
  • Identifies outdated or vulnerable versions.
  • Suggests compatible upgrades with minimal breaking changes.
  • Provides upgrade instructions and potential impact analysis.

Example prompts

  • "Upgrade all npm packages in my React app to their latest stable versions."
  • "Check if the Python libraries in this project have known security issues and suggest updates."
  • "Find compatible replacements for deprecated dependencies in my Node.js application."

Tips & gotchas

  • Ensure your project has a dependency manifest file (e.g., package.json, requirements.txt) for accurate scanning.
  • Some upgrades may require code changes; review suggested updates carefully before applying them.