- Home
- Skills
- Mobile Development
- APK Build Diff — Explain Android Build Growth
More screenshots
Works with the AI Agents you already use
APK Build Diff — Explain Android Build Growth
Compare Android APKs, separate content edits from recompression, enforce your byte budget, and get an offline report whose growth ledger reconciles exactly.
$15
APK Build Diff — Explain Android Build Growth
Example session with this skill installed
Compare these two synthetic APK containers. Check a strict 150,000-byte limit and allow no more than 45,000 bytes of growth. Explain what changed before I modify anything.
- Read your context and instructions
- Compiled the apk build diff
- Generated the data export
Worked example: synthetic APK containers
These fixtures are generated by the author's make_demo.py for deterministic archive testing. They are not installable Android games. Sizes and hashes below are actual helper output, not a customer testimonial.
Request: compare these two completed APK containers, enforce a strict 150,000-byte size limit and at most 45,000 bytes of growth, then explain the change.
APK Build Diff
Archive/budget verdict: PASS
This verdict covers ZIP integrity and configured size gates. It does not establish installability, signing validity, store acceptance, gameplay or device performance.
Current: synthetic-v2.apk — 96344 bytes
SHA-256: d00353fb2a1aabeb0ffffb3934b539ea6440fbec92ca6030c56df8a86373ffba
Baseline: synthetic-v1.apk — 52859 bytes
SHA-256: 074e304a6f44a7d5a87cdfcabbc000a682ba0a62d10d9ae6e8e17cd13f5c2873
| Exact change ledger | Bytes |
|---|---|
| Compressed file payload change | 43207 |
| Container / signing / padding residual | 278 |
| Total APK change | 43485 |
Ledger reconciles: True. Residual is measured, not source-attributed.
Configured gates
| Gate | Actual | Rule | Result |
|---|---|---|---|
| APK bytes | 96344 | < 150000 | PASS |
| Growth bytes | 43485 | <= 45000 | PASS |
Entry evidence
Complete inventory and hashes: audit.json. Complete table: changes.csv. Top 30 shown here.
| Entry | Classification | Before compressed | After compressed | Delta |
|---|---|---|---|---|
| assets/world.bundle | content-changed | 40015 | 75025 | 35010 |
| lib/armeabi-v7a/libsample.so | added | 0 | 7005 | 7005 |
| assets/duplicate-title.dat | added | 0 | 1805 | 1805 |
| assets/title.dat | removed | 1805 | 0 | -1805 |
| assets/ui/title.dat | added | 0 | 1805 | 1805 |
| assets/recompress.dat | recompressed | 1259 | 646 | -613 |
| AndroidManifest.xml | unchanged-content | 38 | 38 | 0 |
| classes.dex | unchanged-content | 27 | 27 | 0 |
| lib/arm64-v8a/libsample.so | unchanged-content | 9005 | 9005 | 0 |
Investigations
ABI_SET_CHANGED: Added ABIs: armeabi-v7a; removed: none Confirm intended CPU coverage and compare Unity Android architecture settings. Do not remove a supported ABI solely to pass a byte budget.
RECOMPRESSION: 1 entries have identical expanded SHA-256 but changed compressed sizes; signed delta -613 bytes. Compare compression/packaging settings before investigating content edits; content hashes did not change.
CONTAINER_DELTA: 278 bytes of change are outside the summed compressed file payloads. This residual includes ZIP structures, directory payloads, signing blocks and padding. Inspect the packaging/signing process; the report does not locate or verify an APK signing block.
TOP_GROWTH: assets/world.bundle grew by 35010 compressed bytes (content-changed). Use a matching Unity BuildReport or bundle layout to identify source assets. This APK entry is opaque: texture, audio and individual asset contributions cannot be inferred from its name. Verify runtime loads and authoring provenance before removing anything.
TOP_GROWTH: lib/armeabi-v7a/libsample.so grew by 7005 compressed bytes (added). Compare ABI, Unity/IL2CPP, symbol and native-plugin build settings. This entry is a compiled library; source-level attribution needs separate build evidence.
TOP_GROWTH: assets/duplicate-title.dat grew by 1805 compressed bytes (added). Use a matching Unity BuildReport or bundle layout to identify source assets. This APK entry is opaque: texture, audio and individual asset contributions cannot be inferred from its name. Verify runtime loads and authoring provenance before removing anything.
REPEATED_CONTENT: 1 non-empty byte-identical content groups; 1805 compressed bytes beyond one largest copy per group. These are inspection candidates, not promised savings. Different package paths may be required. Prove references/runtime loading, rebuild and functionally test before deduplication.
Content-identical move candidates
None detected. Ambiguous many-to-many matches are deliberately not called moves.
Duplicate content candidates
- 1805 repeated compressed bytes: assets/duplicate-title.dat, assets/ui/title.dat
changes.csv
CSV · data export
Example file from a real run - the skill writes it into your workspace.
Connects securely to your tools. The creator never sees your data.
About this skill
Your Android build grew. This skill helps establish what changed before you start rebuilding or reducing asset quality.
Provide the current APK, an optional earlier APK and your own size or growth thresholds. APK Build Diff reads both archives locally and produces exact measurements, entry-level evidence and an interactive offline report.
What you receive
- A complete byte ledger: compressed file changes plus container residual equal the complete APK change.
- Content hashes that separate actual edits from recompression and identify unique content-identical move candidates.
- Absolute size and growth gates with reproducible exit codes and explicit boundary behavior.
- Observed ABI changes, repeated-content candidates and evidence-linked investigation guidance.
- A searchable, sortable HTML report, Markdown explanation, full CSV table and complete JSON evidence.
- Unity-specific guidance that distinguishes opaque bundles from attributable source assets.
The helpers stream entry data, check ZIP CRC, and hash actual files. They do not modify, unpack or execute your APK. Data stays in the local session; review internal filenames before sharing a report.
Scope
This is an archive and configured-budget audit. It does not certify signing, installability, Google Play or another store's acceptance, malware safety, gameplay correctness or phone performance. It does not decode Unity bundles or prove assets unused. Duplicate bytes are investigation candidates, not guaranteed savings. AAB, IPA, split APK sets and Play download-size measurement are outside v1 scope.
Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for Mobile Development.
Archive integrity and configured-budget checks only. Does not verify Android signatures, installability, store acceptance, malware safety, gameplay or phone performance. No AAB, IPA, split APK sets, Play download-size measurement, Unity bundle decoding or per-source-asset attribution. Duplicate bytes are investigation candidates, not guaranteed savings. Windows/Python 3.11.13 and 3.13.3 are validated; other hosts and live Agensi retrieval remain unverified. Default caps: 4 GiB expanded data and 100,000 entries.
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 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 16 days ago
- Software
Python 3.11+
- Optional
- Web browser
Validated on Windows. The browser is only for viewing the optional offline HTML report.
Permissions
Reads only customer-selected APK files and writes reports to the customer-selected output directory. The two supplied Python helpers run from temporary files and are then removed. No network calls, APK extraction/execution, account access or signing keys. Browser use is only needed by the customer to view the generated HTML.