asc-localize-metadata
Automate App Store metadata translation and syncing across multiple languages using LLM and asc CLI.
- Translates version-level fields (description, keywords, what's new, promotional text) and app-level fields (name, subtitle, privacy URLs) to 34+ supported App Store locales
- Enforces character limits (30 for name/subtitle, 100 for keywords, 4000 for description/what's new, 170 for promotional text) and applies formal register guidelines for each target language
- Downloads source locale metadata as .strings files, translates via LLM with locale-specific keyword research, and uploads translations back to App Store Connect in bulk or individually
- Requires app ID, version ID (for version localizations), and app-info ID (for app-level fields); integrates with asc CLI for deterministic ID resolution and verification
asc localize metadata
Use this skill to pull English (or any source locale) App Store metadata, translate it with LLM, and push translations back to App Store Connect — all automated.
Command discovery and output conventions
- Always confirm flags with
--helpfor the exactascversion:asc localizations --helpasc localizations download --helpasc localizations upload --helpasc apps info edit --help
- Prefer explicit long flags (
--app,--version,--version-id,--type,--app-info). - Default output is JSON; use
--output tableonly for human verification steps. - Prefer deterministic ID-based operations. Do not "pick the first row" via
head -1unless the user explicitly agrees.
Preconditions
- Auth configured (
asc auth loginorASC_*env vars) - Know your app ID (
asc apps listto find it) - At least one locale (typically en-US) already has metadata in App Store Connect
More from rudrankriyam/app-store-connect-cli-skills
asc-cli-usage
Guidance for using asc cli in this repo (flags, output formats, pagination, auth, and discovery). Use when asked to run or design asc commands or interact with App Store Connect via the CLI.
2.3Kasc-xcode-build
Build, archive, export, upload, and manage Xcode version/build numbers with the current asc xcode helpers before App Store Connect upload or submission. Use when creating an IPA or PKG for upload.
2.3Kasc-release-flow
Determine whether an app is ready to submit, then drive the current App Store release flow with asc, including validation, staging, review submission, first-time availability, subscriptions, IAP, Game Center, and App Privacy checks.
2.2Kasc-submission-health
Validate App Store submission readiness, submit prepared versions, and monitor review status with current asc commands. Use when shipping or troubleshooting review submissions.
2.2Kasc-metadata-sync
Sync, validate, and apply App Store metadata with the current asc canonical metadata workflow. Use when updating metadata, localizations, keywords, or migrating legacy fastlane metadata.
2.2Kasc-testflight-orchestration
Orchestrate TestFlight distribution, groups, testers, and What to Test notes using asc. Use when rolling out betas.
2.1K