Agent skill

Gplay Testers Orchestration

Manage testers for Google Play testing tracks (internal, closed alpha/beta, custom) using edit sessions.

MITAuto-check passedMobile

Install Gplay Testers Orchestration

skills CLI

$ npx skills add hanamizuki/solopreneur --skill gplay-testers-orchestration -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install hanamizuki/solopreneur gplay-testers-orchestration --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/hanamizuki/solopreneur.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/android-dev/gplay-testers-orchestration .claude/skills/gplay-testers-orchestration && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Paste into Claude Code

Install the "gplay-testers-orchestration" agent skill from https://github.com/hanamizuki/solopreneur/tree/main/skills/android-dev/gplay-testers-orchestration into .claude/skills/gplay-testers-orchestration/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "gplay-testers-orchestration", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/hanamizuki/solopreneur/tree/main/skills/android-dev/gplay-testers-orchestration

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add hanamizuki/solopreneur --skill gplay-testers-orchestration -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install hanamizuki/solopreneur gplay-testers-orchestration --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/hanamizuki/solopreneur.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/android-dev/gplay-testers-orchestration .agents/skills/gplay-testers-orchestration && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "gplay-testers-orchestration" agent skill from https://github.com/hanamizuki/solopreneur/tree/main/skills/android-dev/gplay-testers-orchestration into .agents/skills/gplay-testers-orchestration/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "gplay-testers-orchestration", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add hanamizuki/solopreneur --skill gplay-testers-orchestration -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install hanamizuki/solopreneur gplay-testers-orchestration --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/hanamizuki/solopreneur.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/android-dev/gplay-testers-orchestration .cursor/skills/gplay-testers-orchestration && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "gplay-testers-orchestration" agent skill from https://github.com/hanamizuki/solopreneur/tree/main/skills/android-dev/gplay-testers-orchestration into .cursor/skills/gplay-testers-orchestration/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "gplay-testers-orchestration", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/hanamizuki/solopreneur.git --path skills/android-dev/gplay-testers-orchestration

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add hanamizuki/solopreneur --skill gplay-testers-orchestration -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install hanamizuki/solopreneur gplay-testers-orchestration --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/hanamizuki/solopreneur.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/android-dev/gplay-testers-orchestration .gemini/skills/gplay-testers-orchestration && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "gplay-testers-orchestration" agent skill from https://github.com/hanamizuki/solopreneur/tree/main/skills/android-dev/gplay-testers-orchestration into .gemini/skills/gplay-testers-orchestration/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "gplay-testers-orchestration", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install hanamizuki/solopreneur gplay-testers-orchestration

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add hanamizuki/solopreneur --skill gplay-testers-orchestration -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/hanamizuki/solopreneur.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/android-dev/gplay-testers-orchestration .github/skills/gplay-testers-orchestration && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "gplay-testers-orchestration" agent skill from https://github.com/hanamizuki/solopreneur/tree/main/skills/android-dev/gplay-testers-orchestration into .github/skills/gplay-testers-orchestration/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "gplay-testers-orchestration", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add hanamizuki/solopreneur --skill gplay-testers-orchestration -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install hanamizuki/solopreneur gplay-testers-orchestration --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/hanamizuki/solopreneur.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/android-dev/gplay-testers-orchestration .opencode/skills/gplay-testers-orchestration && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "gplay-testers-orchestration" agent skill from https://github.com/hanamizuki/solopreneur/tree/main/skills/android-dev/gplay-testers-orchestration into .opencode/skills/gplay-testers-orchestration/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "gplay-testers-orchestration", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: gplay-testers-orchestration
GitHub stars: 152
Token cost: ~1.2k tokens
SKILL.md length: 350 words
Files: 2
Skills in repo: 31
Repo updated: Sep 26, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

Manage testers for Google Play testing tracks (internal, closed alpha/beta, custom) using edit sessions.

Assigning testers
SKILL.md covers Testing tracks, Tester commands, Assign testers inside an edit… and Create a closed testing track, plus 2 more sections
Calls jq
Creating closed tracks

