App Store Connect 元数据自动化本地化工具 - asc-localize-metadata 使用指南

asc-localize-metadata by rudrankriyam/app-store-connect-cli-skills

931 周安装量

598 GitHub Stars

GitHub

安装命令

npx skills add https://github.com/rudrankriyam/app-store-connect-cli-skills --skill asc-localize-metadata

AI/机器学习开发自动化

🇨🇳中文介绍

asc localize metadata

使用此技能可提取英文（或任何源语言）的 App Store 元数据，通过 LLM 进行翻译，并将翻译结果推送回 App Store Connect——全程自动化。

命令发现与输出约定

始终使用 --help 确认特定 asc 版本的标志：
- asc localizations --help
- asc localizations download --help
- asc localizations upload --help
- asc apps info edit --help
优先使用明确的长标志（--app、--version、、、）。

广告位招租

在这里展示您的产品或服务

触达数万 AI 开发者，精准高效

联系我们

相关 Skills

find-skills 技能搜索工具 - Vercel Labs 开源智能体技能包管理器

733,500 周安装

Vercel React 最佳实践指南 | 58条Next.js性能优化规则与代码重构

252,100 周安装

Vercel Web界面规范检查工具 - 自动检测代码是否符合Web设计指南

202,600 周安装

agent-browser 浏览器自动化工具 - Vercel Labs 命令行网页操作与测试

133,200 周安装

字段：description、keywords、whatsNew、supportUrl、marketingUrl、promotionalText

字段：name、subtitle、privacyPolicyUrl、privacyChoicesUrl、privacyPolicyText

# 将版本本地化下载到本地 .strings 文件
# (description, keywords, whatsNew, promotionalText, supportUrl, marketingUrl, ...)
asc localizations download --version "VERSION_ID" --path "./localizations"

# 将应用信息本地化下载到本地 .strings 文件
# (name, subtitle, privacyPolicyUrl, privacyChoicesUrl, privacyPolicyText, ...)
asc localizations download --app "APP_ID" --type app-info --app-info "APP_INFO_ID" --path "./app-info-localizations"

语气与语体：始终使用正式、礼貌的语言。在语言区分正式“您”的地方使用正式形式（俄语：«вы»，德语：«Sie»，法语：«vous»，西班牙语：«usted»，荷兰语：«u»，意大利语：«Lei»，葡萄牙语：«você» 正式形式等）。App Store 描述是专业的营销文案——切勿使用随意或非正式的语体。
description：自然翻译，根据本地市场调整语气。保留格式（换行、项目符号、表情符号）。保持在 4000 字符以内。
keywords：不要逐字翻译。研究该语言环境的用户会搜索什么。逗号分隔，总计最多 100 个字符。不要重复，不要包含应用名称（Apple 会自动添加）。
whatsNew：翻译更新说明。保持简洁。最多 4000 字符。
promotionalText：翻译营销口号。最多 170 个字符。这可以在不发布新版本的情况下更新。
subtitle：翻译或调整标语。最多 30 个字符——空间非常紧张，可能需要创造性地调整。
name：通常保留原始应用名称。仅在用户明确要求时翻译。最多 30 个字符。

Translate the following App Store metadata from {source_locale} to {target_locale}.

Rules:
- description: Natural, fluent translation. Preserve formatting (line breaks, bullets, emoji). Max 4000 chars.
- keywords: Do NOT literally translate. Choose keywords native speakers would search for in the App Store. Comma-separated, max 100 chars total. Do not include the app name.
- whatsNew: Translate release notes naturally. Max 4000 chars.
- promotionalText: Translate marketing tagline. Max 170 chars.
- subtitle: Adapt tagline creatively to fit 30 chars max.
- name: Keep the original app name unless explicitly requested to translate it. Max 30 chars.
- Use formal, polite language and formal "you" forms (Russian: вы, German: Sie, French: vous, Spanish: usted, Dutch: u, etc.). App Store copy is professional marketing — never use informal register.
- Respect cultural context. A playful tone in English may need adjustment for formal markets (e.g., ja, de-DE).

Source ({source_locale}):
description: """
{description}
"""

keywords: {keywords}

whatsNew: """
{whatsNew}
"""

promotionalText: {promotionalText}

name: {name}

subtitle: {subtitle}

