More screenshots

    Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+21 more

    Godot Android Export Failure Triage

    1

    Find which stage of a Godot Android export failed — templates, SDK, signing, config, or resources — and get a clean APK or AAB out.

    $5

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned
    Godot Android Export Failure Triage

    Godot Android Export Failure Triage

    Example session with this skill installed

    Scan this export log: ERROR: export template not found for this editor version followed by a Gradle failure line.

    • Read your context and instructions
    • Compiled the godot android export

    Running the bundled script on that log produces:

    STAGE: template
    FIRST-ERROR: ERROR: export template not found for this editor version
    FIX: Install the template set matching the editor version exactly and restart the editor.
    

    The skill's worked example completes the story: the installed templates belonged to the previous stable release, the fix was installing the beta editor's matching templates and removing the stale ones, and the re-export produced a 48 MB APK whose package dump read correctly. The Gradle error never needed attention.

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

    About this skill

    Godot Android exports fail in a small set of repeatable places, but the log cascades: one root failure produces a chain of follow-on errors, and teams fix the last error instead of the first. This skill teaches a stage-based triage: reproduce with a saved log, locate the first error line (not the last), classify it into template, SDK, signing, project config, resources, or toolchain, fix only that stage, and validate the artifact with a package dump before distributing it.

    Beyond the decision table, it includes stage playbooks (including the absolute rule that template versions must match the editor version, beta designations included), a stall diagnosis path, the custom-Gradle-build split test, and a 15-point rubric. A runnable log scanner names the failing stage from an export log automatically.

    • Requires the full export log; a screenshot of the final error alone may not contain the first error line.
    • Covers Android exports only, not iOS, desktop, or web exports.
    • Does not debug gameplay or runtime behavior in an exported build.

    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

    Not necessarily. Read from the top: the first error line decides the stage. In the skill's worked example, a Gradle error at the end was downstream noise from a missing template.

    No. The template version must match the editor version exactly, including beta designations. A nearby version is not close enough.

    Template discovery is cached in ways that survive a settings change but not a restart. Skipping the restart is a common cause of "I installed the template and it still fails."

    New in Game Development