Gplay Submission Checks

This is the pre-flight checklist you run before hitting submit to Google Play. It walks through bundle validation, metadata limits (30 char titles, 80 char short descriptions), screenshot requirements, version code conflicts, and the data safety form that trips up half of all submissions. The dry run command is especially useful since it validates everything server-side without actually committing the release. Also covers the usual rejection culprits like targeting old API levels, missing phone screenshots, and signing key mismatches. If you've ever had a release rejected for something you could have caught locally, this is that systematic runthrough you wish you'd done.

skills.sh installs: 476
GitHub stars: 52
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add tamtom/gplay-cli-skills --skill gplay-submission-checks --agent claude-code

Installs into .claude/skills of the current project.

Files

Google Play Submission Checks

Use this skill to validate everything before submitting a release to Google Play, reducing rejections and failed edits.

Preconditions

Auth configured (gplay auth login or GPLAY_SERVICE_ACCOUNT env var).
Package name known (--package or GPLAY_PACKAGE).
AAB/APK built and signed.
Service account has at least "Release Manager" permission.

Prefer the First-Class Commands

The CLI has canonical, purpose-built commands. Reach for these before hand-scripting individual validators:

gplay validate --package <pkg> — the canonical release-readiness report. Combines local artifact/metadata/screenshot/release-note checks with remote track and listing state and Console-only follow-up items. Use --bundle, --listings-dir, --screenshots-dir, --track, and --strict (treat warnings as failures) to scope it.
```
gplay validate \
  --package com.example.app \
  --bundle app-release.aab \
  --track production \
  --strict
```