How do I install the Gplay Tracks skill?

Run npx skillmds@latest add pollyglot/gplay-tracks 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 Tracks 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 Tracks?

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

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

Who published Gplay Tracks?

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

Gplay Tracks by pollyglot — Agent Skill

Name: Gplay Tracks
Author: PollyGlot

Gplay Tracks

Inspect and manage Google Play release tracks and their testers. Use when checking what's on a track, creating a closed-testing track before an upload, auditing country availability (read-only), or setting the Google Groups authorized to test a closed track.

PollyGlot Updated Sep 21, 2026

File contents

gplay tracks (+ availability + testers)

Tracks are where releases live; testers are who may install a closed track. gplay folds the two together because they are operationally coupled (DESIGN §10). Shared conventions (auth, --package, output, exit codes) are in gplay-cli-usage; shipping builds onto tracks is gplay-release-flow.

Inspect tracks

gplay tracks list --package com.example.app          # every track on the app
gplay tracks view --track production                 # one track's full state

tracks view answers "is anything wrong on this track right now?": the latest release, its status, and rollout fraction.

Create a closed track

gplay tracks create qa-team

The create endpoint supports exactly one kind: a CLOSED_TESTING track on the DEFAULT (phone) form factor, so there is no --type / --form-factor flag, and there is no API path to create open/internal tracks (those exist already). Creating a track that already exists surfaces the API error (exit 30); gplay does not fake idempotency. Use --dry-run to preview the TrackConfig; there is no --confirm (a closed test track is low-stakes).

This is the other half of the release-flow trackhint: an upload/promote to a custom closed track that doesn't exist yet fails with exit 30 and tells you to run gplay tracks create <name> first; gplay never auto-creates a track as a side effect. See gplay-release-flow.

Country availability (read-only)

gplay tracks availability view --track production

Availability, which countries a track's artifacts ship to, is read-only at the Developer API level (ADR-0012): there is no writer. To change where an app is available, use the Play Console. The bare gplay tracks availability prints help; the read is availability view.

Testers (closed-track audience)

gplay testers list --track qa-team
gplay testers set --track qa-team --group qa@googlegroups.com,beta@googlegroups.com
gplay testers set --track qa-team --clear        # close the closed test

testers set is declarative: it replaces the whole audience (it maps 1:1 to testers.update; there is no add/remove). The API exposes only Google Groups, not individual tester emails. A bare set with neither --group nor --clear is refused (exit 2) so a forgotten --group can never silently wipe the list; empty the audience on purpose with --clear. No --confirm; --dry-run previews.

Typical closed-test setup

gplay tracks create qa-team
gplay testers set --track qa-team --group qa@googlegroups.com
gplay releases upload ./app.aab --track qa-team        # see gplay-release-flow

---name: gplay-tracksdescription: Inspect and manage Google Play release tracks and their testers. Use when checking what's on a track, creating a closed-testing track before an upload, auditing country availability (read-only), or setting the Google Groups authorized to test a closed track.---# gplay tracks (+ availability + testers)Tracks are where releases live; testers are who may install a closed track.gplay folds the two together because they are operationally coupled(DESIGN §10). Shared conventions (auth, `--package`, output, exit codes) arein `gplay-cli-usage`; shipping builds onto tracks is `gplay-release-flow`.## Inspect tracks```bashgplay tracks list --package com.example.app # every track on the appgplay tracks view --track production # one track's full state````tracks view` answers "is anything wrong on this track right now?": the latestrelease, its status, and rollout fraction.## Create a closed track```bashgplay tracks create qa-team```The create endpoint supports **exactly one kind**: a `CLOSED_TESTING` track onthe DEFAULT (phone) form factor, so there is no `--type` / `--form-factor`flag, and there is **no API path to create open/internal tracks** (those existalready). Creating a track that already exists surfaces the API error (exit`30`); gplay does not fake idempotency. Use `--dry-run` to preview the`TrackConfig`; there is no `--confirm` (a closed test track is low-stakes).> This is the other half of the release-flow **trackhint**: an> `upload`/`promote` to a custom closed track that doesn't exist yet fails with> exit `30` and tells you to run `gplay tracks create <name>` first; gplay> never auto-creates a track as a side effect. See `gplay-release-flow`.## Country availability (read-only)```bashgplay tracks availability view --track production```Availability, which countries a track's artifacts ship to, is **read-only**at the Developer API level (ADR-0012): there is no writer. To *change* where anapp is available, use the Play Console. The bare `gplay tracks availability`prints help; the read is `availability view`.## Testers (closed-track audience)```bashgplay testers list --track qa-teamgplay testers set --track qa-team --group qa@googlegroups.com,beta@googlegroups.comgplay testers set --track qa-team --clear # close the closed test````testers set` is **declarative**: it replaces the *whole* audience (it maps 1:1to `testers.update`; there is no add/remove). The API exposes **only GoogleGroups**, not individual tester emails. A bare `set` with neither `--group`nor `--clear` is refused (exit `2`) so a forgotten `--group` can never silentlywipe the list; empty the audience on purpose with `--clear`. No `--confirm`;`--dry-run` previews.## Typical closed-test setup```bashgplay tracks create qa-teamgplay testers set --track qa-team --group qa@googlegroups.comgplay releases upload ./app.aab --track qa-team # see gplay-release-flow```

Frequently asked questions