How do I install the Gpc CLI Usage skill?

Run npx skillmds@latest add megastep/gpc-cli-usage in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Gpc CLI Usage safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Gpc CLI Usage?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Gpc CLI Usage free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Gpc CLI Usage?

megastep (@megastep) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Gpc CLI Usage by megastep — Agent Skill

Name: Gpc CLI Usage
Author: megastep

File contents

GPC CLI Usage

Use this skill when you need the right gpc command shape, global flags, or setup flow.

Resolve package and profile first

gpc can get the package name from several places. Prefer the most local source already present in the project:

gpc init --package com.example.app
gpc auth login --credentials ~/.config/gpc/service-account.json --name work --default-package com.example.app
gpc auth current

Package resolution order is effectively:

--package
GPC_PACKAGE
current profile default package
nearest .gpc.yaml

If none are set, add --package explicitly.

Command discovery

Confirm the real command tree before composing anything non-trivial:

gpc --help
gpc bundles --help
gpc tracks update --help
gpc testing testers add --help

Global flags

Common global flags:

--package, -p
--profile
--output, -o with json, table, minimal, tsv, csv, yaml
--pretty
--quiet, -q
--debug
--timeout
--dry-run
--edit-mode with live, stage, open

Default output is JSON. Use -o table for human review and JSON for piping.

gpc apps list -o table
gpc reviews list -o json | jq .
gpc tracks list --pretty

Edit-backed mutations

Many mutating commands support edit submission control. Prefer --edit-mode over legacy compatibility flags:

gpc bundles upload --file app.aab --track production --edit-mode=stage
gpc listings sync --dir ./metadata --edit-mode=open
gpc edits commit --edit-id EDIT_ID --edit-mode=stage

Compatibility aliases still exist during rollout:

--stage
--commit=false

Prefer not to introduce those in new examples unless you are maintaining old scripts.

Auth and setup

Recommended setup paths:

gpc setup --auto
gpc auth list
gpc auth switch --name work
gpc doctor
gpc doctor --verbose

Useful environment variables:

GPC_PACKAGE
GPC_PROFILE
GPC_OUTPUT
GPC_EDIT_MODE
GPC_TIMEOUT
GPC_CREDENTIALS_PATH
GPC_CREDENTIALS_B64

Agent behavior

Prefer examples that work with a configured package instead of always repeating --package.
Add --package explicitly when there is no evidence that a default package is configured.
Use --dry-run before destructive operations when supported.
Use --confirm explicitly for destructive commands; never simulate confirmation with shell tricks.

---name: gpc-cli-usagedescription: Guidance for using the Play Console CLI (gpc) — package resolution, profiles, project config, output formats, edit submission modes, and safety conventions. Use when asked to run or design gpc commands.---# GPC CLI UsageUse this skill when you need the right `gpc` command shape, global flags, or setup flow.## Resolve package and profile first`gpc` can get the package name from several places. Prefer the most local source already present in the project:```bashgpc init --package com.example.appgpc auth login --credentials ~/.config/gpc/service-account.json --name work --default-package com.example.appgpc auth current```Package resolution order is effectively:- `--package`- `GPC_PACKAGE`- current profile default package- nearest `.gpc.yaml`If none are set, add `--package` explicitly.## Command discoveryConfirm the real command tree before composing anything non-trivial:```bashgpc --helpgpc bundles --helpgpc tracks update --helpgpc testing testers add --help```## Global flagsCommon global flags:- `--package`, `-p`- `--profile`- `--output`, `-o` with `json`, `table`, `minimal`, `tsv`, `csv`, `yaml`- `--pretty`- `--quiet`, `-q`- `--debug`- `--timeout`- `--dry-run`- `--edit-mode` with `live`, `stage`, `open`Default output is JSON. Use `-o table` for human review and JSON for piping.```bashgpc apps list -o tablegpc reviews list -o json | jq .gpc tracks list --pretty```## Edit-backed mutationsMany mutating commands support edit submission control. Prefer `--edit-mode` over legacy compatibility flags:```bashgpc bundles upload --file app.aab --track production --edit-mode=stagegpc listings sync --dir ./metadata --edit-mode=opengpc edits commit --edit-id EDIT_ID --edit-mode=stage```Compatibility aliases still exist during rollout:- `--stage`- `--commit=false`Prefer not to introduce those in new examples unless you are maintaining old scripts.## Auth and setupRecommended setup paths:```bashgpc setup --autogpc auth listgpc auth switch --name workgpc doctorgpc doctor --verbose```Useful environment variables:- `GPC_PACKAGE`- `GPC_PROFILE`- `GPC_OUTPUT`- `GPC_EDIT_MODE`- `GPC_TIMEOUT`- `GPC_CREDENTIALS_PATH`- `GPC_CREDENTIALS_B64`## Agent behavior- Prefer examples that work with a configured package instead of always repeating `--package`.- Add `--package` explicitly when there is no evidence that a default package is configured.- Use `--dry-run` before destructive operations when supported.- Use `--confirm` explicitly for destructive commands; never simulate confirmation with shell tricks.

Frequently asked questions

Gpc CLI Usage