asc-localize-metadata

Translate and sync App Store metadata across locales using LLM translation and the asc CLI.

Updated Feb 16, 2026
One-click install
npx skills add https://github.com/dustinober1/sundee-fundee-ios --skill asc-localize-metadata-dustinober1
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: asc-localize-metadata
Source: https://github.com/dustinober1/sundee-fundee-ios/tree/main/SundeeFundeeApp/.agents/skills/asc-localize-metadata
Command: npx skills add https://github.com/dustinober1/sundee-fundee-ios --skill asc-localize-metadata-dustinober1

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Localizing App Store listings into dozens of languages is slow and error-prone when done manually through App Store Connect, and literal keyword translations often miss what local users actually search for. ## Core Features & Use Cases - Automated Localization Workflow: Downloads source-locale metadata as .strings files, translates with LLM following App Store rules, and uploads results back via the asc CLI. - Version and App-Info Coverage: Handles per-version fields (description, keywords, whatsNew, promotionalText) and app-level fields (name, subtitle, privacy URLs) with correct ID resolution. - Limit and Quality Enforcement: Validates character limits (30 for subtitle, 100 for keywords, 4000 for description) and applies locale-appropriate keywords rather than literal translations. - Use Case: You are shipping an update and need your en-US listing translated into nl-NL and ru. The skill resolves app and version IDs, downloads the English metadata, produces reviewed translations, uploads them, and verifies the result. ## Quick Start Ask the assistant to localize your App Store listing into Dutch and Russian using the asc-localize-metadata skill, providing your app name and target locales.

Frequently Asked Questions about asc-localize-metadata

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

FAQPage Schema
How do I localize App Store metadata with the asc CLI?▼

Resolve your app ID, version ID, and app-info ID, then download the source locale with asc localizations download, translate the .strings files, and upload with asc localizations upload. Verify results with asc localizations list.

How should I translate App Store keywords for other languages?▼

Do not translate keywords literally. Research terms native speakers actually search in that locale's App Store, keep them comma-separated under 100 characters, avoid duplicates, and omit the app name since Apple adds it automatically.

What is the difference between version localizations and app-info localizations?▼

Version localizations cover per-release fields like description, keywords, whatsNew, and promotionalText tied to a version ID. App-info localizations cover persistent app-level fields like name, subtitle, and privacy URLs tied to an app-info ID.

What are the App Store character limits for metadata fields?▼

Name and subtitle allow 30 characters, keywords 100, promotional text 170, and description and whatsNew 4000 each. Validate translations against these limits before uploading and shorten text rather than truncating mid-sentence.

Can I update App Store promotional text without submitting a new version?▼

Yes, promotionalText can be updated at any time without a new version submission. Other version-localized fields like description and whatsNew are tied to a specific version and require an editable version to exist.