agentleFS
moasqmoasq/ios-dev-agent/.agents/skills/asc-subscription-localization/SKILL.md

asc-subscription-localization

Skill4 starsChanged 6 months agoMITView on GitHub

Use when localizing subscription or in-app purchase display names and descriptions across App Store locales in bulk with asc.

6 other projects use a version of this, 6 of them edited.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

11 rules. 4 are common, 3 are distinctive, and 4 are very specific to this project.

  • 4

    Common

    Most of the 6 edited versions we read keep these.

  • 3

    Distinctive

    This author's own choices. Worth a look.

  • 4

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use this skill to bulk-create or bulk-update display names (and descriptions) for subscriptions, subscription groups, and in-app purchases …

    line 8
  2. Common:

    Always list existing localizations first to avoid duplicate creation errors.

    line 224
  3. Common:

    When the user provides a single display name, use it for all locales (same name everywhere).

    line 226
  4. Common:

    When the user provides translated names per locale, use the locale-specific name for each.

    line 227
  5. Very specific:

    If a description is provided, pass --description on create.

    line 228
  6. Very specific:

    Use --output table for verification steps so the user can visually confirm.

    line 229
  7. Distinctive:

    Use default JSON output for intermediate automation steps.

    line 230
  8. Common:

    After bulk creation, always run the list command to verify completeness.

    line 231
  9. Distinctive:

    If a create call fails for a locale, log the locale and error, then continue with the remaining locales.

    line 233
  10. Very specific:

    Use --paginate on list commands to ensure all existing localizations are returned.

    line 239
  11. Very specific:

    Use the asc-id-resolver skill if you only have app names instead of IDs.

    line 240

“Common” is measured: kept by at least 6 in 10 of the 6 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

asc subscription localization

Use this skill to bulk-create or bulk-update display names (and descriptions) for subscriptions, subscription groups, and in-app purchases across all App Store Connect locales. This eliminates the tedious manual process of clicking through each language in App Store Connect to set the same display name.

Preconditions

  • Auth configured (asc auth login or ASC_* env vars).
  • Know your app ID (ASC_APP_ID or --app).
  • Subscription groups and subscriptions already exist.

Supported App Store Locales

These are the locales supported by App Store Connect for subscription and IAP 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

Workflow: Bulk-Localize a Subscription

1. Resolve IDs

# Find subscription groups
asc subscriptions groups list --app "APP_ID" --output table

# Find subscriptions within a group
asc subscriptions list --group-id "GROUP_ID" --output table

2. Check existing localizations

asc subscriptions localizations list --subscription-id "SUB_ID" --paginate --output table

This shows which locales already have a name set. Only create localizations for missing locales.

3. Create localizations for all missing locales

For each locale that does not already have a localization, run:

asc subscriptions localizations create \
  --subscription-id "SUB_ID" \
  --locale "LOCALE" \
  --name "Display Name"

For example, to set "Monthly Pro" across all locales:

# One command per locale (skip any that already exist)
asc subscriptions localizations create --subscription-id "SUB_ID" --locale "ar-SA" --name "Monthly Pro"
asc subscriptions localizations create --subscription-id "SUB_ID" --locale "ca" --name "Monthly Pro"
asc subscriptions localizations create --subscription-id "SUB_ID" --locale "cs" --name "Monthly Pro"
asc subscriptions localizations create --subscription-id "SUB_ID" --locale "da" --name "Monthly Pro"
asc subscriptions localizations create --subscription-id "SUB_ID" --locale "de-DE" --name "Monthly Pro"
asc subscriptions localizations create --subscription-id "SUB_ID" --locale "el" --name "Monthly Pro"
asc subscriptions localizations create --subscription-id "SUB_ID" --locale "en-AU" --name "Monthly Pro"
asc subscriptions localizations create --subscription-id "SUB_ID" --locale "en-CA" --name "Monthly Pro"
asc subscriptions localizations create --subscription-id "SUB_ID" --locale "en-GB" --name "Monthly Pro"
asc subscriptions localizations create --subscription-id "SUB_ID" --locale "es-ES" --name "Monthly Pro"
asc subscriptions localizations create --subscription-id "SUB_ID" --locale "es-MX" --name "Monthly Pro"
asc subscriptions localizations create --subscription-id "SUB_ID" --locale "fi" --name "Monthly Pro"
asc subscriptions localizations create --subscription-id "SUB_ID" --locale "fr-CA" --name "Monthly Pro"
asc subscriptions localizations create --subscription-id "SUB_ID" --locale "fr-FR" --name "Monthly Pro"
asc subscriptions localizations create --subscription-id "SUB_ID" --locale "he" --name "Monthly Pro"
asc subscriptions localizations create --subscription-id "SUB_ID" --locale "hi" --name "Monthly Pro"
asc subscriptions localizations create --subscription-id "SUB_ID" --locale "hr" --name "Monthly Pro"
asc subscriptions localizations create --subscription-id "SUB_ID" --locale "hu" --name "Monthly Pro"
asc subscriptions localizations create --subscription-id "SUB_ID" --locale "id" --name "Monthly Pro"
asc subscriptions localizations create --subscription-id "SUB_ID" --locale "it" --name "Monthly Pro"
asc subscriptions localizations create --subscription-id "SUB_ID" --locale "ja" --name "Monthly Pro"
asc subscriptions localizations create --subscription-id "SUB_ID" --locale "ko" --name "Monthly Pro"
asc subscriptions localizations create --subscription-id "SUB_ID" --locale "ms" --name "Monthly Pro"
asc subscriptions localizations create --subscription-id "SUB_ID" --locale "nl-NL" --name "Monthly Pro"
asc subscriptions localizations create --subscription-id "SUB_ID" --locale "no" --name "Monthly Pro"
asc subscriptions localizations create --subscription-id "SUB_ID" --locale "pl" --name "Monthly Pro"
asc subscriptions localizations create --subscription-id "SUB_ID" --locale "pt-BR" --name "Monthly Pro"
asc subscriptions localizations create --subscription-id "SUB_ID" --locale "pt-PT" --name "Monthly Pro"
asc subscriptions localizations create --subscription-id "SUB_ID" --locale "ro" --name "Monthly Pro"
asc subscriptions localizations create --subscription-id "SUB_ID" --locale "ru" --name "Monthly Pro"
asc subscriptions localizations create --subscription-id "SUB_ID" --locale "sk" --name "Monthly Pro"
asc subscriptions localizations create --subscription-id "SUB_ID" --locale "sv" --name "Monthly Pro"
asc subscriptions localizations create --subscription-id "SUB_ID" --locale "th" --name "Monthly Pro"
asc subscriptions localizations create --subscription-id "SUB_ID" --locale "tr" --name "Monthly Pro"
asc subscriptions localizations create --subscription-id "SUB_ID" --locale "uk" --name "Monthly Pro"
asc subscriptions localizations create --subscription-id "SUB_ID" --locale "vi" --name "Monthly Pro"
asc subscriptions localizations create --subscription-id "SUB_ID" --locale "zh-Hans" --name "Monthly Pro"
asc subscriptions localizations create --subscription-id "SUB_ID" --locale "zh-Hant" --name "Monthly Pro"

4. Verify

asc subscriptions localizations list --subscription-id "SUB_ID" --paginate --output table

Workflow: Bulk-Localize a Subscription Group

Subscription groups also have their own display name per locale (this is the "group name" shown to users in the subscription management sheet).

1. Check existing group localizations

asc subscriptions groups localizations list --group-id "GROUP_ID" --paginate --output table

2. Create for missing locales

asc subscriptions groups localizations create \
  --group-id "GROUP_ID" \
  --locale "LOCALE" \
  --name "Group Display Name"

Optional: set a custom app name for the group:

asc subscriptions groups localizations create \
  --group-id "GROUP_ID" \
  --locale "LOCALE" \
  --name "Group Display Name" \
  --custom-app-name "My App"

3. Verify

asc subscriptions groups localizations list --group-id "GROUP_ID" --paginate --output table

Workflow: Bulk-Localize an In-App Purchase

IAPs have their own localization commands with the same pattern.

1. Resolve IAP ID

asc iap list --app "APP_ID" --output table

2. Check existing localizations

asc iap localizations list --iap-id "IAP_ID" --paginate --output table

3. Create for missing locales

asc iap localizations create \
  --iap-id "IAP_ID" \
  --locale "LOCALE" \
  --name "Display Name"

Optional description:

asc iap localizations create \
  --iap-id "IAP_ID" \
  --locale "LOCALE" \
  --name "Unlock All Features" \
  --description "One-time purchase to unlock all premium features"

4. Verify

asc iap localizations list --iap-id "IAP_ID" --paginate --output table

Updating Existing Localizations

To change the display name for existing localizations:

Subscriptions

asc subscriptions localizations update --id "LOC_ID" --name "New Name"

Subscription Groups

asc subscriptions groups localizations update --id "LOC_ID" --name "New Group Name"

In-App Purchases

asc iap localizations update --localization-id "LOC_ID" --name "New Name"

To bulk-update, list existing localizations first, extract the IDs, then update each one.

Bulk-Localize All Subscriptions in an App

For a full app with multiple subscription groups and subscriptions:

# 1. List all groups
asc subscriptions groups list --app "APP_ID" --paginate

# 2. For each group, localize the group itself
#    (repeat group localization workflow above)

# 3. For each group, list subscriptions
asc subscriptions list --group-id "GROUP_ID" --paginate

# 4. For each subscription, localize it
#    (repeat subscription localization workflow above)

Agent Behavior

  • Always list existing localizations first to avoid duplicate creation errors.
  • Skip locales that already have a localization; only create missing ones.
  • When the user provides a single display name, use it for all locales (same name everywhere).
  • When the user provides translated names per locale, use the locale-specific name for each.
  • If a description is provided, pass --description on create. Otherwise omit it.
  • Use --output table for verification steps so the user can visually confirm.
  • Use default JSON output for intermediate automation steps.
  • After bulk creation, always run the list command to verify completeness.
  • For apps with many subscriptions, process them sequentially per group to keep output readable.
  • If a create call fails for a locale, log the locale and error, then continue with the remaining locales. After the batch completes, report all failures together so the user can address them.

Notes

  • Subscription display names are what users see on the subscription management sheet and in purchase dialogs.
  • Creating a localization for a locale that already exists will fail; always check first.
  • There is no bulk API; each locale requires a separate create call.
  • Use --paginate on list commands to ensure all existing localizations are returned.
  • Use the asc-id-resolver skill if you only have app names instead of IDs.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.