asc-subscription-localization

Automate bulk localization of subscription and in-app purchase names across App Store Connect locales.

954|51|Updated Jan 27, 2026
One-click install
npx skills add https://github.com/rudrankriyam/app-store-connect-cli-skills --skill asc-subscription-localization-rudrankriyam
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: asc-subscription-localization
Source: https://github.com/rudrankriyam/app-store-connect-cli-skills/tree/main/skills/asc-subscription-localization
Command: npx skills add https://github.com/rudrankriyam/app-store-connect-cli-skills --skill asc-subscription-localization-rudrankriyam

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill automates the tedious process of manually localizing subscription and in-app purchase display names across all App Store Connect locales, saving significant time and effort.

Core Features & Use Cases

  • Bulk Localization: Create or update display names and descriptions for subscriptions, subscription groups, and in-app purchases across all supported App Store locales.
  • Efficiency: Eliminates the need to navigate App Store Connect manually for each language.
  • Use Case: You've just launched a new subscription tier and need to set its display name ("Pro Plan") in 30 different languages. This Skill handles that in one go.

Quick Start

Use the asc-subscription-localization skill to create missing localizations for subscription ID '12345' with the name 'Premium Access'.

Frequently Asked Questions about asc-subscription-localization

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

FAQPage Schema
How do I bulk localize in-app purchase display names across all App Store Connect locales?

Bulk localizing in-app purchase display names involves automating the creation and updating of metadata across all supported App Store Connect locales. This requires authentication with App Store Connect CLI and the specific subscription or in-app purchase IDs.

What is the best way to localize subscription group metadata for multiple languages at once?

Localizing subscription group metadata for multiple languages at once is best handled by bulk automation scripts that create or update display names and descriptions across all App Store locales. This eliminates navigating App Store Connect manually for each language.

Do I need the App Store Connect CLI to automate subscription localizations?

Yes, you need the App Store Connect CLI to automate subscription localizations. Authentication with the App Store Connect CLI is required to interact with App Store Connect services and update display names and descriptions for your in-app purchases.

Can I update existing subscription localizations or only create new ones?

You can both create missing localizations and update existing ones for subscriptions, subscription groups, and individual in-app purchases. The automation handles setting the display name and description across all specified App Store locales.

What information do I need to provide to automate IAP localization?

To automate IAP localization, you need the relevant subscription or in-app purchase IDs, the display name, and the description text. You also need App Store Connect CLI authentication to execute the bulk updates across all locales.

Why should I use automation for App Store Connect subscription localization instead of the web interface?

Using automation for App Store Connect subscription localization saves significant time and effort by eliminating the need to navigate the web interface manually for each language. It handles setting display names across 30 different languages in one go.