asc-subscription-localization
Skill7 starsChanged 16 days agoMITView on GitHub
Use when filling or updating subscription/IAP names and descriptions without App Store Connect UI work. Bulk-localize subscription, subscription-group, and in-app purchase display names across App Store locales using asc, including API 4.4.1 version-scoped v2 resources.
6 other projects use a version of this, 5 of them edited.
Adopted by
Most recently taken up by
- VelimirMueller/ai-development-skillsword for word, first seen Nov 1, 2026
- The-Artificer-of-Ciphers-LLC/skills-from-the-artificeredited, first seen Nov 1, 2026
- rorkai/app-store-connect-cli-skillsedited, first seen Oct 26, 2026
- malpern/VoxClawedited, first seen Oct 8, 2026
- rudrankriyam/app-store-connect-cli-skillsedited, first seen Oct 8, 2026
- moasq/ios-dev-agentedited, first seen May 26, 2026
Other versions6 projects use a version of this.
Word for word · 1
- VelimirMueller/ai-development-skills★ 7100% same
Edited · 5
- rorkai/app-store-connect-cli-skills★ 1.1k97% same
- rudrankriyam/app-store-connect-cli-skills★ 1.1k97% same
- malpern/VoxClaw★ 20832% same
- The-Artificer-of-Ciphers-LLC/skills-from-the-artificer★ 637% same
- moasq/ios-dev-agent★ 433% same
Wrote their own version · 0
None found.
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository156 other files it gives its agents.
- skills/swift/swiftui-design-principles/AGENTS.mdAGENTS.md
- skills/swift/ios-code-audit/CLAUDE.mdCLAUDE.md
- skills/swift/swift-focusengine-pro/llms.txtllms.txt
- build-llm-seamSkill
- build-mcp-serverSkill
- build-rag-pipelineSkill
- secure-llm-featuresSkill
- set-up-llm-evalsSkill
- build-nextjs-backendSkill
- build-supabase-edge-functionSkill
- configure-backend-testsSkill
- design-http-apiSkill
- harden-backendSkill
- scaffold-fastapi-serviceSkill
- scaffold-go-serviceSkill
- scaffold-hono-serviceSkill
- secure-supabase-rlsSkill
- set-up-backend-authSkill
- set-up-background-jobsSkill
- set-up-databaseSkill
- set-up-nextjs-supabase-authSkill
- set-up-observabilitySkill
- set-up-supabaseSkill
- build-cliSkill
- release-cliSkill
- set-up-dev-toolchainSkill
- audit-securitySkill
- audit-toolchainSkill
- extend-skillsetSkill
- promote-releaseSkill
- set-up-stack-profileSkill
- write-commit-messagesSkill
- write-pull-requestsSkill
- analyze-complexitySkill
- apply-algorithmsSkill
- apply-design-patternsSkill
- apply-design-principlesSkill
- apply-solidSkill
- choose-data-structureSkill
- debug-systematicallySkill
- enforce-dependency-ruleSkill
- refactor-safelySkill
- slice-and-estimateSkill
- write-clean-testsSkill
- write-readable-codeSkill
- clean-frontend-scaffoldingSkill
- configure-accessibilitySkill
- configure-analyticsSkill
- configure-ciSkill
- configure-error-trackingSkill
- configure-lintingSkill
- configure-test-stackSkill
- configure-typescriptSkill
- create-moduleSkill
- optimize-performanceSkill
- scaffold-frontend-projectSkill
- set-up-authSkill
- set-up-design-systemSkill
- set-up-document-headSkill
- set-up-error-boundariesSkill
- The first 60 shown.
The file
Show its rules and text
We split this skill into the rules it gives an agent
19 rules. 4 are common, 7 are distinctive, and 8 are very specific to this project.
4
Common
Most of the 5 edited versions we read keep these.
7
Distinctive
This author's own choices. Worth a look.
8
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 8
Use this skill to bulk-create or bulk-update display names and, where supported, descriptions for subscriptions, subscription groups, and …
- Very specific: line 24
Use asc ... versions localizations ...
- Distinctive: line 25
Do not use the product- or group-scoped v1 localization commands.
- Distinctive: line 28
Never pass a product, subscription, or group ID to a version-scoped command.
- Very specific: line 100
Do not combine a value flag with its matching --clear-name or --clear-description flag.
- Very specific: line 127
Do not include --clear-name or --clear-custom-app-name in the standard bulk localization workflow.
- Distinctive: line 174
Use only version-scoped v2 resources for new localization work.
- Distinctive: line 175
Keep version IDs separate from product, subscription, and group IDs.
- Common: line 176
Always list existing localizations first to avoid duplicate creation errors.
- Distinctive: line 177
Create a missing locale, update the resolved localization ID when existing values differ, and do nothing when the existing values already …
- Common: line 179
When the user provides a single display name, use it for all locales (same name everywhere).
- Common: line 180
When the user provides translated names per locale, use the locale-specific name for each.
- Very specific: line 190
Create or update their names normally, with --custom-app-name only when the user supplied that value.
- Very specific: line 192
Use --output table for verification steps so the user can visually confirm.
- Very specific: line 193
Use explicit --output json for intermediate automation steps.
- Common: line 195
After bulk writes, always run the list command to verify completeness.
- Distinctive: line 197
If a create or update call fails for a locale, log the locale and error, then continue with the remaining locales.
- Very specific: line 206
Use --paginate on list commands to ensure all existing localizations are returned.
- Very specific: line 207
Use the asc-id-resolver skill if you only have app names instead of IDs.
“Common” is measured: kept by at least 6 in 10 of the 5 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.
Files
asc subscription localization
Use this skill to bulk-create or bulk-update display names and, where supported, 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 loginorASC_*env vars). - Know your app ID (
ASC_APP_IDor--app). - Subscription groups and subscriptions already exist.
Choose the API scope first
API 4.4.1 adds discrete versions for IAPs, subscriptions, and subscription groups. A version ID is different from its product, subscription, or group ID.
- Use
asc ... versions localizations ...for all new localization work. - Do not use the product- or group-scoped v1 localization commands. API 4.4.1 deprecates those resources, and the CLI now emits migration warnings for their compatibility commands.
- Never pass a product, subscription, or group ID to a version-scoped command.
Resolve or create versions before localizing them:
asc iap versions list --iap-id "IAP_ID" --state PREPARE_FOR_SUBMISSION --paginate --output table
asc subscriptions versions list --subscription-id "SUB_ID" --state PREPARE_FOR_SUBMISSION --paginate --output table
asc subscriptions groups versions list --group-id "GROUP_ID" --state PREPARE_FOR_SUBMISSION --paginate --output tableBranch independently on each list result: zero matches means create, one means reuse that version ID, and more than one means stop and require an explicit version ID. Run each command below only for its zero-match branch:
# If and only if the IAP version list returned zero matches:
asc iap versions create --iap-id "IAP_ID" --output json
# If and only if the subscription version list returned zero matches:
asc subscriptions versions create --subscription-id "SUB_ID" --output json
# If and only if the group version list returned zero matches:
asc subscriptions groups versions create --group-id "GROUP_ID" --output jsonNone of the three version families has a version delete command. List and
reuse the single PREPARE_FOR_SUBMISSION version; create only for zero matches,
and stop for an explicit ID when multiple matches exist. Live parent deletion
did not cascade IAP or subscription versions, so do not assume parent deletion
cleans up versions created for testing.
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-HantImport many locales from one file
For bulk writes, map each locale to its fields in one JSON file and import it into the resolved version ID. Import creates missing locales, updates only differing fields, never clears or deletes, and reports per-locale failures.
asc subscriptions versions localizations import --version-id "VERSION_ID" --file "./localizations.json" --dry-run
asc subscriptions versions localizations import --version-id "VERSION_ID" --file "./localizations.json" --confirmasc iap versions localizations import takes the same name and
description fields. asc subscriptions groups versions localizations import
takes name and customAppName. Give every new subscription or IAP locale a
non-empty description; see the create rules below.
Workflow: Bulk-localize a subscription version (v2)
List existing localizations, create only missing locales, then verify:
asc subscriptions versions localizations list --version-id "VERSION_ID" --paginate --output table
asc subscriptions versions localizations create --version-id "VERSION_ID" --locale "LOCALE" --name "Display Name" --description "Description"
asc subscriptions versions localizations list --version-id "VERSION_ID" --paginate --output tableUpdates distinguish omitted values, non-empty strings, and JSON null:
asc subscriptions versions localizations update --id "LOC_ID" --name "New Name" --description "Updated description"Do not combine a value flag with its matching --clear-name or
--clear-description flag. The 4.4.1 schema permits JSON null, but Apple's
live service currently rejects both an empty --description and
--clear-description for subscription-version localizations because the
description must contain at least one character.
Creating a missing subscription-version localization therefore requires a non-empty description. A display-name-only run may update the name of an existing localization, but must not create a missing locale until the user provides a non-empty locale-specific or shared fallback description.
Workflow: Bulk-localize a subscription group version (v2)
asc subscriptions groups versions localizations list --version-id "VERSION_ID" --paginate --output table
asc subscriptions groups versions localizations create --version-id "VERSION_ID" --locale "LOCALE" --name "Group Display Name" --custom-app-name "My App"
asc subscriptions groups versions localizations update --id "LOC_ID" --name "Updated Group Display Name" --custom-app-name "My App"
asc subscriptions groups versions localizations list --version-id "VERSION_ID" --paginate --output tableClearing metadata is a separate, explicit opt-in operation. After confirming that the user wants to remove an existing custom app name, run:
asc subscriptions groups versions localizations update --id "LOC_ID" --clear-custom-app-nameDo not include --clear-name or --clear-custom-app-name in the standard bulk
localization workflow. Use either flag only when JSON null is deliberately
intended; omitting the flag leaves that attribute unchanged.
Workflow: Bulk-localize an IAP version (v2)
asc iap versions localizations list --version-id "VERSION_ID" --paginate --output table
asc iap versions localizations create --version-id "VERSION_ID" --locale "LOCALE" --name "Display Name" --description "Description"
asc iap versions localizations update --localization-id "LOC_ID" --description "Updated description"
asc iap versions localizations list --version-id "VERSION_ID" --paginate --output tableApple's live service also rejects empty descriptions and
--clear-description for IAP-version localizations even though the 4.4.1
schema permits JSON null. As with subscriptions, a display-name-only run may
update existing IAP localizations but must not create missing locales until a
non-empty description is available.
Bulk-localize all subscription versions in an app
For a full app with multiple subscription groups and subscriptions:
# 1. List groups and resolve each group's unique mutable version.
asc subscriptions groups list --app "APP_ID" --paginate --output json
asc subscriptions groups versions list --group-id "GROUP_ID" --state PREPARE_FOR_SUBMISSION --paginate --output json
# 2. Localize each group version.
asc subscriptions groups versions localizations list --version-id "GROUP_VERSION_ID" --paginate --output json
asc subscriptions groups versions localizations create --version-id "GROUP_VERSION_ID" --locale "LOCALE" --name "Group Display Name"
# 3. List subscriptions and resolve each subscription's unique mutable version.
asc subscriptions list --group-id "GROUP_ID" --paginate --output json
asc subscriptions versions list --subscription-id "SUB_ID" --state PREPARE_FOR_SUBMISSION --paginate --output json
# 4. Localize each subscription version.
asc subscriptions versions localizations list --version-id "SUBSCRIPTION_VERSION_ID" --paginate --output json
asc subscriptions versions localizations create --version-id "SUBSCRIPTION_VERSION_ID" --locale "LOCALE" --name "Display Name" --description "Description"Apply the same zero/one/many rule to each version list: create a version for zero matches, reuse the one match, and stop for an explicit ID when multiple matches are returned.
Agent Behavior
- Use only version-scoped v2 resources for new localization work.
- Keep version IDs separate from product, subscription, and group IDs.
- Always list existing localizations first to avoid duplicate creation errors.
- Create a missing locale, update the resolved localization ID when existing values differ, and do nothing when the existing values already match.
- 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.
- For subscription- and IAP-version localizations, require a non-empty
--descriptionon every create. If the user supplies only display names, update existing localizations by resolved ID, skip creates for missing locales, and ask for locale-specific descriptions or one non-empty fallback description before creating them. - On updates to existing subscription- or IAP-version localizations, omit
--descriptionunless the user supplied a new non-empty value; never infer an empty value or clear it. - Subscription-group-version localizations do not have a description field.
Create or update their names normally, with
--custom-app-nameonly when the user supplied that value. - Use
--output tablefor verification steps so the user can visually confirm. - Use explicit
--output jsonfor intermediate automation steps; output defaults are TTY-aware. - After bulk writes, 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 or update 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; list first and update the resolved ID when a change is needed.
- Apple has no bulk localization endpoint;
... localizations importvalidates the whole file, then writes one locale at a time. - Use
--paginateon list commands to ensure all existing localizations are returned. - Use the
asc-id-resolverskill if you only have app names instead of IDs.
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
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.

