gpd-cli-usage

Original：🇺🇸 English

Not Translated

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.

2installs

Sourcerudrankriyam/gpd-cli-skills

Added on2026-03-15

NPX Install

npx skill4agent add rudrankriyam/gpd-cli-skills gpd-cli-usage

SKILL.md Content

GPD CLI usage

Use this skill when you need to run or design

gpd

commands for Google Play Developer Console.

Command discovery

Always use

--help

to confirm commands and flags.

```
gpd --help
```
```
gpd publish --help
```
```
gpd monetization --help
```

Flag conventions

Use explicit long flags (for example:
```
--package
```
,
```
--track
```
,
```
--status
```
).
No interactive prompts; destructive operations require
```
--confirm
```
.
Use
```
--all
```
when the user wants all pages.

Output formats

Default output is minified JSON.
Use
```
--pretty
```
for readable JSON during debugging.

Authentication and defaults

Service account auth via
```
GPD_SERVICE_ACCOUNT_KEY
```
is required.

Validate access for a package:

gpd auth check --package com.example.app

Safety

Use
```
--dry-run
```
when available before destructive operations.
Prefer edit lifecycle (
```
gpd publish edit create
```
) for multi-step publishing.