gplay-screenshot-automation

Automate Android screenshot capture, framing, and upload to Google Play via gplay CLI.

127|8|Updated Apr 6, 2026
One-click install
npx skills add https://github.com/hanamizuki/solopreneur --skill gplay-screenshot-automation-hanamizuki
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gplay-screenshot-automation
Source: https://github.com/hanamizuki/solopreneur/tree/main/plugins/android-dev/skills/gplay-screenshot-automation
Command: npx skills add https://github.com/hanamizuki/solopreneur --skill gplay-screenshot-automation-hanamizuki

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates repetitive Android screenshot capture across multiple devices and locales and uploads results to Google Play, reducing manual QA time and errors in store listings.

Core Features & Use Cases

  • Automated multi-device screenshot capture using adb, Espresso, and UI Automator.
  • Locale-aware captures with emulator locale switching and per-locale directories.
  • Device framing with frameit or custom framing scripts to produce store-ready assets.
  • Upload via gplay CLI, including batch imports and per-locale organization.
  • CI/CD-friendly workflow for end-to-end screenshot pipelines.

Quick Start

Set up your environment, then run the gplay-screenshot-automation workflow to capture, frame, and upload screenshots for all locales and devices.

Frequently Asked Questions about gplay-screenshot-automation

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate Android screenshots for Google Play listings across multiple locales?

Automating Android screenshots for Google Play involves capturing images on emulators or devices using Espresso and UI Automator, then uploading them via the gplay CLI. The workflow handles multi-device and multi-locale organization for store assets.

What's the best way to automate screenshot capture and upload in an Android CI/CD pipeline?

Integrating an end-to-end screenshot pipeline into your CI/CD workflow is the best way to automate capture and upload. It handles repetitive Android screenshot capture, device framing, and Google Play uploads via gplay CLI, reducing manual QA time.

Do I need adb and Espresso to automate Android screenshot capture for app store listings?

Yes, you need adb to interact with emulators or devices and Espresso or UI Automator to drive the app interface for screenshot capture. These tools are required to automate the multi-device capture process before uploading via gplay CLI.

Can I frame Android screenshots for Google Play using custom scripts after capturing them on emulators?

Yes, you can frame Android screenshots using frameit or custom framing scripts after capturing them on emulators. This process produces store-ready assets by adding device frames before organizing and uploading them via the gplay CLI.

Why does my automated Android screenshot pipeline fail to organize per-locale directories for Google Play?

An automated Android screenshot pipeline may fail to organize per-locale directories if emulator locale switching is not properly configured before capture. Correct locale switching ensures screenshots are saved into the correct per-locale directories for gplay CLI uploads.