What it does

Gplay Testers Orchestration is an agent skill from hanamizuki/solopreneur. Manage testers for Google Play testing tracks (internal, closed alpha/beta, custom) using edit sessions. Use when assigning testers, creating closed tracks, or promoting builds between tracks.

Its SKILL.md is about 1.2k tokens, which your agent loads only when the skill is triggered. The skill folder holds 1 other file (for example `_VENDOR.md`).

It sits in Mobile. It works with Android. The repository describes itself as: Skills and agents for solopreneurs — ship, review, debug, and think through problems with AI. The licence is MIT.

When your agent uses it

Assigning testers
Creating closed tracks
Promoting builds between tracks

Example prompts

“/gplay-testers-orchestration”

What it can do on your machine

Read from SKILL.md and the folder at commit f43f001. It shows what the files ask for, not the result of running them.

Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
- jq
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Gplay Testers Orchestration loads about 1.2k tokens when it runs. Until then it costs about 55 tokens; SKILL.md has 350 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~55
When it runs · the whole SKILL.md, loaded when a task matches: ~1.2k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from hanamizuki/solopreneur at commit f43f001, republished under its MIT licence (© hanamizuki). 350 words, ~1,233 tokens.

Download SKILL.mdSave it as .claude/skills/gplay-testers-orchestration/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.

name: gplay-testers-orchestration
description: Manage testers for Google Play testing tracks (internal, closed alpha/beta, custom) using edit sessions. Use when assigning testers, creating closed tracks, or promoting builds between tracks.

Testers Orchestration for Google Play

Use this skill to assign testers to a track and promote builds through the testing funnel. All tester changes happen inside an edit session and take effect only after gplay edits commit.

Testing tracks

Track	Type	Max testers	Review	Access
`internal`	Internal	100	No	Instant
`alpha`	Closed testing	Unlimited	No	Minutes
`beta`	Open or closed testing	Unlimited	No/Yes	Minutes
custom track	Closed testing	Unlimited	No	Minutes
`production`	Public	Unlimited	Yes	Days

alpha is a closed track (invite-only), not public. Testers on internal and closed tracks are managed by email address or by Google Group.

Tester commands

gplay testers has only three subcommands. There is no testers list — to list the testers on a track, use testers get.

gplay testers get — read the testers on a track.
gplay testers update — replace the entire tester set (emails/groups not included are removed).
gplay testers patch — merge with the existing set (preserves fields you omit).

List (get) testers for a track

bash

gplay testers get \
  --package com.example.app \
  --edit $EDIT_ID \
  --track alpha

Assign testers (replace the whole set)

bash

gplay testers update \
  --package com.example.app \
  --edit $EDIT_ID \
  --track alpha \
  --emails "tester1@example.com,tester2@example.com"

By Google Group instead of individual emails:

bash

gplay testers update \
  --package com.example.app \
  --edit $EDIT_ID \
  --track alpha \
  --google-groups "beta-testers@example.com,qa-team@example.com"

Add testers without dropping existing ones (patch)

bash

gplay testers patch \
  --package com.example.app \
  --edit $EDIT_ID \
  --track alpha \
  --emails "newtester@example.com"

Remove a tester (update = replace with the reduced set)

update replaces the resource, so re-send only the testers you want to keep:

bash

CURRENT=$(gplay testers get --package com.example.app --edit $EDIT_ID --track alpha \
  | jq -r '.testers[]?')
KEEP=$(echo "$CURRENT" | grep -v "user@example.com" | paste -sd "," -)

gplay testers update \
  --package com.example.app \
  --edit $EDIT_ID \
  --track alpha \
  --emails "$KEEP"

Show full SKILL.md (146 more words)Show less

Assign testers inside an edit session (canonical flow)

Tester assignment is not a flag on gplay release. There is no --testers flag anywhere. The real flow is an edit session:

bash

# 1. Create an edit
EDIT_ID=$(gplay edits create --package com.example.app | jq -r '.id')