# 副标题/名称（应用信息本地化）通过应用信息本地化管理。
# 使用应用信息本地化 .strings 文件 + 上传流程（没有 `asc app-infos localizations ...` 命令）。
#
# 1) 编辑：./app-info-localizations/nl-NL.strings
# "subtitle" = "Leer tafels spelenderwijs";
#
# 2) 上传：
asc localizations upload --app "APP_ID" --type app-info --app-info "APP_INFO_ID" --path "./app-info-localizations"

# 1) 确定性解析 ID（不要自动选择“第一”行）
# 如果只有名称，请使用 asc-id-resolver 技能。
asc apps list --output table
APP_ID="APP_ID_HERE"

asc versions list --app "$APP_ID" --state PREPARE_FOR_SUBMISSION --output table
VERSION_ID="VERSION_ID_HERE"

asc apps info list --app "$APP_ID" --output table
APP_INFO_ID="APP_INFO_ID_HERE"

# 2) 下载英文源（或你选择的源语言环境）
asc localizations download --version "$VERSION_ID" --path "./localizations"
asc localizations download --app "$APP_ID" --type app-info --app-info "$APP_INFO_ID" --path "./app-info-localizations"

# 3) 读取 en-US.strings，翻译为 nl-NL 和 ru（LLM 步骤）

# 4) 将 nl-NL.strings 和 ru.strings 写入：
#    - ./localizations/ （版本本地化字段）
#    - ./app-info-localizations/ （副标题/名称/隐私字段）

# 5) 全部上传
asc localizations upload --version "$VERSION_ID" --path "./localizations"
asc localizations upload --app "$APP_ID" --type app-info --app-info "$APP_INFO_ID" --path "./app-info-localizations"

# 6) 验证
asc localizations list --version "$VERSION_ID" --output table
asc localizations list --app "$APP_ID" --type app-info --app-info "$APP_INFO_ID" --output table

始终从读取源语言环境开始——切勿凭记忆或假设翻译。
首先检查现有本地化——除非用户要求更新，否则不要覆盖现有翻译。
版本与应用信息是不同的——版本字段位于 --version "VERSION_ID" 下；副标题/名称/隐私字段位于 --app ... --type app-info 下。
优先使用确定性 ID——除非明确请求，否则不要通过 head -1 选择 ID；使用 --output table 进行选择或使用 asc-id-resolver。
在上传前验证字符限制。计算每个字段的字符数。如果超出限制，重新翻译为更短的版本。
关键词是特殊的——不要逐字翻译。研究适合该语言环境的搜索词。像使用该语言在 App Store 中搜索的用户一样思考。
在上传前向用户展示翻译——提供一个所有字段 × 语言环境的摘要表格以供批准。未经确认不要推送。
如果翻译多种语言，一次处理一个语言环境——更容易审查和发现错误。
如果某个语言环境上传失败，记录错误，继续处理其他语言环境，最后报告所有失败。
对于更新现有本地化——下载当前内容，显示将要更改的差异，获得批准，然后上传。

版本本地化与特定版本绑定。如果版本不存在，请先创建版本。
promotionalText 可以随时更新，无需提交新版本。
whatsNew 仅与更新相关，不适用于第一个版本。
如果只有应用/版本名称而没有 ID，请使用 asc-id-resolver 技能。
对于非翻译元数据操作，请使用 asc-metadata-sync 技能。
对于订阅/IAP 显示名称本地化，请改用 asc-subscription-localization 技能。

🇺🇸English

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, uk, vi, zh-Hans, zh-Hant

Two Types of Metadata

Version Localizations (per-release)

Fields: description, keywords, whatsNew, supportUrl, marketingUrl, promotionalText

App Info Localizations (app-level, persistent)

Fields: name, subtitle, privacyPolicyUrl, privacyChoicesUrl, privacyPolicyText

Workflow

Step 1: Resolve IDs

# 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

Notes:

Version-localization fields (description, keywords, whatsNew, etc.) are per-version.
App-info fields (name, subtitle, privacy URLs/text) are app-level and use --type app-info.
If you only have names (app name, version string) and need IDs deterministically, use asc-id-resolver.

Step 2: Download source locale

# Download version localizations to local .strings files
# (description, keywords, whatsNew, promotionalText, supportUrl, marketingUrl, ...)
asc localizations download --version "VERSION_ID" --path "./localizations"

# Download app-info localizations to local .strings files
# (name, subtitle, privacyPolicyUrl, privacyChoicesUrl, privacyPolicyText, ...)
asc localizations download --app "APP_ID" --type app-info --app-info "APP_INFO_ID" --path "./app-info-localizations"

