More screenshots

    Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+21 more

    APK Install Failure Triage

    1

    Diagnose any Android install failure from its exact error line and apply the smallest fix that gets the build installed.

    $5

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned
    APK Install Failure Triage

    APK Install Failure Triage

    Example session with this skill installed

    Classify this install output: Failure [INSTALL_FAILED_UPDATE_INCOMPATIBLE: Package signatures do not match previously installed version].

    • Read your context and instructions
    • Compiled the apk install failure

    Running the bundled script on that log produces:

    CLASS: signature-mismatch
    EVIDENCE: Failure [INSTALL_FAILED_UPDATE_INCOMPATIBLE: Package signatures do not match previously installed version]
    FIRST-FIX: Uninstall the old copy on this test device, then reinstall. If users hold the old build, the new build must use the original key.
    

    The skill's worked example then shows the full triage: the installed copy was release-signed, the new file was a debug build, the fix was device-local, and the prevention item (never mix test-track and debug builds on one device without warning the tester) was recorded so the next occurrence is answered in a minute instead of a rebuild cycle.

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

    About this skill

    When an APK refuses to install, teams usually rebuild first and read the error second. This skill reverses that order. It captures the exact installer output, checks the package-manager log for the real verdict, classifies the failure against a decision table covering signature mismatches, version-code regressions, parse failures, SDK floor mismatches, storage, test-only flags, and policy blocks, then applies one fix at a time with a verification step that proves the app both installs and launches.

    What makes it different from a generic troubleshooting checklist: a decision table keyed to verbatim error strings, fix playbooks for the recurring classes (including the debug-vs-release signature trap that wastes the most cycles), a template incident note that turns ten incidents into a pattern detector, and a 15-point scoring rubric that grades a triage before it is closed. It also ships a runnable classifier script that reads an install log and names the failure class and first fix.

    • Classification depends on having the exact error text; a paraphrased error can only yield a provisional classification.
    • On-device installs without adb access give weaker evidence than a connected-device run.
    • The skill diagnoses install failures only; it does not fix crashes after a successful install.

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

    Permissions

    Terminal / Shell
    Read Files
    Listed23 days ago
    Updated21 days ago

    What's inside

    Frequently Asked Questions

    Yes. A silent refusal is treated as a signal: the skill directs you to the package-manager log, where the real reason usually appears, and classifies from that line.

    Only on a test device. On a real user's device, uninstalling deletes their data, and the durable fix is signing the new build with the original key.

    Because a rebuild that changes nothing except the timestamp wastes a build cycle and destroys evidence. If the error text is unchanged after a rebuild, the cause was never in the build.

    New in Testing & Debugging