# 2. Upload the build
gplay bundles upload \
  --package com.example.app \
  --edit $EDIT_ID \
  --file app-release.aab

# 3. Assign the release to the track
gplay tracks update \
  --package com.example.app \
  --edit $EDIT_ID \
  --track alpha \
  --releases '[{"versionCodes":["123"],"status":"completed"}]'

# 4. Assign testers to the track
gplay testers update \
  --package com.example.app \
  --edit $EDIT_ID \
  --track alpha \
  --emails "tester1@example.com,tester2@example.com"

# 5. Commit (nothing applies until this succeeds)
gplay edits commit --package com.example.app --edit $EDIT_ID

Create a closed testing track

Custom closed tracks are created inside an edit, then get testers assigned the same way:

bash

EDIT_ID=$(gplay edits create --package com.example.app | jq -r '.id')

gplay tracks create \
  --package com.example.app \
  --edit $EDIT_ID \
  --track qa-ring

gplay testers update \
  --package com.example.app \
  --edit $EDIT_ID \
  --track qa-ring \
  --emails "qa1@example.com,qa2@example.com"

gplay edits commit --package com.example.app --edit $EDIT_ID

Promote a build between tracks

Promotion copies the source track's version codes to a destination track. --rollout is a fraction (0.0–1.0), not a percentage:

bash

# Internal -> closed alpha
gplay promote --package com.example.app --from internal --to alpha

# Closed beta -> production at 10% staged rollout
gplay promote --package com.example.app --from beta --to production --rollout 0.1

Agent behavior

There is no testers list subcommand; use gplay testers get --track <track> to read a track's testers.
Never pass --testers to gplay release; assign testers via testers update/patch inside an edit, then commit.
Use update to set the exact tester set, patch to add without removing.
--rollout values are fractions (0.1 = 10%), range 0.0–1.0.
Always gplay edits commit — tester changes are inert until committed.
Confirm flags with --help before running.

Files

SKILL.md and 1 other file in skills/android-dev/gplay-testers-orchestration of hanamizuki/solopreneur.

SKILL.md
_VENDOR.md

Open the folder on GitHubat commit f43f001

Compare with similar skills

Gplay Testers Orchestration next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Gplay Testers Orchestration compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Gplay Testers Orchestration this skillhanamizuki/solopreneur	152	—	~1.2k	Automated safety check: Pass	MIT	14 days ago
Compose Multiplatform Patternsmonta-app/ocpp-emulator	180	5 repos	~2k	Automated safety check: Pass	Apache-2.0	yesterday
Phone HarnessShawnPana/phone-harness	3.2k	—	~7.7k	Automated safety check: Pass	MIT	today
Stylessreichholf/dreamDroid	116	5 repos	~2.3k	Automated safety check: Pass	GPL-3.0	today
Argent Metro Debuggerbbplayer-app/BBPlayer	1.2k	—	~3.4k	Automated safety check: Pass	MIT	3 days ago
Android XML ResourceafkT/DevUtils	1.6k	—	~1.3k	Automated safety check: Pass	Apache-2.0	1 mo ago

Similar skills

Compose Multiplatform Patterns
monta-app/ocpp-emulator
Compose Multiplatform and Jetpack Compose patterns for KMP projects — state management, navigation, theming, performance, and platform-specific UI.
180 GitHub starsUsed in 5 repos~2k tokens
MobileAuto-check passed
Phone Harness
ShawnPana/phone-harness
Control the user's phone - an iPhone through the Mac's iPhone Mirroring window, an Android over adb, a rented cloud Android, or a cloud iPhone over HTTPS: open apps, tap, type, swipe, read the screen.
3.2k GitHub stars~7.7k tokensUpdated today
MobileAuto-check passed
Styles
sreichholf/dreamDroid
A skill your agent uses to integrate the Jetpack Compose Styles API into an Android project.
116 GitHub starsUsed in 5 repos~2.3k tokens
MobileAuto-check passed
Argent Metro Debugger
bbplayer-app/BBPlayer
Debug a JS runtime via CDP using argent debugger tools. An agent skill from bbplayer-app/BBPlayer.
1.2k GitHub stars~3.4k tokensUpdated 3 days ago
MobileAuto-check passed
Android XML Resource
afkT/DevUtils
统一 Android XML 资源命名：layout、drawable、mipmap、color、values、id 的前缀与 snakecase 规则；把颜色/圆角/描边/状态编码进文件名（bg、border、textcolor…selector）。
1.6k GitHub stars~1.3k tokensUpdated 1 mo ago
MobileAuto-check passed
Mobile QA
tloncorp/tlon-apps
Run a mobile QA checklist on a physical Android device over adb for tlon-apps, then triage what fails into fixes.
107 GitHub stars~2.4k tokensUpdated today
MobileAuto-check passed

