gplay-screenshot-automation

Validate and upload Google Play listing screenshots with the gplay CLI.

Updated Mar 25, 2026
One-click install
npx skills add https://github.com/lettucebo/Skills --skill gplay-screenshot-automation-lettucebo
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gplay-screenshot-automation
Source: https://github.com/lettucebo/Skills/tree/main/skills/google-play-console-cli/gplay-screenshot-automation
Command: npx skills add https://github.com/lettucebo/Skills --skill gplay-screenshot-automation-lettucebo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Managing Google Play store listing screenshots across locales and device types is error-prone: wrong image counts, dimensions, or formats cause rejected uploads, and manual uploads through the Play Console do not scale. This Skill automates validation and upload of listing graphics through the gplay CLI. ## Core Features & Use Cases - Pre-upload validation: Run gplay validate screenshots against a Fastlane-style metadata directory to catch count, dimension, and format issues before uploading. - Bulk and individual uploads: Import an entire locale tree with gplay sync import-images, upload single images with gplay images upload, or attach screenshots to a release via gplay release --screenshots-dir. - Replace and verify flows: Clear existing screenshots with images delete-all --confirm and verify live images with gplay images list. - Use Case: You have localized screenshots for en-US and de-DE organized by device type. Validate the tree, import all images into an edit, validate the edit, and commit it to update the Play listing in one scripted flow. ## Quick Start Ask the agent to validate the screenshots in ./metadata and upload them to the Google Play listing for your package using gplay.

Frequently Asked Questions about gplay-screenshot-automation

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

FAQPage Schema
How do I upload screenshots to Google Play from the command line?▼

Use the gplay CLI: create an edit with gplay edits create, then run gplay sync import-images with --dir pointing to your Fastlane-style metadata tree, and finish with gplay edits validate and gplay edits commit.

How to validate Google Play screenshots before uploading?▼

Run gplay validate screenshots --dir ./metadata to check all locales, or add --locale en-US for a single locale. This catches count, dimension, and format problems before you spend an upload.

What directory structure does gplay expect for screenshots?▼

gplay expects a Fastlane-style tree: metadata/<locale>/images/<type>/, where types include phoneScreenshots, sevenInchScreenshots, tenInchScreenshots, tvScreenshots, wearScreenshots, featureGraphic, and icon. Prefix filenames with numbers to control ordering.

What image formats and sizes does Google Play accept for screenshots?▼

Google Play requires PNG or JPEG images, with PNG recommended, and a maximum of 8 MB per image. Phone screenshots are required with 2 to 8 images per listing.

Why does gplay images delete-all refuse to run?▼

The delete-all command defaults --confirm to false and refuses to run without it as a safety measure. Pass --confirm explicitly, then re-upload replacement images within the same edit before committing.