Agent skill

Gplay Metadata Sync

Metadata and localization sync (including Fastlane format) for Google Play Store listings.

MITAuto-check passedMobile

Install Gplay Metadata Sync

skills CLI

$ npx skills add hanamizuki/solopreneur --skill gplay-metadata-sync -a claude-code

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

GitHub CLI

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

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-metadata-sync -a codex

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

GitHub CLI

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

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

GitHub CLI

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

--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-metadata-sync -a gemini-cli

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

GitHub CLI

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

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

At a glance

Metadata and localization sync (including Fastlane format) for Google Play Store listings.

Works in 3 steps: Copy existing locale directory → Translate all text files → Import
Updating app descriptions
SKILL.md covers Fastlane Directory Structure, Export Metadata from Play Store, Import Metadata to Play Store and Compare Local vs Remote, plus 7 more sections
Reaches youtube.com

What it does

Gplay Metadata Sync is an agent skill from hanamizuki/solopreneur. Metadata and localization sync (including Fastlane format) for Google Play Store listings. Use when updating app descriptions, screenshots, or managing multi-locale metadata.

Its SKILL.md is about 1.4k 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, covering Internationalization and App store release. 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

Updating app descriptions
Managing multi-locale metadata

Example prompts

“/gplay-metadata-sync”

Workflow steps

3 steps, taken from the first numbered list in SKILL.md.

Copy existing locale directory
Translate all text files
Import

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
No scripts in the folder and no shell commands in SKILL.md (its code samples are bash).
From the folder's file list and the shell code blocks in SKILL.md.
Network
Hosts in commands or code, which the agent is likely to contact:
- youtube.com
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 Metadata Sync loads about 1.4k tokens when it runs. Until then it costs about 49 tokens; SKILL.md has 235 words of instructions outside code blocks.

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

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). 235 words, ~1,397 tokens.

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

name: gplay-metadata-sync
description: Metadata and localization sync (including Fastlane format) for Google Play Store listings. Use when updating app descriptions, screenshots, or managing multi-locale metadata.

Metadata Sync for Google Play

Use this skill when you need to update or sync Play Store metadata and localizations.

Fastlane Directory Structure

fastlane/metadata/android/
├── en-US/
│   ├── title.txt
│   ├── short_description.txt
│   ├── full_description.txt
│   ├── video.txt
│   └── images/
│       ├── phoneScreenshots/
│       │   ├── 1.png
│       │   └── 2.png
│       ├── sevenInchScreenshots/
│       ├── tenInchScreenshots/
│       ├── tvScreenshots/
│       ├── wearScreenshots/
│       ├── icon.png
│       └── featureGraphic.png
├── es-ES/
│   ├── title.txt
│   └── ...
└── fr-FR/
    └── ...

Export Metadata from Play Store

bash

# Export all listings to Fastlane format
gplay sync export-listings \
  --package com.example.app \
  --dir ./fastlane/metadata/android

# Export images
gplay sync export-images \
  --package com.example.app \
  --dir ./fastlane/metadata/android

Import Metadata to Play Store

bash

# Validate before importing (offline check)
gplay validate listing \
  --dir ./fastlane/metadata/android \
  --locale en-US

# Import all listings
gplay sync import-listings \
  --package com.example.app \
  --dir ./fastlane/metadata/android

# Import images
gplay sync import-images \
  --package com.example.app \
  --dir ./fastlane/metadata/android

Compare Local vs Remote

bash

# See what would change
gplay sync diff-listings \
  --package com.example.app \
  --dir ./fastlane/metadata/android

Manual Metadata Management

List all listings

bash

gplay listings list \
  --package com.example.app \
  --edit $EDIT_ID

Get specific locale

bash

gplay listings get \
  --package com.example.app \
  --edit $EDIT_ID \
  --locale en-US

Update listing

listings update sets all fields for a locale via individual flags (fields not provided are cleared). Use listings patch for partial updates.

bash

