gplay-metadata-sync

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

43|6|Updated Feb 5, 2026
One-click install
npx skills add https://github.com/tamtom/gplay-cli-skills --skill gplay-metadata-sync
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gplay-metadata-sync
Source: https://github.com/tamtom/gplay-cli-skills/tree/main/skills/gplay-metadata-sync
Command: npx skills add https://github.com/tamtom/gplay-cli-skills --skill gplay-metadata-sync

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill streamlines the process of updating and synchronizing your Google Play Store listing's metadata and localizations, preventing errors and saving significant time.

Core Features & Use Cases

  • Metadata Synchronization: Export and import app listings (descriptions, titles, etc.) and images to and from the Play Store.
  • Fastlane Integration: Works seamlessly with the Fastlane directory structure for metadata management.
  • Validation and Comparison: Validate metadata against character limits and compare local changes with remote versions before importing.
  • Use Case: You need to update the app's short description and add new screenshots for five different languages. This Skill allows you to export the current metadata, make your edits locally in the Fastlane structure, validate them, and then import the changes efficiently.

Quick Start

Use the gplay-metadata-sync skill to export all listings for the package 'com.example.app' to the './fastlane/metadata/android' directory.

Frequently Asked Questions about gplay-metadata-sync

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

FAQPage Schema
How do I sync app localization metadata to the Google Play Store?

To sync app localization metadata, you can export current listings, edit text and visual assets locally in a Fastlane directory structure, validate character limits, and import changes back to the Google Play Store.

Can I validate Play Store metadata character limits before uploading?

Yes, you can validate Play Store metadata against character limits before uploading. The process compares local changes with remote versions to ensure titles and descriptions meet platform requirements before importing.

How do I export Google Play Store listings for local editing?

You can export Google Play Store listings by pulling app titles, text descriptions, and visual assets like screenshots directly into a local Fastlane-compatible directory structure for offline editing.

Does this metadata sync workflow use the Fastlane directory structure?

Yes, the metadata sync process works seamlessly with the Fastlane directory structure. It organizes exported app listings, localizations, and visual assets into standard Fastlane metadata folders for streamlined management.

What is the best way to update app screenshots for multiple languages on the Play Store?

The best way to update app screenshots across multiple languages is to export current listings, replace image assets in local Fastlane directories, and import the updated visual assets back to the Google Play Store.

Can I compare local metadata changes with the remote Google Play Store version?

Yes, you can compare local metadata changes with the remote Google Play Store version. This comparison validates updated titles and descriptions against character limits before executing the final import sync.