gplay-cli-usage
Guidance for using the Google Play Console CLI in this repo (flags, output formats, pagination, auth, and discovery). Use when asked to run or design gplay commands or interact with Google Play Console via the CLI.
By tamtom · 385 installs
npx skills add tamtom/gplay-cli-skills --skill gplay-cli-usage
Source repository · Upstream listing
Google Play CLI usage
Use this skill when you need to run or design gplay commands for Google Play Console.
Command discovery
Always use help to discover commands and flags.
gplay help
gplay tracks help
gplay tracks list help
Available commands
Command Description
gplay auth Authentication and profile management
gplay apps List and manage apps in the developer account
gplay init Initialize a project with default config
gplay release High level release workflow
gplay promote Promote releases between tracks
gplay rollout Manage staged rollouts
gplay tracks Track management
gplay bundles Bundle (AAB) management
gplay edits Edit session management
gplay listings Store listing management
gplay images Screenshot and image management
gplay sync Metadata sync (import/export)
gplay validate Offline validation of metadata
gplay vitals App vitals monitoring (crashes, performance, errors)
gplay users User management for developer account
gplay grants App level permission grants
gplay reports Financial and statistics reports (list/download from GCS)
gplay docs generate Generate CLI documentation
gplay migrate Migration tools (e.g., from Fastlane)
gplay notify Send notifications (e.g., Slack, webhook)
gplay update Self update the CLI binary
Flag conventions
Use explicit long flags (e.g., package , output ).
No interactive prompts; destructive operations require confirm .
Use paginate when the user wants all pages.
Use dry run to preview changes without executing them (supported by release , migrate , and other write commands).
Output formats
Default output is minified JSON.
Use output table or output markdown only for human readable output.
pretty is only valid with JSON output.
Set GPLAY DEFAULT OUTPUT environment variable to change the default output format (e.g., GPLAY DEFAULT OUTPUT=table ).
Authentication and defaults
Prefer service account auth via gplay auth login service account /path/to/sa.json .
Fallback env vars: GPLAY SERVICE ACCOUNT , GPLAY PACKAGE .
GPLAY PACKAGE can provide a default package name.
Timeouts
GPLAY TIMEOUT / GPLAY TIMEOUT SECONDS control request timeouts.
GPLAY UPLOAD TIMEOUT / GPLAY UPLOAD TIMEOUT SECONDS control upload timeouts.
Environment Variables
Variable Purpose
GPLAY SERVICE ACCOUNT Path to service account JSON
GPLAY PACKAGE Default package name
GPLAY PROFILE Active profile name
GPLAY TIMEOUT Request timeout (e.g., 90s , 2m )
GPLAY TIMEOUT SECONDS Timeout in seconds (alternative)
GPLAY UPLOAD TIMEOUT Upload timeout (e.g., 5m , 10m )
GPLAY DEBUG Enable debug logging (set to api for HTTP requests)
GPLAY NO UPDATE Disable update checks
GPLAY MAX RETRIES Max retries for failed requests (default: 3)
GPLAY RETRY DELAY Base delay between retries (default: 1s )
GPLAY DEFAULT OUTPUT Default output format ( json , table , markdown )
Common patterns
List with pagination
Parse JSON output with jq
Use profiles
Debug mode
Dry run (preview changes)
Initialize a project
List apps in developer account
Generate CLI documentation
Self update
Financial reports
Statistics reports
Send notifications
Edit sessions
Most write operations require an edit session:
High level vs manual commands
High level : gplay release (creates edit, uploads, commits)
Manual : gplay edits create → gplay bundles upload → gplay edits commit
Use high level for simplicity, manual for fine grained control.