skills.rest
hanamizuki
hanamizukiCOMMUNITY
Explore all skills by this author →
Website𝕏@hanamizukiGitHub

gplay-metadata-sync

Export, validate, and import Google Play metadata across locales.

127|8|Updated Apr 6, 2026
Search Tags:#automation#localization#fastlane#google-play#listings#play-metadata
One-click install
npx skills add https://github.com/hanamizuki/solopreneur --skill gplay-metadata-sync-hanamizuki
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gplay-metadata-sync
Source: https://github.com/hanamizuki/solopreneur/tree/main/plugins/android-dev/skills/gplay-metadata-sync
Command: npx skills add https://github.com/hanamizuki/solopreneur --skill gplay-metadata-sync-hanamizuki

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Keeping Google Play Store metadata and localization in sync across locales is tedious, error-prone, and slows releases.

Core Features & Use Cases

  • Export current listings and locale-specific assets to a Fastlane-friendly format for version control.
  • Validate, import, and apply updates to Google Play metadata and images across en-US, es-ES, fr-FR, and more locales.
  • Manage multi-locale workflows including screenshots, titles, and descriptions to maintain consistency across markets.

Quick Start

Export the current metadata, edit locale files locally, validate changes, and import updates to apply them to Google Play.

Frequently Asked Questions about gplay-metadata-sync

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

FAQPage Schema
How do I keep Google Play Store metadata in sync across multiple locales?▼

Keeping Google Play metadata in sync requires exporting current listings to a Fastlane-friendly format, editing locale files locally, validating changes, and re-importing updates to apply them consistently across markets.

What's the best way to automate Google Play localization for titles and descriptions?▼

Automating Google Play localization involves a repeatable export, validate, and import process using Fastlane-style metadata exports and the Play Console CLI workflow to manage multi-locale titles and descriptions.

Can I use Fastlane metadata exports to manage Google Play listings?▼

Yes, you can export current Google Play listings and locale-specific assets to a Fastlane-friendly format for version control, then validate and import updates back to the Play Console.

Does this Google Play metadata sync workflow support screenshots and media assets?▼

Yes, the multi-locale workflow manages screenshots, titles, descriptions, and media assets to maintain consistency across markets like en-US, es-ES, and fr-FR.

How do I validate Google Play listing changes before importing them?▼

You validate Google Play listing changes by editing exported locale files locally, then running a validation step to ensure consistency before importing updates through the Play Console CLI workflow.

Why does manual Google Play metadata localization slow down releases?▼

Manual Google Play metadata localization is tedious and error-prone because tracking titles, descriptions, and assets across multiple locales like en-US, es-ES, and fr-FR without automated export and import creates inconsistency and delays.

Related Skills

Explore More Marketing & Sales Skills→
hitoshura25hitoshura25
3

android-release-notes-structure

Create locale-aware Android release notes directories with fastlane metadata templates.

Community
Basic
tamtomtamtom
43

gplay-subscription-localization

Localize Google Play subscription titles, descriptions, and benefits across all supported locales.

Community
Intermediate
tamtomtamtom
43

gplay-metadata-sync

Synchronize Google Play Store metadata and localizations using a Fastlane-compatible directory structure.

Community
Intermediate
ImL1sImL1s
6

store-screenshot-beautifier

Composite device screenshots with AI backgrounds and text overlays for app store listings.

Community
Advanced