More screenshots

    Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIDeepSeekDeepSeekMuseMuse+22 more

    Check the Download Your Users Actually Get

    1

    Before you call a release live, test the actual file your users download — and update to — the way they will.

    $9

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned

    Check the Download Your Users Actually Get

    Example session with this skill installed

    Verify the release feed at https://api.example.com/v1/releases/latest against the hosted asset at https://cdn.example.com/downloads/setup.exe and check for branding leaks of 'OldProject'.

    • Read your context and instructions
    • Compiled the check the download

    I have performed the release verification for the latest version. The feed and hosted asset match, but several rebranding leaks were found in the codebase.

    Release Verification Report

    Check ItemResultDetails
    Feed Version2.4.1Extracted from api.example.com
    Feed File NameExampleApp_Setup_2.4.1.exeExact match expected
    Hosted Asset NameExampleApp_Setup_2.4.1.exeMATCH
    Download Status200 OKSize: 45.2MB
    Clean InstallPASSEDVersion 2.4.1 confirmed in About panel
    Update PathPASSEDUpdated from 2.4.0 to 2.4.1 successfully
    Branding SweepFAILED4 hits found for 'OldProject'
    User ConfirmationUNCONFIRMEDPending manual report

    Branding Leak Details

    - /src/locales/es.json: "copyright": "© 2023 OldProject"
    - /src/components/Settings.tsx: <h2>About OldProject</h2>
    - /docs/README.md: https://github.com/org/OldProject
    - /scripts/postinstall.sh: echo "Installing OldProject..."
    

    Next steps

    1. Patch the 4 branding leaks identified in the Spanish locale and source files.
    2. Request a version report from a team member on a different OS to move User Confirmation to PASSED.
    3. Update the release feed only after the rebranding fixes are committed and verified.

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

    About this skill

    A green build does not prove a release works. A release feed once named a file with spaces while the host served the same name with dots — every user's updater got a 404 error, and nothing in the build pipeline complained. This skill is the check that catches that class of failure: test the published file itself, reached through the same address and update path a user hits, never a local build that merely resembles it.

    Inside the package: the skill file covering the published-artifact checks, the live update-path test, and the rebrand sweep, plus a filled example verification report and a one-page checklist.

    A run goes like this: the agent reads your live release feed and compares the file name it promises against the hosted file, character by character. It downloads and installs that file from a clean state and confirms the installed version matches the feed. Then it installs the previous version, launches it, and runs its normal update check to the new one — including a second attempt, because some updaters quietly give up after a few failures and hide a still-broken feed. If you've renamed the product, it also sweeps every screen, settings panel, onboarding slide, and language file for the old name. You get a report that lists each item as verified or unconfirmed, separately. A part nobody checked is reported as unconfirmed — never folded into a cheerful "released."

    Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for Testing & Debugging.

    Requires manual confirmation for user-reported version checks. Does not automate VM provisioning or environment snapshots.

    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 buying a skill.

    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 6 days ago

    Software
    A clean install environmentPrevious version for update testing

    Access to the release feed and hosted artifact download URLs.

    Permissions

    Read Files
    Network Access
    Terminal / Shell
    Listed6 days ago

    What's inside

    Frequently Asked Questions

    While CI/CD pipelines confirm your code builds, they often miss external hosting issues like broken download URLs or filename case-sensitivity that occur after the code leaves the build environment. This skill acts as a final safety check, ensuring that what the user actually downloads is functional and correctly branded.

    The skill is compatible with any AI agent or platform that supports external tool integration and web browsing capabilities, as it needs to fetch live manifests and verify hosted URLs. It works across various distribution formats, including desktop installers, CLI binaries, and mobile packages.

    Yes, the 'Update Path Testing' feature is specifically designed to identify failures that occur when moving between versions, such as registry errors or installer conflicts that don't appear during a fresh install. This helps you catch issues that would otherwise only be reported by your existing user base.

    You will receive the structured skill logic, a set of configuration templates for different release feeds (like JSON manifests or GitHub Releases), and a guide on how to integrate it into your release workflow. It includes predefined audit patterns for both technical verification and brand string consistency.

    The skill focuses on external verification; it requires access to your public or staging release feeds and the ability to execute installation commands in your target environment. It does not require access to your source code repository, keeping your intellectual property secure.

    New in Testing & Debugging