Asc Revenuecat Catalog Sync

If you're managing iOS or macOS subscriptions across App Store Connect and RevenueCat, this keeps the two catalogs in sync. It audits both sides, spots missing products or mapping conflicts, then optionally creates ASC subscription groups and IAPs before mapping them into RevenueCat products, entitlements, offerings, and packages. The workflow is audit first, explicit confirmation before writes, and it won't delete anything. Useful for bootstrapping RevenueCat from an existing ASC catalog or catching drift before a release. The identifier mapping is straightforward: ASC productId becomes RevenueCat store_identifier, and it handles all the IAP type conversions automatically.

skills.sh installs: 1K
GitHub stars: 905
last updated: Jul 14, 2026

View on GitHub

Install

$ npx -y skills add rudrankriyam/asc-skills --skill asc-revenuecat-catalog-sync --agent claude-code

Installs into .claude/skills of the current project.

Files

asc RevenueCat catalog sync

Use this skill to keep App Store Connect (ASC) and RevenueCat aligned, including creating missing ASC items and mapping them to RevenueCat resources.

When to use

You want to bootstrap RevenueCat from an existing ASC catalog.
You want to create missing ASC subscriptions/IAPs, then map them into RevenueCat.
You need a drift audit before release.
You want deterministic product mapping based on identifiers.

Preconditions

asc authentication is configured (asc auth login or ASC_* env vars).
RevenueCat MCP server is configured and authenticated.
In Cursor and VS Code, OAuth auth is available for RevenueCat MCP. API key auth is also supported.
You know:
- ASC app ID (APP_ID)
- RevenueCat project_id
- target RevenueCat app type (app_store or mac_app_store) and bundle ID for create flows
Use a write-enabled RevenueCat API v2 key when applying changes.