A green fastlane summary is not a shipped release.
Play delivery where every claim is a readback. The skill proves the credential with a real API call before it touches anything, uploads to a testing track, promotes that exact versionCode instead of re-uploading one Play will reject, and finishes by reading the track back so you learn whether the release landed staged or complete. It never grants itself Play Console access and never promotes to production without being told.
"ship the android build"->/suede-play-releaseAsk in plain words. The router reads the request and loads this lane; MCP agents find it with list_suede_skills.
claude code · sample session
$ /suede-play-release promote 1.2preflight: edit opened and deleted · publishing wiredinternal: versionCode 8 · promote, not re-uploadPRODUCTION: completed · 4 localesread back from the Play API, not the summary
Preflight the credential with a live API call that opens a Play edit and deletes it, so a 403 from a missing Play Console grant is named before a build is ever made.
Store the service-account JSON base64-encoded in the OS keychain, because security hex-encodes multi-line secrets on read and raw JSON returns in two possible shapes.
Keep the publishing identity separate from any billing or purchase-verification account, so a release credential cannot void purchases.
Verify the AAB itself: signature, versionCode in the merged manifest, and a hash match between a changed asset and the copy inside the bundle.
Write release notes per locale per versionCode first, because a missing changelog is a silent skip that serves the previous version's notes to real users.
Promote the versionCode already validated on a testing track rather than re-uploading a bundle Play rejects for a duplicate versionCode.
Read the production track back and report versionCode, status, and userFraction, since a staged rollout at 100% and a completed release read identically in a success message.
When to use it
Uploading an Android build, or promoting one between tracks.
Wiring a Play service account, keychain credential, and fastlane supply lanes for the first time.
Raising, holding, or explaining a staged production rollout.
Answering what version and what rollout fraction production is actually serving.
Fixing per-versionCode changelogs that are missing in some locales.
Not for: planning, building, or policy-checking the app itself (use android-app-factory).
Not for: live Play listing and keyword audits on a shipped app (use suede-aso).
Not for: wiring CI required checks around the release (use suede-ci-gate).
Best prompt
Use $suede-play-release to ship this Android build: preflight the Play credential, verify the AAB signature and versionCode, upload to internal, then promote to production at a staged rollout and read the track back to confirm what actually shipped.
It ships inside the Suede Creator Skills pack, so one install brings the whole pack and this skill with it. Claude Code takes two commands the first time and one after that; Codex installs the same pack natively.