Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+21 more

    Dependency Update Planner

    1

    Analyze npm and Python dependencies to generate risk-aware, batched upgrade plans with live registry data.

    $2.99

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned
    Dependency Update Planner

    Dependency Update Planner

    Example session with this skill installed

    Analyze my package.json for pending updates and flag anything that hasn't been updated in over two years.

    • Read your context and instructions
    • Compiled the dependency update planner

    I have analyzed your package.json against the npm registry. I found 12 pending updates, including one abandoned package and two high-risk major version jumps.

    Dependency Upgrade Plan

    PackageCurrentLatestTypeAge DriftRisk / Status
    lodash4.17.154.17.21Patch840 daysStable
    axios0.21.11.6.7Major1,120 daysBreaking (0.x to 1.x)
    moment2.24.02.30.1Minor1,500 daysDeprecated (Use date-fns)
    left-pad1.3.01.3.0-2,200 daysAbandoned (No release >2yr)
    next13.0.014.1.0Major95 daysBreaking

    Batch 1: Low Risk (Patches)

    npm install lodash@4.17.21
    

    Batch 2: Significant Updates (Requires Testing)

    
    # Note: axios 1.x introduces breaking changes to error handling
    npm install axios@1.6.7 next@14.1.0
    

    Batch 3: Replacement Required

    • moment: Project is in maintenance mode. Plan migration to dayjs or date-fns.
    • left-pad: No updates since 2018. Evaluate if this utility is still necessary.

    Next steps

    1. Review the axios migration guide for changes to the error.response object.
    2. Run Batch 1 and execute your unit test suite.
    3. Schedule a refactor for the moment library to reduce bundle size and improve maintainability.

    Connects securely to your tools. The creator never sees your data.

    About this skill

    Outdated dependencies introduce technical debt and subtle bugs. Blindly running update commands often breaks builds due to unexpected breaking changes. This skill analyzes your project to build a risk-aware upgrade roadmap.

    What it does

    • Version Analysis identifies patch, minor, and major updates for npm and Python ecosystems.
    • Risk Assessment flags abandoned packages (2+ years stagnant) and bleeding-edge releases (under 7 days old).
    • Update Classification treats 0.x minor bumps as breaking changes to prevent semver accidents.
    • Drift Measurement calculates exactly how many days and versions each package trails the latest release.
    • Batched Execution generates ordered install commands to manage complex dependency chains.

    How it works

    1. Source Scan reads package.json, package-lock.json, requirements.txt, or pyproject.toml (Poetry/PEP 621).
    2. Registry Lookup queries npm and PyPI APIs for current version metadata and deprecation notices.
    3. Logic Application filters updates based on age, stability, and version delta.
    4. Plan Generation outputs a Markdown report with links to changelogs and exact shell commands.

    Frameworks & tools

    Supports Node.js (npm, yarn, pnpm) and Python (pip, Poetry). Uses public JSON APIs for registry.npmjs.org and pypi.org.

    Why this beats prompting it yourself

    Generic LLMs lack real-time registry data and often ignore the nuances of 0.x versioning. This skill integrates live API lookups to distinguish between a safe patch and a risky, unproven release.

    Use cases

    • Quarterly Maintenance to systematically reduce version drift across a monorepo.
    • Pre-release Hardening by identifying and replacing abandoned or deprecated libraries.
    • Incident Response to check if a local bug exists in a more recent, stable version.

    Known limitations

    Requires outbound network access to npm and PyPI registries. Does not perform local build testing or automated regression checks.

    Requires outbound network access to npm and PyPI. Does not execute local builds or run test suites to verify compatibility.

    How to use

    1. 1

      Connect your agent to the Agensi MCP

      Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup

    2. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before any payment.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill goes through the trust checks below.

    Security scanned

    Checked by our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    Money-back guarantee

    Doesn't do what its page promises? You get your money back.

    Trust & safety

    Security scan

    Security scan passed 1 month ago

    Requires

    Npmjs
    Pypi
    Python

    Permissions

    Terminal / Shell

    Allowed Hosts

    registry.npmjs.org
    pypi.org
    Listed1 month ago

    What's inside

    Frequently Asked Questions

    This skill performs live API queries against npm and PyPI registries to retrieve real-time metadata, whereas generic LLMs rely on training data that is months or years out of date. It also applies specific logic to treat 0.x version bumps as breaking changes, preventing the common stability issues that occur with standard automated updates.

    The skill supports Node.js projects using npm, yarn, or pnpm, as well as Python projects using pip (requirements.txt) or Poetry (pyproject.toml). It can process standard lockfiles to ensure its version drift calculations are based on your actual installed environment.

    No, this skill focuses on intelligent planning and risk assessment rather than execution. It generates a structured Markdown report with prioritized, batched shell commands that you can review and run manually or via your CI/CD pipeline to maintain full control over your codebase.

    The skill flags 'bleeding-edge' releases (less than 7 days old) and 'abandoned' packages (no updates in over 2 years). This allows you to avoid unstable new code and identify libraries that may pose a long-term maintenance risk due to lack of maintainer support.

    The skill requires an AI agent with outbound network access to connect to registry.npmjs.org and pypi.org. It works best with agents that have file-system access to read your dependency manifests and the ability to output formatted Markdown reports.

    New in APIs & Backend