agentleFS
Sign inStart free
mikezamayiasmikezamayias/agent-skills/skills/gplay-console/SKILL.md

gplay-console

Skill1 starsChanged 27 days agoBSD-3-ClauseView on GitHub

Automates and preflights Google Play Console releases for Android and Flutter apps. Use when publishing to Google Play, uploading AABs, managing tracks and staged rollouts or syncing store listings. Also covers Data safety, Play Billing products, reviews, Android vitals and a Play counterpart to asc workflows.

The file

Show its rules and text

We split this skill into the rules it gives an agent

15 rules. About 0 are common, 12 are distinctive, and 3 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈12

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Use this skill as the Google Play counterpart to the asc-* App Store Connect skills.

    line 9
  2. Distinctive:

    Before making changes, identify:

    line 19
  3. Distinctive:

    Prefer an already configured MCP or CLI wrapper if present in the environment.

    line 31
  4. Very specific:

    Use Fastlane supply when the repo already has fastlane/metadata/android/ or Fastlane lanes.

    line 32
  5. Distinctive:

    Use Android Publisher REST/API clients for direct, transactional release automation.

    line 33
  6. Distinctive:

    Use browser automation only for first app creation or Play Console declarations that cannot be safely handled by API.

    line 34
  7. Distinctive:

    Run go-live preflight: target API, signed AAB, Play App Signing, privacy policy, Data safety, store assets, metadata, release notes, …

    line 41
  8. Very specific:

    Create a Play edit or use Fastlane supply.

    line 43
  9. Distinctive:

    Update the intended track with status and rollout fraction.

    line 44
  10. Distinctive:

    Check Play Console review/managed publishing status and report any manual gates.

    line 45
  11. Distinctive:

    Do not store service-account JSON, OAuth refresh tokens, keystores, or passwords in repo files.

    line 50
  12. Distinctive:

    Prefer Keychain, SOPS/direnv, CI secrets, or ignored local paths for credentials.

    line 51
  13. Distinctive:

    Treat production rollout, price changes, subscription changes, and policy declarations as approval-gated.

    line 52
  14. Distinctive:

    Do not claim a Play policy form is complete unless it was read from Play Console/API or the user explicitly confirmed it.

    line 53
  15. Distinctive:

    If Managed Publishing is on, distinguish "submitted/approved" from "published".

    line 54

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Google Play Console

Use this skill as the Google Play counterpart to the asc-* App Store Connect skills. Prefer official Google Play Developer APIs, Fastlane supply, or an installed Google Play MCP when available; use browser automation only for gaps that are not API-safe.

References

  • Load references/api-map.md before choosing the automation path or writing commands.
  • Load references/play-go-live-checklist.md before release readiness, submission, or policy work.
  • Load references/research-notes.md when deciding whether to install or configure a third-party MCP/skill.

Required Intake

Before making changes, identify:

  • Package name, app name, and whether the app already exists in Play Console.
  • Target track: internal, closed, open, production, or staged rollout.
  • Artifact path: signed .aab, mapping file, native debug symbols, and release notes.
  • Listing source: fastlane/metadata/android/, metadata/, store_assets/, or Play Console only.
  • Developer account type (personal or organization) and creation date, because they decide whether a 12-tester, 14-day closed test gates production access. Load the Account Gate section of references/play-go-live-checklist.md.
  • Credential path and auth mode. Never commit service-account JSON keys.
  • Manual declarations still needed: app content, content rating, target audience, ads, financial products, government apps, health, Data safety, privacy policy, and account deletion.

Automation Path

  1. Prefer an already configured MCP or CLI wrapper if present in the environment.
  2. Use Fastlane supply when the repo already has fastlane/metadata/android/ or Fastlane lanes.
  3. Use Android Publisher REST/API clients for direct, transactional release automation.
  4. Use browser automation only for first app creation or Play Console declarations that cannot be safely handled by API.

First-time app creation is a Play Console UI flow. The Publishing API generally operates after an app/package exists in the developer account.

Workflow

  1. Discover the Android project: package name, version code/name, signing config, flavors, target SDK, permissions, billing, analytics, and store metadata paths.
  2. Run go-live preflight: target API, signed AAB, Play App Signing, privacy policy, Data safety, store assets, metadata, release notes, billing, age/content declarations.
  3. Build or locate the signed AAB. Validate it before upload.
  4. Create a Play edit or use Fastlane supply; upload artifact, mapping/symbols, listing text, images, and track release notes.
  5. Update the intended track with status and rollout fraction. Commit only after verifying every staged change.
  6. Check Play Console review/managed publishing status and report any manual gates.
  7. Produce a short go/no-go report with exact next commands, manual items, and rollback/pause instructions.

Safety Rules

  • Do not store service-account JSON, OAuth refresh tokens, keystores, or passwords in repo files.
  • Prefer Keychain, SOPS/direnv, CI secrets, or ignored local paths for credentials.
  • Treat production rollout, price changes, subscription changes, and policy declarations as approval-gated.
  • Do not claim a Play policy form is complete unless it was read from Play Console/API or the user explicitly confirmed it.
  • If Managed Publishing is on, distinguish "submitted/approved" from "published"; the final publish step may still be manual.

Done State

  • Artifact and metadata source paths are recorded.
  • Track, release status, rollout percent, and version codes are explicit.
  • Data safety and policy declarations are either completed or listed as manual blockers.
  • Play listing assets and text pass the checklist.
  • The final report says SHIP, HOLD, or BLOCK with concrete reasons.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free