gpd-cli-usage
Scannednpx machina-cli add skill rudrankriyam/app-store-connect-cli-skills/gpd-cli-usage --openclawFiles (1)
SKILL.md
1.1 KB
GPD CLI usage
Use this skill when you need to run or design gpd commands for Google Play Developer Console.
Command discovery
- Always use
--helpto confirm commands and flags.gpd --helpgpd publish --helpgpd monetization --help
Flag conventions
- Use explicit long flags (for example:
--package,--track,--status). - No interactive prompts; destructive operations require
--confirm. - Use
--allwhen the user wants all pages.
Output formats
- Default output is minified JSON.
- Use
--prettyfor readable JSON during debugging.
Authentication and defaults
- Service account auth via
GPD_SERVICE_ACCOUNT_KEYis required. - Validate access for a package:
gpd auth check --package com.example.app
Safety
- Use
--dry-runwhen available before destructive operations. - Prefer edit lifecycle (
gpd publish edit create) for multi-step publishing.
Source
git clone https://github.com/rudrankriyam/app-store-connect-cli-skills/blob/main/skills/gpd-cli-usage/SKILL.mdView on GitHub Overview
This skill guides you through running and designing gpd commands for the Google Play Developer Console. It covers discovery, flag conventions, output formats, authentication, and safety practices to streamline Play Console workflows.
How This Skill Works
You discover commands with gpd --help and apply explicit long flags (for example: --package, --track) with no interactive prompts. Authentication is performed via a service account key (GPD_SERVICE_ACCOUNT_KEY), and you can use --dry-run before destructive actions; for multi-step publishing, prefer the edit lifecycle (gpd publish edit create).
When to Use It
- When you need to discover available gpd commands and flags with --help
- When you need to fetch, list, or paginate results across pages using --all
- When validating access to a package with gpd auth check --package
- When preparing a publish or update, using --dry-run first for safety
- When performing multi-step publishing, using the edit lifecycle (gpd publish edit create)
Quick Start
- Step 1: Run gpd --help to discover commands
- Step 2: Build a command using explicit flags (e.g., --package, --track, --status) and avoid prompts; use --confirm for destructive steps
- Step 3: Validate with gpd auth check --package and perform a dry-run before actual publish (gpd publish edit create)
Best Practices
- Always start with gpd --help to confirm commands and flags
- Use explicit long flags like --package, --track, --status
- Avoid interactive prompts; require --confirm for destructive actions
- Use --all for complete pagination and --pretty for debugging
- Use --dry-run before destructive or irreversible publishing steps
Example Use Cases
- Running gpd --help to map the available commands and flags
- Listing all monetization items with gpd monetization --help and --all
- Validating package access with gpd auth check --package com.example.app
- Previewing a publish with gpd publish edit create and --dry-run
- Publishing a release with explicit flags after confirming with --confirm
Frequently Asked Questions
Add this skill to your agents