How do I install the Gplay Setup skill?

Run npx skillmds@latest add pollyglot/gplay-setup 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 Gplay Setup 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 Gplay Setup?

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 Gplay Setup free to use?

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

Who published Gplay Setup?

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

Gplay Setup by pollyglot — Agent Skill

Name: Gplay Setup
Author: PollyGlot

Gplay Setup

Onboard gplay authentication from zero with the `auth` namespace. Use when setting up gplay auth for the first time, switching or rotating service accounts, managing stored accounts, or diagnosing why an authenticated gplay command fails with an auth error (exit 10/11).

PollyGlot Updated Sep 21, 2026

File contents

gplay setup (auth onboarding)

Get gplay talking to the Google Play Developer API. This skill covers the auth namespace end to end; for the conventions every command shares (credential resolution order, exit codes, output), see gplay-cli-usage.

The credential

gplay authenticates as a Google Cloud service account with the Android Publisher role, invited to your Play Console. You supply its JSON key one of three ways (resolution order in gplay-cli-usage):

GPLAY_SERVICE_ACCOUNT, a path to the JSON file or the inline JSON itself (handy for CI secrets).
--service-account <path-or-json> on any command, overrides the env.
A stored Account registered with gplay auth login (the credential lands in the OS keystore, see gplay auth status for where).

First-run flow

# 1. Register the service account as the active Account.
gplay auth login --service-account ./service_account.json

# 2. Confirm what gplay will use, and where the credential lives.
gplay auth status

# 3. Run ordered diagnostics (credential valid? scopes? developer id?).
gplay auth doctor

auth status prints the active Account, the keystore backend, and the credential's location. auth doctor runs ordered checks and is the first thing to reach for when an authenticated command fails; it pinpoints whether the problem is a bad key (exit 10) or a service account that is valid but not invited on the app/account (exit 11).

Managing stored accounts

gplay auth list                     # every registered Account
gplay auth logout <name> --confirm  # remove an Account from the config + keystore

auth logout removes a stored credential, so it is --confirm-gated like every destructive write (missing → exit 3, naming the flag).

Use --account <name> on later commands to target a specific stored Account when you have more than one.

Verify, then hand off

Once gplay auth doctor is green, auth is done. Every other skill assumes the credential set up here; the next step is gplay-apps, to register a package (gplay apps add <package>) and pin it to the repo (gplay init).

---name: gplay-setupdescription: Onboard gplay authentication from zero with the `auth` namespace. Use when setting up gplay auth for the first time, switching or rotating service accounts, managing stored accounts, or diagnosing why an authenticated gplay command fails with an auth error (exit 10/11).---# gplay setup (auth onboarding)Get gplay talking to the Google Play Developer API. This skill covers the`auth` namespace end to end; for the conventions every command shares(credential resolution order, exit codes, output), see `gplay-cli-usage`.## The credentialgplay authenticates as a **Google Cloud service account** with the*Android Publisher* role, invited to your Play Console. You supply its JSONkey one of three ways (resolution order in `gplay-cli-usage`):- `GPLAY_SERVICE_ACCOUNT`, a **path** to the JSON file *or* the **inline JSON** itself (handy for CI secrets).- `--service-account <path-or-json>` on any command, overrides the env.- A stored **Account** registered with `gplay auth login` (the credential lands in the OS keystore, see `gplay auth status` for where).## First-run flow```bash# 1. Register the service account as the active Account.gplay auth login --service-account ./service_account.json# 2. Confirm what gplay will use, and where the credential lives.gplay auth status# 3. Run ordered diagnostics (credential valid? scopes? developer id?).gplay auth doctor````auth status` prints the active Account, the keystore backend, and thecredential's location. `auth doctor` runs ordered checks and is the firstthing to reach for when an authenticated command fails; it pinpoints whetherthe problem is a bad key (exit `10`) or a service account that is valid butnot invited on the app/account (exit `11`).## Managing stored accounts```bashgplay auth list # every registered Accountgplay auth logout <name> --confirm # remove an Account from the config + keystore````auth logout` removes a stored credential, so it is `--confirm`-gated likeevery destructive write (missing → exit `3`, naming the flag).Use `--account <name>` on later commands to target a specific stored Accountwhen you have more than one.## Verify, then hand offOnce `gplay auth doctor` is green, auth is done. Every other skill assumes thecredential set up here; the next step is `gplay-apps`, to register a package(`gplay apps add <package>`) and pin it to the repo (`gplay init`).

Frequently asked questions