Agent skill · Media & Video

asc-localize-metadata

Automatically translate and sync App Store metadata (description, keywords, what's new, subtitle) to multiple languages using LLM translation and asc CLI. Use when asked to localize an app's App Store listing, translate app descriptions, or add new languages to App Store Connect.

rorkaigithub.com/rorkaiGitHub ↗
claude-codeMIT
Install
npx skills add rorkai/app-store-connect-cli-skills --skill asc-localize-metadata --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 1
SKILL.md size: 11 KB
Bundled scripts: none
Path: skills/asc-localize-metadata/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 948
Language: Python

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# 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 `--help` for the exact `asc` version: - `asc localizations --help` - `asc localizations download --help` - `asc localizations upload --help` - `asc apps info edit --help` - Prefer explicit long flags (`--app`, `--version`, `--version-id`, `--type`, `--app-info`). - Default output is JSON; use `--output table` only for human verification steps. - Prefer deterministic ID-based operations. Do not "pick the first row" via `head -1` unless the user explicitly agrees. ## Preconditions - Auth configured (`asc auth login` or `ASC_*` env vars) - Know your app ID (`asc apps list` to find it) - At least one locale (typically en-US) already has metadata in App Store Connect ## Supported Locales App Store Connect locales for version and app-info localizations: ``` ar-SA, ca, cs, da, de-DE, el, en-AU, en-CA, en-GB, en-US, es-ES, es-MX, fi, fr-CA, fr-FR, he, hi, hr, hu, id, it, ja, ko, ms, nl-NL, no, pl, pt-BR, pt-PT, ro, ru, sk, sv, th, tr, u

What's inside
Steps it walks through
  1. Command discovery and output conventions
  2. Preconditions
  3. Supported Locales
  4. Two Types of Metadata
  5. Version Localizations (per-release)
  6. App Info Localizations (app-level, persistent)
  7. Workflow
  8. Step 1: Resolve IDs
  9. Step 2: Download source locale
  10. Step 3: Translate with LLM
  11. Step 4: Upload translations
  12. Step 5: Verify
  13. Character Limits (enforce before upload!)
  14. Full Example: Add nl-NL and ru to Roxy Math
Commands it runs
Find app ID
asc apps list --output table
Find latest version ID
asc versions list --app "APP_ID" --state READY_FOR_DISTRIBUTION --output table
or for editable version:
asc versions list --app "APP_ID" --state PREPARE_FOR_SUBMISSION --output table
Find app info ID (for app-level fields like name/subtitle)
asc apps info list --app "APP_ID" --output table
Download version localizations to local .strings files
asc localizations download --version "VERSION_ID" --path "./localizations"
More from app-store-connect-cli-skills
All skills →
About this skill
What does the asc-localize-metadata skill do?

Automatically translate and sync App Store metadata (description, keywords, what's new, subtitle) to multiple languages using LLM translation and asc CLI. Use when asked to localize an app's App Store listing, translate app descriptions, or add new languages to App Store Connect.

How do I install it?

Run `npx skills add rorkai/app-store-connect-cli-skills --skill asc-localize-metadata --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From rorkai/app-store-connect-cli-skills, a repository with 948 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going