This creates files like ./localizations/en-US.strings and ./app-info-localizations/en-US.strings. If download is unavailable, read fields individually:

# List version localizations to see existing locales and their content
asc localizations list --version "VERSION_ID" --output table

Step 3: Translate with LLM

For each target locale, translate the source text. Follow these rules:

Translation Guidelines

Tone & Register: Always use formal, polite language. Use formal "you" forms where the language distinguishes them (Russian: «вы», German: «Sie», French: «vous», Spanish: «usted», Dutch: «u», Italian: «Lei», Portuguese: «você» formal, etc.). App Store descriptions are professional marketing copy — never use casual or informal register.
description : Translate naturally, adapt tone to local market. Keep formatting (line breaks, bullet points, emoji). Stay within 4000 chars.
keywords : Do NOT literally translate. Research what users in that locale would search for. Comma-separated, max 100 chars total. No duplicates, no app name (Apple adds it automatically).
whatsNew : Translate release notes. Keep it concise. Max 4000 chars.
promotionalText : Translate marketing hook. Max 170 chars. This can be updated without a new version.
subtitle : Translate or adapt tagline. Max 30 chars — this is very tight, may need creative adaptation.
name : Usually keep the original app name. Only translate if the user explicitly asks. Max 30 chars.

LLM Translation Prompt Template

For each target locale, use this approach:

Translate the following App Store metadata from {source_locale} to {target_locale}.

Rules:
- description: Natural, fluent translation. Preserve formatting (line breaks, bullets, emoji). Max 4000 chars.
- keywords: Do NOT literally translate. Choose keywords native speakers would search for in the App Store. Comma-separated, max 100 chars total. Do not include the app name.
- whatsNew: Translate release notes naturally. Max 4000 chars.
- promotionalText: Translate marketing tagline. Max 170 chars.
- subtitle: Adapt tagline creatively to fit 30 chars max.
- name: Keep the original app name unless explicitly requested to translate it. Max 30 chars.
- Use formal, polite language and formal "you" forms (Russian: вы, German: Sie, French: vous, Spanish: usted, Dutch: u, etc.). App Store copy is professional marketing — never use informal register.
- Respect cultural context. A playful tone in English may need adjustment for formal markets (e.g., ja, de-DE).

Source ({source_locale}):
description: """
{description}
"""

keywords: {keywords}

whatsNew: """
{whatsNew}
"""

promotionalText: {promotionalText}

name: {name}

subtitle: {subtitle}

Step 4: Upload translations

Option A: Via .strings files (bulk)

Create a .strings file per locale in the appropriate directory.

Version localization example:

// nl-NL.strings
"description" = "Je app-beschrijving hier";
"keywords" = "wiskunde,kinderen,tafels,leren";
"whatsNew" = "Bugfixes en verbeteringen";
"promotionalText" = "Leer de tafels van vermenigvuldiging!";

Then upload version localizations:

asc localizations upload --version "VERSION_ID" --path "./localizations"

App-info localization example:

// nl-NL.strings
"subtitle" = "Leer tafels spelenderwijs";

Then upload app-info localizations:

asc localizations upload --app "APP_ID" --type app-info --app-info "APP_INFO_ID" --path "./app-info-localizations"

Option B: Via individual commands (fine control)

# Version localization fields (fine control).
# Prefer passing the explicit version ID for determinism.
asc apps info edit --app "APP_ID" --version-id "VERSION_ID" --locale "nl-NL" \
  --description "Je beschrijving..." \
  --keywords "wiskunde,kinderen,tafels" \
  --whats-new "Bugfixes en verbeteringen"

For app-level fields:

# Subtitle/name (app-info localization) is managed via app-info localizations.
# Use the app-info localization .strings + upload flow (there is no `asc app-infos localizations ...` command).
#
# 1) Edit: ./app-info-localizations/nl-NL.strings
# "subtitle" = "Leer tafels spelenderwijs";
#
# 2) Upload:
asc localizations upload --app "APP_ID" --type app-info --app-info "APP_INFO_ID" --path "./app-info-localizations"

Step 5: Verify

# Check all locales are present
asc localizations list --version "VERSION_ID" --output table

# Check app info localizations
asc localizations list --app "APP_ID" --type app-info --app-info "APP_INFO_ID" --output table

Character Limits (enforce before upload!)

Field	Limit
Name	30
Subtitle	30
Keywords	100 (comma-separated)
Description	4000
What's New	4000
Promotional Text	170

