JasonColapietro/suede-creator-skills / skills/suede-play-release
suede-play-release
VerifiedSuede Google Play Release Skills. Google Play release delivery with AAB preflight, test-track upload, exact versionCode promotion, staged rollout, locale notes, and API readback. Use when asked "promote this Android build" or to diagnose Play publishing access and prove the served release. NOT FOR: app building or policy review (android-app-factory), listing assets (suede-aso), or CI gates (suede-ci-gate).
| File | Kind | Size |
|---|---|---|
| CARD.md | markdown | 4.5 KB |
| SKILL.md | skill md | 9.2 KB |
| agents/openai.yaml | config | 1.2 KB |
| references/worked-contract.md | markdown | 2.6 KB |
| scripts/play-preflight.pyexecutable | script | 4.7 KB |
agents/openai.yaml
View on GitHubinterface:
display_name: "Suede Google Play Release Skills"
short_description: "Google Play delivery with a proven readback"
default_prompt: "Use $suede-play-release to upload or promote an Android build on Google Play. Preflight the credential with a real API call that opens and deletes an edit: a new service account returns 403 until the Play Console grants it, and that grant is a Console UI action to hand to the user. Pull before every fastlane command, because fastlane reads the working tree and a stale checkout produces a run that succeeds and does nothing. Write a changelog per locale per versionCode first; a missing one is a silent skip that serves the previous version's notes. Verify the AAB rather than the source tree: signature, versionCode in the merged manifest, and a hash match for any changed asset. Upload to a testing track, then promote that exact versionCode instead of re-uploading, which Play rejects. Finish by reading the track back from the Play API and reporting versionCode, status and userFraction, because a green fastlane summary cannot tell you whether the release landed staged or completed."
policy:
allow_implicit_invocation: true
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| finishing-a-development-branchobra/superpowersUse when implementation is complete, all tests pass, and you need to decide how to integrate the work | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| systematic-debuggingobra/superpowersUse when encountering any bug, test failure, or unexpected behavior, before proposing fixes | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| test-driven-developmentobra/superpowersUse when implementing any feature or bugfix, before writing implementation code | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| skill-creatoranthropics/skillsCreate new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |