asc-localize-metadata

Translates and syncs App Store metadata across locales using LLM translation and the asc CLI.

1|Updated Aug 9, 2026
One-click install
npx skills add https://github.com/OMIXEC/all-in-one-swift-skills --skill asc-localize-metadata-omixec
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: asc-localize-metadata
Source: https://github.com/OMIXEC/all-in-one-swift-skills/tree/main/skills/asc-localize-metadata
Command: npx skills add https://github.com/OMIXEC/all-in-one-swift-skills --skill asc-localize-metadata-omixec

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Localizing App Store listings into dozens of languages is slow and error-prone: each locale needs translated descriptions, keywords, subtitles, and release notes, all within strict App Store Connect character limits. This Skill automates the full round trip of downloading source metadata, translating it with an LLM, and uploading localized versions back to App Store Connect. ## Core Features & Use Cases - Automated metadata localization: Downloads source-locale metadata via asc localizations download, translates it with LLM guidance, and uploads per-locale .strings files with asc localizations upload. - Two metadata scopes: Handles both version localizations (description, keywords, whatsNew, promotionalText) and app-info localizations (name, subtitle, privacy URLs) with the correct asc commands for each. - Limit-aware translation rules: Enforces App Store character limits (name 30, subtitle 30, keywords 100, description 4000) and locale-appropriate keyword research instead of literal translation. - Use Case: You are shipping an update and need your listing in nl-NL and ru. The Skill resolves app/version IDs, pulls the en-US metadata, produces formal-register translations, shows them for approval, uploads, and verifies the result. ## Quick Start Ask the agent to localize your app's App Store metadata into Dutch and Russian using the asc CLI, starting from the existing en-US listing.

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?▼

Download the source locale with asc localizations download, translate the .strings files per target locale, then upload with asc localizations upload. Version fields use --version VERSION_ID, while name and subtitle use --type app-info with the app info ID.

How should App Store keywords be translated for other languages?▼

Keywords should not be literally translated. Research terms native speakers actually search for in that locale's App Store, keep them comma-separated under 100 characters, avoid duplicates, and do not include the app name since Apple adds it automatically.

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

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

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 every translation against these limits before uploading, and shorten over-limit 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 in App Store Connect.