// Guidance for using the Google Play Developer CLI (flags, output formats, auth, pagination). Use when asked to run or design gpd commands for Play Console workflows.
| name | gpd-cli-usage |
| description | Guidance for using the Google Play Developer CLI (flags, output formats, auth, pagination). Use when asked to run or design gpd commands for Play Console workflows. |
Use this skill when you need to run or design gpd commands for Google Play Developer Console.
--help to confirm commands and flags.
gpd --helpgpd publish --helpgpd monetization --help--package, --track, --status).--confirm.--all when the user wants all pages.--pretty for readable JSON during debugging.GPD_SERVICE_ACCOUNT_KEY is required.gpd auth check --package com.example.app--dry-run when available before destructive operations.gpd publish edit create) for multi-step publishing.Orchestrate Google Play beta testing groups and distribution using gpd. Use when managing testers, internal testing, or beta rollouts.
Track build processing, status, and retention for Google Play using gpd publish commands. Use when waiting on processing or managing releases.
Manage Google Play Developer Console using the gpd CLI. Use when working with Android app publishing, Play Store releases, app reviews, Android vitals, in-app purchases, subscriptions, or when the user mentions Google Play, Play Store, Android publishing, or gpd.
Resolve Google Play identifiers (package, tracks, version codes, products, subscriptions) using gpd. Use when commands require IDs or exact values.
Sync and validate Google Play metadata, listings, and assets with gpd, including Fastlane-style workflows. Use when updating store listings or translations.
Set region-specific pricing for Google Play subscriptions and products using gpd monetization commands. Use when adjusting prices by territory or PPP strategy.