asc-subscription-localization

Bulk-localize subscription and in-app purchase display names across App Store locales using asc.

1|Updated Aug 16, 2025
One-click install
npx skills add https://github.com/barronlroth/Cubby --skill asc-subscription-localization-barronlroth
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: asc-subscription-localization
Source: https://github.com/barronlroth/Cubby/tree/main/.agents/skills/asc-subscription-localization
Command: npx skills add https://github.com/barronlroth/Cubby --skill asc-subscription-localization-barronlroth

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Bulk-localize subscription and in-app purchase display names across all App Store locales using asc. Use when you want to fill in subscription/IAP names for every language without clicking through App Store Connect manually.

Core Features & Use Cases

  • Bulk-localizes subscription display names across all locales for subscriptions, subscription groups, and IAPs.
  • Checks existing localizations, creates missing localizations for all locales, and verifies results across locales.
  • Requires authentication with asc and an app ID; coordinates resolution of IDs and per-locale updates in a safe, auditable workflow.

Quick Start

Authenticate with asc, identify the app, and run the localization workflow to apply a single name across all 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 in-app purchase display names across all App Store locales?

You can bulk-localize in-app purchase display names across all App Store locales by running an asc workflow that applies a single name across every language for subscriptions, subscription groups, and IAPs without manual clicking.

Do I need an existing app ID and asc authentication to localize subscription names?

Yes, you need asc authentication and an existing app ID to localize subscription names. The workflow requires existing resources within a single app to resolve IDs and perform per-locale updates safely.

Can I fill in missing localizations for all App Store locales automatically?

Yes, you can fill in missing localizations automatically. The workflow checks existing localizations, creates missing localizations for all locales, and verifies results across locales with validation and failure reporting.

What is the best way to apply a single subscription display name across every App Store language?

The best way to apply a single subscription display name across every App Store language is using an automated asc workflow that coordinates per-locale create and update calls with validation and failure reporting.

Why does my automated App Store Connect localization workflow fail for some locales?

Automated App Store Connect localization workflows can fail for some locales due to validation errors. The workflow reports failures per-locale during create and update calls, allowing you to audit and resolve issues safely.