More screenshots

    Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+21 more

    APK Size Diet

    1

    Shrink an Android APK or AAB by measuring what actually takes space, cutting the largest waste first, and verifying the smaller build.

    $5

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned
    APK Size Diet

    APK Size Diet

    Example session with this skill installed

    Rank this listing: lib/arm64-v8a/libnative.so at 20,000,000 bytes, res/drawable/bg.png at 15,000,000 bytes, and classes.dex at 8,000,000 bytes.

    • Read your context and instructions
    • Compiled the apk size diet

    Running the bundled reporter on that listing produces:

    TOTAL: 43000000 bytes (41.0 MB) across 3 entries
    CATEGORIES (ranked):
      native-libs: 20000000 bytes (46.5%)
      images: 15000000 bytes (34.9%)
      code: 8000000 bytes (18.6%)
    TOP FILES:
      20000000  lib/arm64-v8a/libnative.so
      15000000  res/drawable/bg.png
      8000000  classes.dex
    BULK-FILE: lib/arm64-v8a/libnative.so is 46.5% of the total — check it before category-wide cuts.
    LARGEST-CATEGORY: native-libs — start the diet here.
    

    The skill's worked example scales this up: a 142 MB app cut to 98 MB (31 percent) by dropping an unneeded architecture, downscaling oversized backgrounds, and re-encoding audio — with a font-subset cut rejected because the target was already met and the glyph risk was not worth 3 MB.

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

    About this skill

    Size work usually starts with what is easy to cut while the actual bulk sits untouched in uncompressed assets or duplicated native libraries. This skill starts with a ranked size breakdown by category — code, native libraries per architecture, images, audio, fonts, resources — then ranks cuts by saving per risk, applies them in order with a rebuild and measurement per cut, and verifies the smaller build installs and passes a smoke pass covering every flow that touches a cut asset.

    It includes a decision table keyed to the largest category, guidance on the classic bulk causes (unneeded architectures, full-resolution images displayed small, uncompressed audio, test assets in release), and the discipline of stopping at the target or the risk boundary, with rejected cuts recorded so the next diet does not re-argue them. A runnable reporter ranks an archive listing by category, names the largest files, and flags any single file over 25 percent of the total.

    • Needs a size breakdown from the actual artifact; estimates from source folders alone mislead.
    • Store-delivered splits make download size smaller than a universal APK; the skill requires stating which artifact was measured.
    • Moving assets to download-on-demand shrinks the artifact but adds a download step and failure mode; it is only a genuine cut when the asset is rarely needed on first run.

    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

    No. Rank by bytes, always. A diet measured in files deleted has lost the plot; one large asset usually outweighs hundreds of small ones.

    Because an image that looks fine in a desktop preview can show banding or blur on a phone screen, and audio that sounds fine on headphones can sound thin on a phone speaker.

    When the target is met, or when the remaining candidates are all high-risk with small savings. Cutting a language or a feature to hit a round number nobody asked for is not a diet.

    New in Mobile Development