Always validate translated text fits within limits before uploading. Truncated text looks unprofessional. If translation exceeds the limit, shorten it — do not truncate mid-sentence.

Full Example: Add nl-NL and ru to Roxy Math

# 1) Resolve IDs deterministically (do not auto-pick the "first" row)
# If you only have names, use asc-id-resolver skill.
asc apps list --output table
APP_ID="APP_ID_HERE"

asc versions list --app "$APP_ID" --state PREPARE_FOR_SUBMISSION --output table
VERSION_ID="VERSION_ID_HERE"

asc apps info list --app "$APP_ID" --output table
APP_INFO_ID="APP_INFO_ID_HERE"

# 2) Download English source (or your chosen source locale)
asc localizations download --version "$VERSION_ID" --path "./localizations"
asc localizations download --app "$APP_ID" --type app-info --app-info "$APP_INFO_ID" --path "./app-info-localizations"

# 3) Read en-US.strings, translate to nl-NL and ru (LLM step)

# 4) Write nl-NL.strings and ru.strings to:
#    - ./localizations/ (version localization fields)
#    - ./app-info-localizations/ (subtitle/name/privacy fields)

# 5) Upload all
asc localizations upload --version "$VERSION_ID" --path "./localizations"
asc localizations upload --app "$APP_ID" --type app-info --app-info "$APP_INFO_ID" --path "./app-info-localizations"

# 6) Verify
asc localizations list --version "$VERSION_ID" --output table
asc localizations list --app "$APP_ID" --type app-info --app-info "$APP_INFO_ID" --output table

Agent Behavior

Always start by reading the source locale — never translate from memory or assumptions.
Check existing localizations first — don't overwrite existing translations unless the user asks to update them.
Version vs app-info is different — version fields live under --version "VERSION_ID"; subtitle/name/privacy live under --app ... --type app-info.
Prefer deterministic IDs — do not select IDs via head -1 unless explicitly requested; use --output table for selection or asc-id-resolver.
Validate character limits before uploading. Count characters for each field. If over limit, re-translate shorter.
Keywords are special — do not literally translate. Research locale-appropriate search terms. Think like a user searching the App Store in that language.
Show the user translations before uploading — present a summary table of all fields × locales for approval. Do not push without confirmation.
Process one locale at a time if translating many languages — easier to review and catch errors.

Notes

Version localizations are tied to a specific version. Create the version first if it doesn't exist.
promotionalText can be updated anytime without a new version submission.
whatsNew is only relevant for updates, not the first version.
Use asc-id-resolver skill if you only have app/version names instead of IDs.
Use asc-metadata-sync skill for non-translation metadata operations.
For subscription/IAP display name localization, use asc-subscription-localization skill instead.

Weekly Installs

931

Repository

rudrankriyam/ap…i-skills

GitHub Stars

598

First Seen

Feb 19, 2026

Security Audits

Gen Agent Trust HubPass SocketPass SnykPass

Installed on

codex913

opencode906

gemini-cli905

github-copilot897

kimi-cli891

amp891

App Store Connect 元数据自动化本地化工具 - asc-localize-metadata 使用指南

🇨🇳中文介绍

asc localize metadata

命令发现与输出约定

相关 Skills

前提条件

支持的语言环境

两种类型的元数据

版本本地化（按版本）

应用信息本地化（应用级别，持久性）

工作流程

步骤 1：解析 ID

步骤 2：下载源语言环境

步骤 3：使用 LLM 翻译

翻译指南

LLM 翻译提示模板

步骤 4：上传翻译

选项 A：通过 .strings 文件（批量）

选项 B：通过单独的命令（精细控制）

步骤 5：验证

字符限制（上传前强制执行！）

完整示例：为 Roxy Math 添加 nl-NL 和 ru

代理行为

注意事项

🇺🇸English

asc localize metadata

Command discovery and output conventions

Preconditions

Supported Locales

Two Types of Metadata

Version Localizations (per-release)

App Info Localizations (app-level, persistent)

Workflow

Step 1: Resolve IDs

Step 2: Download source locale

Step 3: Translate with LLM

Translation Guidelines

LLM Translation Prompt Template

Step 4: Upload translations

Option A: Via .strings files (bulk)

Option B: Via individual commands (fine control)

Step 5: Verify

Character Limits (enforce before upload!)

Full Example: Add nl-NL and ru to Roxy Math

Agent Behavior

Notes

最新 Skills