asc-subscription-localization

Generate per-locale App Store Connect commands for subscription and IAP display names.

Updated Apr 4, 2026
One-click install
npx skills add https://github.com/curtislmartin/daily-ascent-engineering --skill asc-subscription-localization-curtislmartin
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: asc-subscription-localization
Source: https://github.com/curtislmartin/daily-ascent-engineering/tree/main/skills_repo/asc-subscription-localization
Command: npx skills add https://github.com/curtislmartin/daily-ascent-engineering --skill asc-subscription-localization-curtislmartin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manual entry of display names for each locale in App Store Connect is time‑consuming and error‑prone.

Core Features & Use Cases

  • Bulk creation of subscription, group, and IAP localizations for every supported App Store locale.
  • Verification steps that list existing localizations to avoid duplicate errors.
  • Update workflow to modify names or descriptions across locales.
  • Use case: A developer releasing a new subscription tier can instantly set its name in all languages with a single command.

Quick Start

Ask the skill to set the subscription name “Monthly Pro” for all App Store locales.

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 subscription display names across all App Store locales?

You can set subscription names for every supported locale with a single command by providing your App Store Connect authentication and subscription, group, or IAP IDs to generate the necessary per-locale creation commands automatically.

Can I update existing in-app purchase localizations without creating duplicates?

Updating in-app purchase localizations safely requires verification steps to list existing localizations first, preventing duplicate errors. This skill includes checks to list existing entries before generating update commands for modified names or descriptions.

What do I need to generate App Store localization commands for my IAPs?

To generate App Store localization commands for your IAPs, you need App Store Connect authentication and the specific subscription, group, or in-app purchase IDs you intend to localize. These are the only required inputs to begin the process.

Why does manual localization of subscription tiers in App Store Connect take so long?

Manual localization of subscription tiers is time-consuming because developers must individually edit each locale in App Store Connect. This skill solves the problem by bulk-creating localizations across all supported languages instantly using a single command.

Does this bulk localization approach work for both subscriptions and in-app purchases?

Yes, this bulk localization approach works for both subscriptions and in-app purchases. It supports bulk creation and updating of display names and descriptions for individual IAPs, subscription groups, and specific subscription tiers across all locales.