gplay listings update \
  --package com.example.app \
  --edit $EDIT_ID \
  --locale en-US \
  --title "My Awesome App" \
  --short-description "A short description under 80 characters" \
  --full-description "A full description under 4000 characters..." \
  --video "https://www.youtube.com/watch?v=VIDEO_ID"

Image Management

Upload screenshots

bash

gplay images upload \
  --package com.example.app \
  --edit $EDIT_ID \
  --locale en-US \
  --type phoneScreenshots \
  --file screenshot1.png

gplay images upload \
  --package com.example.app \
  --edit $EDIT_ID \
  --locale en-US \
  --type phoneScreenshots \
  --file screenshot2.png

Image types

phoneScreenshots - Phone screenshots (required)
sevenInchScreenshots - 7" tablet screenshots
tenInchScreenshots - 10" tablet screenshots
tvScreenshots - TV screenshots
wearScreenshots - Wear OS screenshots
icon - App icon
featureGraphic - Feature graphic (1024x500)

List images

bash

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

Delete image

bash

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

App Details

Get app details

bash

gplay details get \
  --package com.example.app \
  --edit $EDIT_ID

Update contact info

bash

gplay details update \
  --package com.example.app \
  --edit $EDIT_ID \
  --contact-email support@example.com \
  --contact-phone "+1234567890" \
  --contact-website "https://example.com"

Character Limits

Validate against Google Play limits:

Field	Limit
Title	30 characters
Short Description	80 characters
Full Description	4000 characters

bash

# Validate before upload
gplay validate listing \
  --dir ./fastlane/metadata/android \
  --locale en-US

Workflow Example

Complete metadata update workflow:

bash

# 1. Export current metadata
gplay sync export-listings \
  --package com.example.app \
  --dir ./metadata

# 2. Edit files locally
vi ./metadata/en-US/full_description.txt

# 3. Validate changes
gplay validate listing \
  --dir ./metadata \
  --locale en-US

# 4. See what will change
gplay sync diff-listings \
  --package com.example.app \
  --dir ./metadata

# 5. Import changes
gplay sync import-listings \
  --package com.example.app \
  --dir ./metadata

Multi-Locale Management

Create new locale

Copy existing locale directory:

bash

cp -r fastlane/metadata/android/en-US fastlane/metadata/android/es-ES

Translate all text files

Import:

bash

gplay sync import-listings \
  --package com.example.app \
  --dir ./fastlane/metadata/android

Supported Locales

Use Play Console locale codes:

en-US - English (United States)
es-ES - Spanish (Spain)
fr-FR - French (France)
de-DE - German (Germany)
ja-JP - Japanese (Japan)
etc.

Best Practices

Keep metadata in version control - Track changes over time
Validate before importing - Catch character limit errors
Use consistent formatting - Follow style guide
Test on different devices - Screenshots should represent actual app
Update regularly - Keep descriptions current with features
Localize properly - Don't use machine translation without review

Files

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

SKILL.md
_VENDOR.md

Open the folder on GitHubat commit f43f001

Compare with similar skills

Gplay Metadata Sync 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 Metadata Sync compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Gplay Metadata Sync this skillhanamizuki/solopreneur	152	—	~1.4k	Automated safety check: Pass	MIT	13 days ago
Asc Subscription Localizationrorkai/app-store-connect-cli-skills	1.1k	2 repos	~2.7k	Automated safety check: Pass	MIT	5 days ago
Screenshotsshortcuts/locationjoystick	104	—	~3.1k	Automated safety check: Pass	MIT	yesterday
Reply Reviewstimusus/Shuttle2	229	—	~1k	Automated safety check: Pass	Apache-2.0	today
Play Policy Insightsarindamxd/camerax-android	132	2 repos	~2.1k	Automated safety check: Pass	Apache-2.0	8 days ago
Pp Google Playmvanhorn/printing-press-library	2.1k	—	~3.4k	Automated safety check: Notes	Apache-2.0	today

Similar skills

