Agent skill

Gplay Screenshot Automation

Manage, validate, and upload Google Play listing screenshots and graphics with the gplay CLI.

MITAuto-check passedMobile

Install Gplay Screenshot Automation

skills CLI

$ npx skills add hanamizuki/solopreneur --skill gplay-screenshot-automation -a claude-code

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

GitHub CLI

$ gh skill install hanamizuki/solopreneur gplay-screenshot-automation --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-screenshot-automation .claude/skills/gplay-screenshot-automation && 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-screenshot-automation" agent skill from https://github.com/hanamizuki/solopreneur/tree/main/skills/android-dev/gplay-screenshot-automation into .claude/skills/gplay-screenshot-automation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "gplay-screenshot-automation", 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-screenshot-automation

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-screenshot-automation -a codex

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

GitHub CLI

$ gh skill install hanamizuki/solopreneur gplay-screenshot-automation --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-screenshot-automation .agents/skills/gplay-screenshot-automation && 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-screenshot-automation" agent skill from https://github.com/hanamizuki/solopreneur/tree/main/skills/android-dev/gplay-screenshot-automation into .agents/skills/gplay-screenshot-automation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "gplay-screenshot-automation", 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-screenshot-automation -a cursor

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

GitHub CLI

$ gh skill install hanamizuki/solopreneur gplay-screenshot-automation --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-screenshot-automation .cursor/skills/gplay-screenshot-automation && 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-screenshot-automation" agent skill from https://github.com/hanamizuki/solopreneur/tree/main/skills/android-dev/gplay-screenshot-automation into .cursor/skills/gplay-screenshot-automation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "gplay-screenshot-automation", 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-screenshot-automation

--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-screenshot-automation -a gemini-cli

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

GitHub CLI

$ gh skill install hanamizuki/solopreneur gplay-screenshot-automation --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-screenshot-automation .gemini/skills/gplay-screenshot-automation && 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-screenshot-automation" agent skill from https://github.com/hanamizuki/solopreneur/tree/main/skills/android-dev/gplay-screenshot-automation into .gemini/skills/gplay-screenshot-automation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "gplay-screenshot-automation", 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-screenshot-automation

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-screenshot-automation -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-screenshot-automation .github/skills/gplay-screenshot-automation && 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-screenshot-automation" agent skill from https://github.com/hanamizuki/solopreneur/tree/main/skills/android-dev/gplay-screenshot-automation into .github/skills/gplay-screenshot-automation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "gplay-screenshot-automation", 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-screenshot-automation -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-screenshot-automation --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-screenshot-automation .opencode/skills/gplay-screenshot-automation && 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-screenshot-automation" agent skill from https://github.com/hanamizuki/solopreneur/tree/main/skills/android-dev/gplay-screenshot-automation into .opencode/skills/gplay-screenshot-automation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "gplay-screenshot-automation", 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-screenshot-automation
GitHub stars: 152
Token cost: ~1.3k tokens
SKILL.md length: 342 words
Files: 2
Skills in repo: 31
Repo updated: Sep 26, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

Manage, validate, and upload Google Play listing screenshots and graphics with the gplay CLI.

Works in 4 steps: Validate before uploading → Upload → Replace existing screenshots → …
Organizing screenshots by locale and device type and pushing them to a Play listing via gplay images upload
SKILL.md covers Directory layout, Image types, 1) Validate before uploading and 2) Upload, plus 3 more sections
Calls jq and adb

What it does

Gplay Screenshot Automation is an agent skill from hanamizuki/solopreneur. Manage, validate, and upload Google Play listing screenshots and graphics with the gplay CLI. Use when organizing screenshots by locale and device type and pushing them to a Play listing via gplay images upload, sync import-images, or a release.

Its SKILL.md is about 1.3k 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

Organizing screenshots by locale and device type and pushing them to a Play listing via gplay images upload
Sync import-images

Example prompts

“/gplay-screenshot-automation”

Workflow steps

4 steps, taken from the step headings in SKILL.md.

Validate before uploading
Upload
Replace existing screenshots
Verify what's live

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
- adb
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 Screenshot Automation loads about 1.3k tokens when it runs. Until then it costs about 68 tokens; SKILL.md has 342 words of instructions outside code blocks.

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

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). 342 words, ~1,299 tokens.

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

name: gplay-screenshot-automation
description: Manage, validate, and upload Google Play listing screenshots and graphics with the gplay CLI. Use when organizing screenshots by locale and device type and pushing them to a Play listing via gplay images upload, sync import-images, or a release.

Google Play Screenshot Management

Use this skill to organize, validate, and upload Android screenshots and store graphics to a Google Play listing with gplay. This skill covers the gplay-specific upload/validate flow — not screenshot capture.

Capturing the raw images is standard Android tooling and not gplay-specific: take them with adb shell screencap (then adb pull), or drive state-based captures with an Espresso / UI Automator instrumentation test, switching emulator locale via setprop persist.sys.locale when you need per-language shots. Produce PNGs organized by locale and device type, then use the commands below.

Directory layout

gplay expects a Fastlane-style tree. sync import-images and release --screenshots-dir both read this shape:

metadata/
  en-US/
    images/
      phoneScreenshots/
        1_home.png
        2_search.png
      tenInchScreenshots/
        1_home.png
      featureGraphic.png
  de-DE/
    images/
      phoneScreenshots/
        1_home.png

