Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+21 more

    ELYRAON Dependency Update Verifier

    1

    Verify dependency upgrades against your actual repository before adopting them.

    $12.99

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned

    About this skill

    "A newer version exists" is not the same as "this repository has been verified against that newer version." ELYRAON Dependency Update Verifier exists to answer one question: does this update actually work with my repository?

    Instead of just reporting the latest release, it evaluates a proposed Python dependency upgrade against the inputs you provide: your before and after requirements pins, local candidate wheels, and your own unittest suite. It returns a clear status with evidence, so you can decide whether to adopt the change.

    What it does

    • Pin comparison identifies the exact version changes between your current and proposed requirements.
    • Dependency classification separates direct, transitive and unknown changes, so hidden transitive bumps are visible.
    • Isolated verification builds a virtual environment, installs the local candidate wheels and checks installed metadata against the pins.
    • Import checks confirm the modules you list import in the candidate environment.
    • Test validation runs your local unittest suites against the candidate dependency set.
    • Evidence output binds hashes of inputs and outputs and returns a status from REVIEW_REQUIRED to SAFE_TO_UPDATE.

    Scope

    Python-first and local: it works on Python requirements pins and local wheel files, and requires Python 3.11+. It reports a verification result; it does not edit your repository, open pull requests, merge, or deploy.

    Verification is specific to your repository and the tests you have. A passing result is evidence, not a guarantee. See Known Limitations.

    Python only; other package managers and languages are not supported. Requires Python 3.11+ (tested on Linux with Python 3.12). Execution mode requires local wheel files for the candidate packages, so candidates must be available locally. Automated testing uses unittest only. Inputs are limited to 2MB each. No network isolation is provided: your code runs with your user permissions. Verification is specific to your repository and environment: passing tests does not guarantee the absence of regressions, an incomplete test suite lowers confidence, and transitive dependency effects may differ between environments. Some upgrades will still require manual review. The skill does not patch files, open PRs, merge or deploy.

    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

    Python

    Permissions

    Terminal / Shell
    Read Files
    Write Files

    Runs local Python/venv/unittest commands, reads requirements files, wheels and tests, and writes temporary verification environments and evidence output. No network access or external hosts are used; verification runs against local wheel files.

    Listed1 month ago

    What's inside

    Frequently Asked Questions

    An updater tells you a newer version exists. This skill checks whether your repository works with it: it compares the before and after pins, classifies direct and transitive changes, installs local wheels into an isolated virtual environment, runs your unittest suite and import checks, and returns a status with evidence. It does not apply updates to your repository.

    No. It is designed for Python (3.11+) requirements pins and uses standard venv, unittest and pip metadata inspection. Other package managers and languages are not supported.

    Reading a requirements file shows what changed on paper. This skill also installs the candidate wheels in a clean environment, runs your tests and import checks, and records hashes of inputs and outputs in its evidence output. Results are still specific to your repository and are not a guarantee.

    A local environment with Python 3.11 or higher (tested on Linux with Python 3.12), plus a local wheelhouse and module list so the skill can run the isolated install and import tests.

    Results range from REVIEW_REQUIRED to SAFE_TO_UPDATE. SAFE_TO_UPDATE means the verification stages passed for the pins, wheels and tests you provided. It is scoped to those inputs, is not a guarantee that the upgrade is free of regressions, and does not modify, commit, merge or deploy anything.

    The skill is limited to a 2MB file size per input and does not provide network isolation; any code executed during the validation phase runs with your local user permissions.

    New in Testing & Debugging