- Home
- Skills
- Testing & Debugging
- ELYRAON Dependency Update Verifier
Works with the AI Agents you already use
ELYRAON Dependency Update Verifier
Verify dependency upgrades against your actual repository before adopting them.
$12.99
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
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
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 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
Permissions
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.