Screenshots upload in filename order, so prefix with 1_, 2_, etc. to control ordering on the store.

Image types

Type	Usage
`phoneScreenshots`	Phone screenshots (required, 2-8)
`sevenInchScreenshots`	7-inch tablet screenshots
`tenInchScreenshots`	10-inch tablet screenshots
`tvScreenshots`	Android TV screenshots
`wearScreenshots`	Wear OS screenshots
`featureGraphic`	Feature graphic (1024x500)
`promoGraphic`	Promo graphic (180x120)
`icon`	App icon (512x512)
`tvBanner`	TV banner (1280x720)

Google Play requires PNG or JPEG (PNG recommended), max 8 MB per image.

1) Validate before uploading

Always validate the directory first — this catches count/dimension/format issues before you spend an upload:

bash

# Validate all locales
gplay validate screenshots --dir ./metadata --output table

# Validate a single locale
gplay validate screenshots --dir ./metadata --locale en-US --output table

2) Upload

Option A — bulk import (preferred)

Imports every image in the Fastlane tree in one command. Requires an open edit:

bash

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

gplay sync import-images \
  --package com.example.app \
  --edit "$EDIT_ID" \
  --dir ./metadata          # add --locale en-US to import one locale, --dry-run to preview

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

Option B — individual images

Use when you need fine control over specific files:

bash

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

gplay images upload \
  --package com.example.app \
  --edit "$EDIT_ID" \
  --locale en-US \
  --type phoneScreenshots \
  --file ./metadata/en-US/images/phoneScreenshots/1_home.png

gplay images upload \
  --package com.example.app \
  --edit "$EDIT_ID" \
  --locale en-US \
  --type featureGraphic \
  --file ./metadata/en-US/images/featureGraphic.png

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

Option C — as part of a release

Upload screenshots alongside a bundle in one release flow:

bash

gplay release \
  --package com.example.app \
  --track production \
  --bundle app-release.aab \
  --screenshots-dir ./metadata \
  --release-notes @release-notes.json

3) Replace existing screenshots

delete-all clears a type for a locale before re-uploading. It defaults --confirm to false and will refuse without it, so --confirm is REQUIRED:

bash

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

gplay images delete-all \
  --package com.example.app \
  --edit "$EDIT_ID" \
  --locale en-US \
  --type phoneScreenshots \
  --confirm

gplay images upload \
  --package com.example.app \
  --edit "$EDIT_ID" \
  --locale en-US \
  --type phoneScreenshots \
  --file ./metadata/en-US/images/phoneScreenshots/1_home.png

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

4) Verify what's live

bash

gplay images list \
  --package com.example.app \
  --edit "$EDIT_ID" \
  --locale en-US \
  --type phoneScreenshots \
  --output table

Agent behavior

Confirm exact flags with --help before running commands.
Always run gplay validate screenshots before uploading.
Prefer gplay sync import-images over many individual gplay images upload calls.
Every write goes through an edit: create → upload/import → validate → commit.
images delete-all needs --confirm; without it the command refuses.
Use explicit long flags (--package, --edit, --locale, --type, --file).
Default to JSON for machine steps, --output table for human review.

Files

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

SKILL.md
_VENDOR.md

Open the folder on GitHubat commit f43f001

Compare with similar skills

Gplay Screenshot Automation 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 Screenshot Automation compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Gplay Screenshot Automation this skillhanamizuki/solopreneur	152	—	~1.3k	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 Screenshot Automation

What does Gplay Screenshot Automation do?

Manage, validate, and upload Google Play listing screenshots and graphics with the gplay CLI. Gplay Screenshot Automation is an agent skill from hanamizuki/solopreneur. Manage, validate, and upload Google Play listing screenshots and graphics with the gplay CLI.

When should I use Gplay Screenshot Automation?

Gplay Screenshot Automation fits situations like: organizing screenshots by locale and device type and pushing them to a Play listing via gplay images upload; sync import-images.

How do I install Gplay Screenshot Automation in Claude Code?

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

How do I install Gplay Screenshot Automation in Codex?

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

Can I use Gplay Screenshot Automation 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-screenshot-automation -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-screenshot-automation, .gemini/skills/gplay-screenshot-automation, .github/skills/gplay-screenshot-automation and .opencode/skills/gplay-screenshot-automation in your project.

What does Gplay Screenshot Automation need to run?

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

Does Gplay Screenshot Automation 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 Screenshot Automation 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 Screenshot Automation use?

Gplay Screenshot Automation 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 Screenshot Automation use?

About 1.3k tokens (SKILL.md is roughly 5.2k 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 Screenshot Automation?

Skills that share tags, products or a category with Gplay Screenshot Automation: 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 Screenshot Automation?

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 Screenshot Automation

Facts

At a glance

What it does

When your agent uses it

Example prompts

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Google Play Screenshot Management

Directory layout

Image types

1) Validate before uploading

2) Upload

Option A — bulk import (preferred)

Option B — individual images

Option C — as part of a release

3) Replace existing screenshots

4) Verify what's live

Agent behavior

Files

Compare with similar skills

Similar skills

More from hanamizuki/solopreneur

Related

Questions about Gplay Screenshot Automation