Questions about Gplay Testers Orchestration

What does Gplay Testers Orchestration do?

Manage testers for Google Play testing tracks (internal, closed alpha/beta, custom) using edit sessions. Gplay Testers Orchestration is an agent skill from hanamizuki/solopreneur. Manage testers for Google Play testing tracks (internal, closed alpha/beta, custom) using edit sessions.

When should I use Gplay Testers Orchestration?

Gplay Testers Orchestration fits situations like: assigning testers; creating closed tracks; promoting builds between tracks.

How do I install Gplay Testers Orchestration in Claude Code?

Run `npx skills add hanamizuki/solopreneur --skill gplay-testers-orchestration -a claude-code`. Or copy the skill folder (skills/android-dev/gplay-testers-orchestration in hanamizuki/solopreneur) into .claude/skills/gplay-testers-orchestration in your project. Claude Code loads it when a task matches its description.

How do I install Gplay Testers Orchestration in Codex?

Run `npx skills add hanamizuki/solopreneur --skill gplay-testers-orchestration -a codex`. Or copy the skill folder (skills/android-dev/gplay-testers-orchestration in hanamizuki/solopreneur) into .agents/skills/gplay-testers-orchestration in your project. Codex loads it when a task matches its description.

Can I use Gplay Testers Orchestration in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add hanamizuki/solopreneur --skill gplay-testers-orchestration -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/gplay-testers-orchestration, .gemini/skills/gplay-testers-orchestration, .github/skills/gplay-testers-orchestration and .opencode/skills/gplay-testers-orchestration in your project.

What does Gplay Testers Orchestration need to run?

Going by SKILL.md and its folder, Gplay Testers Orchestration needs the command-line tools its instructions call (jq).

Does Gplay Testers Orchestration access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Gplay Testers Orchestration safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Gplay Testers Orchestration use?

Gplay Testers Orchestration is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Gplay Testers Orchestration use?

About 1.2k tokens (SKILL.md is roughly 4.9k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Gplay Testers Orchestration?

Skills that share tags, products or a category with Gplay Testers Orchestration: Compose Multiplatform Patterns (monta-app/ocpp-emulator, 180 stars), Phone Harness (ShawnPana/phone-harness, 3.2k stars), Styles (sreichholf/dreamDroid, 116 stars) and Argent Metro Debugger (bbplayer-app/BBPlayer, 1.2k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Gplay Testers Orchestration?

hanamizuki (a GitHub user) maintains it in hanamizuki/solopreneur, which has 152 GitHub stars. The repository holds 31 skills in this directory. The repository was last updated on September 26, 2026.

Source: hanamizuki/solopreneur on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install Gplay Testers Orchestration

Facts

At a glance

What it does

When your agent uses it

Example prompts

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Testers Orchestration for Google Play

Testing tracks

Tester commands

List (get) testers for a track

Assign testers (replace the whole set)

Add testers without dropping existing ones (patch)

Remove a tester (update = replace with the reduced set)

Assign testers inside an edit session (canonical flow)

Create a closed testing track

Promote a build between tracks

Agent behavior

Files

Compare with similar skills

Similar skills

More from hanamizuki/solopreneur

Related

Questions about Gplay Testers Orchestration