asc-localize-metadata

Translate and synchronize App Store metadata into target locales via asc CLI.

Updated Apr 4, 2026
One-click install
npx skills add https://github.com/curtislmartin/daily-ascent-engineering --skill asc-localize-metadata-curtislmartin
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: asc-localize-metadata
Source: https://github.com/curtislmartin/daily-ascent-engineering/tree/main/skills_repo/asc-localize-metadata
Command: npx skills add https://github.com/curtislmartin/daily-ascent-engineering --skill asc-localize-metadata-curtislmartin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It removes the manual, error-prone work of copying, translating, validating, and uploading App Store Connect metadata across multiple locales, preventing character-limit mistakes and accidental overwrites.

Core Features & Use Cases

  • Deterministic ID resolution and download: Find and download version and app-info localizations via asc CLI to create a safe working copy.
  • LLM-assisted, rule-driven translation: Translate description, whatsNew, promotionalText, subtitle, and keywords with locale-specific tone, keyword strategy, and strict character-limit enforcement.
  • Safe upload and verification: Produce .strings files or execute field-level asc commands, validate lengths, show diffs, and verify successful uploads per-locale.
  • Use Case: Localize an English release into multiple App Store Connect locales while preserving marketing tone and ensuring each field meets Apple character limits.

Quick Start

Use the asc-localize-metadata skill to download the en-US metadata, generate LLM translations for nl-NL, validate lengths, and prepare .strings files for upload.

Frequently Asked Questions about asc-localize-metadata

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

FAQPage Schema
How do I translate and sync App Store metadata into multiple locales?

To translate and sync App Store metadata, you can use LLM-guided rules to translate version-level and app-info localizations, validate character limits, and upload via asc CLI commands.

How does LLM-assisted localization handle App Store character limits?

LLM-assisted localization handles App Store character limits by applying strict, per-field character-limit enforcement during the translation of description, keywords, and promotional text before uploading.

Can I use asc CLI to download and upload App Store Connect localizations?

Yes, you can use asc CLI to deterministically resolve app and version IDs, download en-US localizations to a safe working copy, and execute field-level upload commands for target locales.

What is the best way to localize App Store keywords for different regions?

The best way to localize App Store keywords is using LLM-guided translation with locale-specific keyword strategies, ensuring translated terms meet Apple's strict character limits for each target region.

Do I need asc authentication to prepare .strings files for App Store localization?

Yes, asc authentication is required to resolve app, version, and app-info IDs, download existing metadata, and verify successful field-level uploads after preparing your .strings files.

Why does App Store Connect localization fail when updating version metadata?

App Store Connect localization fails when character-limit mistakes or accidental overwrites occur during manual updates, which is prevented by validating lengths and showing diffs before upload.