- Home
- Skills
- Mobile Development
- APK Build Pipeline: CI to Signed, Verified APK
More screenshots
Works with the AI Agents you already use
APK Build Pipeline: CI to Signed, Verified APK
Take Android app source to a signed, verified APK: build through GitHub Actions, pull the artifact, run the six-check smoke test, and fall back to a local JDK build only when CI is blocked.
$5
APK Build Pipeline: CI to Signed, Verified APK
Example session with this skill installed
Build version 1.1 (code 2) of a Godot game, com.dogbyte.deepfall, for a phone playtest. The user's phone already has 1.0 installed. Build it through CI and verify it before I hand it over.
- Read your context and instructions
- Compiled the apk build pipeline
BUILD + VERIFICATION — deepfall 1.1 (code 2): six smoke checks green, ready to ship.
Step 1 — source prep: build-tools 36.1.0 pinned, platform android-36 pinned, all binary assets verified by magic bytes. versionCode bumped 1 → 2, versionName 1.0 → 1.1. The bump matters: the phone already has 1.0 installed, and a same-version rebuild would silently fail to replace it.
Step 2 — CI: pushed to the build branch; the "Build APK" run started and went green in 9 minutes. Run URL recorded with the branch and commit.
Step 3 — artifact: downloaded, 2,066,467 bytes, recorded immediately as the reference for every later check.
Step 4 — smoke tests, all green:
- dex + resources packaged — the app contains code and assets.
- Manifest parses — package com.dogbyte.deepfall, code 2, name 1.1.
- v2 signature valid — signed by the expected key.
- versionCode/versionName match the release.
- Native libs 16KB page-aligned (Android 15+ requirement).
- Web assets byte-identical to source.
Step 6 — delivery report handed over with the run URL, commit, byte count, signature result, and the six-row table. The user installs it; the new version replaces the old one because the versionCode moved. Had the version stayed at 1, the phone would have kept running the old build and the playtest feedback would have been about the wrong code — the version check is what prevents that. Verdict: SHIP.
Connects securely to your tools. The creator never sees your data.
About this skill
An APK the user installs must be traceable: which commit, which workflow run, which signature, and a verification report. This skill makes that the default instead of a hope.
The pipeline has six steps: prepare the source (pinned build-tools, resolvable dependencies, binary assets verified by magic bytes, version bumped), push and trigger CI (with a Git Data API fallback when the cached credential has expired, including the singular-vs-plural ref quirk), pull the artifact and record the exact byte count immediately, smoke-test it, fall back locally only when CI is blocked, and deliver with the report.
The smoke test runs every time, no exceptions: dex and resources packaged, manifest parses, v2 signature valid, versionCode/versionName match the release, native libs 16KB page-aligned for Android 15+, and web assets byte-identical to source. The delivery report hands over the APK path, byte count, Actions run URL with branch and commit, version, signature result, and the six-row pass/fail table.
It also includes install-failure triage — diagnosis first, rebuild never: byte count (truncated download), signature collision (stale install with a different key), OS requirements (minSdk, 16KB alignment), and file confusion (browsers renaming .apk to .zip). Only after all four come back clean is a rebuild on the table.
- CI green means it built; only the smoke tests prove it is the right build, signed, aligned, and intact.
- A fresh debug key per CI run means each build is signed differently and can never update a previous install — the signing key must be pinned.
- Smoke tests verify packaging, not runtime: a build that passes can still crash on launch, which is a device-lab investigation.
- The Git Data API fallback requires the API helper; it cannot recover a lost credential on its own.
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 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 3 days ago
Permissions
No special permissions declared or detected