store-metadata

Generate and upload multilingual store metadata for App Store and Google Play.

Updated Mar 26, 2026

Search Tags:#localization #metadata #fastlane #app-store #mobile-app #google-play #store-listing

Ready to run

npx skills add https://github.com/seungmanchoi/store-deploy-plugin --skill store-metadata-seungmanchoi

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: store-metadata
Source: https://github.com/seungmanchoi/store-deploy-plugin/tree/main/skills/store-metadata
Command: npx skills add https://github.com/seungmanchoi/store-deploy-plugin --skill store-metadata-seungmanchoi

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Generating accurate, localized metadata for app store listings is time-consuming and error-prone; this skill automates creation and uploading of titles, descriptions, keywords, and release notes for iOS and Android repositories in multiple languages. Without centralized tooling, teams struggle to maintain consistency across languages and platforms.

Core Features & Use Cases

Generate multilingual metadata files for iOS and Android in fastlane-friendly locations.
Ensure consistent naming, descriptions, keywords, and release notes across languages.
Integrate with fastlane to publish metadata to App Store Connect and Google Play Console, supporting teams releasing with multilingual content.

Quick Start

Run the store-metadata skill with target languages and platform to generate and upload multilingual metadata to App Store and Google Play.

Frequently Asked Questions about store-metadata

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

FAQPage Schema

How do I generate multilingual store metadata for App Store and Google Play?▼

Multilingual store metadata generation creates titles, descriptions, keywords, and release notes for iOS and Android storefronts. It enforces required fastlane file structures and validates language coverage before publishing to App Store Connect and Google Play Console.

What's the best way to localize app store listings with fastlane?▼

Localizing app store listings with fastlane requires generating metadata files in fastlane-friendly paths across multiple languages. This approach automates creation of consistent naming, descriptions, and release notes for en-US and ko, with scalable workflows for additional languages.

Does fastlane support publishing localized metadata to both App Store Connect and Google Play Console?▼

Fastlane supports publishing localized metadata to both App Store Connect and Google Play Console. The skill validates language coverage and enforces required file structures before uploading multilingual content for iOS and Android repositories.

Can I scale localization workflows for additional languages beyond English and Korean?▼

Localization workflows can scale to additional languages beyond en-US and ko. The skill handles multilingual content generation with consistent naming, descriptions, keywords, and release notes, validating full language coverage before publishing to storefronts.

Why does my fastlane metadata upload fail due to missing language files?▼

Fastlane metadata uploads fail when required language files are missing or improperly structured. The skill enforces required fastlane file structures and validates language coverage before publishing, ensuring all required localized metadata exists for App Store and Google Play.

Do I need fastlane to manage app store release notes across multiple languages?▼

Fastlane is required to upload multilingual app store metadata including release notes. The skill generates release notes and other metadata in fastlane-friendly locations, then integrates with fastlane to publish content to App Store Connect and Google Play Console.