asc-localize-metadata

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

70|4|Updated Jul 22, 2025
One-click install
npx skills add https://github.com/AlexW00/Zettel --skill asc-localize-metadata-alexw00
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: asc-localize-metadata
Source: https://github.com/AlexW00/Zettel/tree/main/.agents/skills/asc-localize-metadata
Command: npx skills add https://github.com/AlexW00/Zettel --skill asc-localize-metadata-alexw00

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Localizing App Store listings manually means copying descriptions, keywords, and release notes into App Store Connect for every locale, which is slow and error-prone. This Skill automates downloading source metadata, translating it with an LLM, and uploading localized versions back to App Store Connect. ## Core Features & Use Cases - Bulk Localization Sync: Download version and app-info localizations as .strings files, translate them, and upload them back with the asc CLI. - Locale-Aware Translation Rules: Enforces formal register, character limits (30/100/170/4000 chars), and locale-appropriate keyword research instead of literal translation. - Deterministic ID Resolution: Works with explicit app, version, and app-info IDs to avoid accidental edits to the wrong listing. - Use Case: You are releasing an update for your iOS app and want to add German, French, and Japanese listings. The Skill pulls your en-US metadata, produces validated translations, and uploads them after your approval. ## Quick Start Localize my app's App Store metadata from en-US into de-DE and fr-FR and upload the translations to App Store Connect.

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 from the command line?▼

Use the asc CLI to download localizations as .strings files with asc localizations download, translate each field per locale, then upload with asc localizations upload. Version fields like description and keywords use --version, while name and subtitle use --type app-info.

How to translate App Store keywords for other languages?▼

Do not translate keywords literally. Research terms users in that locale actually search for, keep them comma-separated under 100 characters, avoid duplicates, and do not include the app name since Apple adds it automatically.

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

Name and subtitle allow 30 characters, keywords 100, promotional text 170, and description plus what's new 4000 each. Validate every translation against these limits before uploading, and shorten text rather than truncating mid-sentence.

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 with --type app-info.

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

Yes, promotionalText can be updated anytime 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.