About gpd-cli-usage
A skill for running or planning `gpd` commands for Google Play Developer Console. It explains command discovery, flags, output, authentication, and safer handling of destructive operations.
Key features
- 01Discover commands with `--help`
- 02Use explicit long flags
- 03Control JSON output formatting
- 04Check service account access
- 05Apply dry runs and edit lifecycle
Use cases
- 01Plan Google Play publishing commands
- 02Confirm flags before running operations
- 03Check package access and credentials
- 04Reduce risk in destructive changes
Install
Copy the command and run it in a terminal.
$
npx skills add https:/ / github.com/ dl-alexandre/ skills --skill gpd-cli-usageAfter installing, type/gpd-cli-usagein Claude Code to confirm it loaded.
Details
From the project READMEGPD 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.
Comments
Markdown supported