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.

rudrankriyam/asc-skillsUpdated Apr 8, 2026

Works with

Claude CodeCursorClineWindsurfCodexGooseGitHub CopilotZed

0

total installs

0

this week

710

GitHub stars

0

upvotes

Install Skill

Run in your terminal

$npx skills add https://github.com/rudrankriyam/asc-skills --skill asc-subscription-localization

0

installs

0

this week

710

stars

Installation Guide

How to use asc-subscription-localization on Cursor

AI-first code editor with Composer

1

Prerequisites

Before installing skills in Cursor, ensure your development environment meets these requirements:

  • Cursor installed and configured on your machine
  • Node.js 16+ with npm — verify with node --version
  • Active project directory where you want to add asc-subscription-localization
2

Run the install command

Execute the skills CLI command in your project's root directory to begin installation:

$npx skills add https://github.com/rudrankriyam/asc-skills --skill asc-subscription-localization

Fetches asc-subscription-localization from rudrankriyam/asc-skills and configures it for Cursor.

3

Select Cursor when prompted

The CLI shows a list of agents. Use arrow keys and space to select Cursor:

◆ Which agents do you want to install to?
│ ── Universal (.agents/skills) ────────────────
│ · Cline · Codex · Goose · Windsurf
│ ●Cursor(selected)
│ · Cursor · Aider · Continue
4

Verify installation

Confirm successful installation by checking the skill directory location:

.cursor/skills/asc-subscription-localization

Restart Cursor to activate asc-subscription-localization. Access via /asc-subscription-localization in your agent's command palette.

Security Notice

We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.

Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.

Documentation

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

List & Monetize Your Skill

Submit your Claude Code skill and start earning

Get started →

Use Cases

User Story & Requirements Generation

Create detailed user stories, acceptance criteria, and feature specs

Example

Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios

Reduce spec writing time by 50%, ensure comprehensive coverage

Competitive Analysis

Research competitors, compare features, identify gaps

Example

Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities

Complete competitive research in 2 hours instead of 2 days

Roadmap Prioritization

Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs

Example

Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale

Make data-driven prioritization decisions faster

Stakeholder Communication

Draft PRDs, status updates, and stakeholder presentations

Example

Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement

Save 3-5 hours/week on communication overhead

Implementation Guide

Prerequisites

  • Claude Desktop or compatible AI client
  • Access to product documentation and roadmap tools (Jira, Notion, etc.)
  • Understanding of product management frameworks (RICE, Jobs-to-be-Done, etc.)
  • Stakeholder contact information and communication channels

Time Estimate

30-60 minutes to see productivity improvements

Steps

  1. 1Install product management skill
  2. 2Start with user story generation for known feature
  3. 3Progress to competitive analysis: research 2-3 competitors
  4. 4Use for roadmap prioritization: apply RICE/ICE scoring
  5. 5Draft stakeholder communications and refine based on feedback
  6. 6Build template library for recurring PM tasks
  7. 7Share effective prompts with product team

Common Pitfalls

  • Not validating competitive research—verify facts before sharing
  • Accepting user stories without involving engineering team
  • Over-relying on frameworks without qualitative judgment
  • Not customizing outputs to company culture and communication style
  • Skipping stakeholder validation of generated requirements

Best Practices

✓ Do

  • +Validate research and competitive analysis with real data
  • +Collaborate with engineering when generating technical requirements
  • +Customize frameworks and templates to your company context
  • +Use skill for first drafts, refine with stakeholder input
  • +Document successful prompt patterns for PM tasks
  • +Combine AI efficiency with human judgment and intuition

✗ Don't

  • Don't publish competitive analysis without fact-checking
  • Don't finalize user stories without engineering review
  • Don't make prioritization decisions solely on AI scoring
  • Don't skip customer validation of generated requirements
  • Don't ignore company-specific context and culture

💡 Pro Tips

  • Provide context: company goals, constraints, customer feedback
  • Ask for alternatives: 'Show 3 ways to prioritize this roadmap'
  • Request stakeholder-specific formatting: 'Executive summary vs. engineering spec'
  • Use skill for 70% generation + 30% customization to company needs

When to Use This

✓ Use when

Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.

✗ Avoid when

Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.

Learning Path

  1. 1Basic: user stories, feature specs, status updates
  2. 2Intermediate: competitive analysis, prioritization frameworks, PRDs
  3. 3Advanced: product strategy, go-to-market planning, OKR setting
  4. 4Expert: product vision, market positioning, business model innovation

Related Skills

Reviews

4.649 reviews
  • D
    Dhruvi JainDec 24, 2024

    asc-subscription-localization is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.

  • N
    Noor RaoDec 20, 2024

    We added asc-subscription-localization from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.

  • S
    Sakura YangDec 8, 2024

    asc-subscription-localization has been reliable in day-to-day use. Documentation quality is above average for community skills.

  • I
    Ishan BhatiaDec 8, 2024

    asc-subscription-localization reduced setup friction for our internal harness; good balance of opinion and flexibility.

  • R
    Ren MenonNov 27, 2024

    Solid pick for teams standardizing on skills: asc-subscription-localization is focused, and the summary matches what you get after install.

  • C
    Camila MartinezNov 27, 2024

    Registry listing for asc-subscription-localization matched our evaluation — installs cleanly and behaves as described in the markdown.

  • O
    OshnikdeepNov 15, 2024

    asc-subscription-localization fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.

  • A
    Amelia MehtaNov 11, 2024

    Useful defaults in asc-subscription-localization — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.

  • S
    Sofia NasserOct 18, 2024

    asc-subscription-localization is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.

  • K
    Kabir SmithOct 18, 2024

    Useful defaults in asc-subscription-localization — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.

showing 1-10 of 49

1 / 5

Discussion

Comments — not star reviews
  • No comments yet — start the thread.