Asc Subscription Localization
rorkai/app-store-connect-cli-skills
Bulk-localize subscription, subscription-group, and in-app purchase display names across App Store locales using asc, including API 4.4.1 version-scoped v2 resources.
1.1k GitHub starsUsed in 2 repos~2.7k tokens
MobileAuto-check passed
Screenshots
shortcuts/locationjoystick
Refresh all wiki/Play Store gallery screenshots from a connected Android device.
104 GitHub stars~3.1k tokensUpdated yesterday
MobileAuto-check passed
Reply Reviews
timusus/Shuttle2
Weekly Play Store review flow for S2: fetch new reviews, draft replies, get owner approval, then post.
229 GitHub stars~1k tokensUpdated today
MobileAuto-check passed
Play Policy Insights
arindamxd/camerax-android
Automated auditor designed to verify Android applications against Google Play Policy domains.
132 GitHub starsUsed in 2 repos~2.1k tokens
MobileAuto-check passed
Pp Google Play
mvanhorn/printing-press-library
Every public Google Play surface in one Go binary Trigger phrases: top grossing games on google play, google play app details for, track this app's rank over time, what changed on this play store…
2.1k GitHub stars~3.4k tokensUpdated today
MobileAuto-check: notes
Cometchat Android V6 Kotlin Customization
cometchat/cometchat-skills
Make the CometChat Android v6 UI match your app in the Kotlin XML Views cohort — theming via CometChatTheme.DayNight attributes, per-component styles, message-bubble styling, ViewHolder view slots…
132 GitHub stars~2.2k tokensUpdated 5 days ago
MobileAuto-check passed

Questions about Gplay Metadata Sync

What does Gplay Metadata Sync do?

Metadata and localization sync (including Fastlane format) for Google Play Store listings. Gplay Metadata Sync is an agent skill from hanamizuki/solopreneur. Metadata and localization sync (including Fastlane format) for Google Play Store listings.

When should I use Gplay Metadata Sync?

Gplay Metadata Sync fits situations like: updating app descriptions; managing multi-locale metadata.

How do I install Gplay Metadata Sync in Claude Code?

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

How do I install Gplay Metadata Sync in Codex?

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

Can I use Gplay Metadata Sync 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-metadata-sync -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-metadata-sync, .gemini/skills/gplay-metadata-sync, .github/skills/gplay-metadata-sync and .opencode/skills/gplay-metadata-sync in your project.

What does Gplay Metadata Sync need to run?

SKILL.md names no scripts, command-line tools or credentials: Gplay Metadata Sync is instructions for the agent only.

Does Gplay Metadata Sync access the network?

SKILL.md names 1 domain. In commands or code: youtube.com; the agent is likely to contact it when it follows the instructions. This is read from the text; nothing was executed.

Is Gplay Metadata Sync 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 Metadata Sync use?

Gplay Metadata Sync 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 Metadata Sync use?

About 1.4k tokens (SKILL.md is roughly 5.6k 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 Metadata Sync?

Skills that share tags, products or a category with Gplay Metadata Sync: Asc Subscription Localization (rorkai/app-store-connect-cli-skills, 1.1k stars), Screenshots (shortcuts/locationjoystick, 104 stars), Reply Reviews (timusus/Shuttle2, 229 stars) and Play Policy Insights (arindamxd/camerax-android, 132 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Gplay Metadata Sync?

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 Metadata Sync

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

Metadata Sync for Google Play

Fastlane Directory Structure

Export Metadata from Play Store

Import Metadata to Play Store

Compare Local vs Remote

Manual Metadata Management

List all listings

Get specific locale

Update listing

Image Management

Upload screenshots

Image types

List images

Delete image

App Details

Get app details

Update contact info

Character Limits

Workflow Example

Multi-Locale Management

Create new locale

Supported Locales

Best Practices

Files

Compare with similar skills

Similar skills

More from hanamizuki/solopreneur

Related

Questions about Gplay Metadata Sync