Asc Revenuecat Catalog Sync
Align App Store Connect subscriptions and IAPs with RevenueCat products, entitlements, and offerings before shipping paid mobile apps.
Overview
asc-revenuecat-catalog-sync is an agent skill most often used in Build (also Validate, Ship) that reconciles App Store Connect and RevenueCat subscription catalogs via asc and RevenueCat MCP.
Install
npx skills add https://github.com/rudrankriyam/asc-skills --skill asc-revenuecat-catalog-syncWhat is this skill?
- Read-only drift audit mode before any writes
- Deterministic cross-system mapping on ASC product identifiers
- Create missing ASC items then map into RevenueCat resources
- Per-item failure tolerance with a consolidated failure report at the end
- Explicit write confirmation; workflow never deletes ASC or RevenueCat resources
- Starts in read-only audit mode before writes
- Never deletes resources in this workflow
- Requires write-enabled RevenueCat API v2 key to apply changes
Adoption & trust: 850 installs on skills.sh; 845 GitHub stars; 3/3 security scanners passed (skills.sh audits).
What problem does it solve?
Your ASC products and RevenueCat entitlements diverge or are incomplete, so you risk broken purchases or wrong offerings at release.
Who is it for?
Indie mobile apps already on ASC and RevenueCat who need a structured audit-then-sync ritual before a subscription launch or catalog change.
Skip if: Teams without ASC or RevenueCat credentials configured, or anyone who only needs GA4 traffic reporting instead of store monetization sync.
When should I use this skill?
Setting up or syncing subscription catalogs across App Store Connect and RevenueCat, including bootstrap, create-and-map, or pre-release drift audit flows.
What do I get? / Deliverables
You get a deterministic identifier map, optional created ASC items, and aligned RevenueCat products, entitlements, offerings, and packages ready for release testing.
- Cross-system identifier mapping report
- Aligned RevenueCat products, entitlements, offerings, and packages
- Aggregated per-item failure log after apply runs
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
Catalog mapping is primarily an integration task during product build when wiring monetization stacks. Uses asc CLI and RevenueCat MCP together—classic third-party subscription integration work.
Where it fits
Compare ASC price tiers and RevenueCat packages before you commit to a subscription model.
Wire asc and RevenueCat MCP to create missing products and map entitlements deterministically.
Run a final drift audit so offerings match what TestFlight and production builds expect.
How it compares
Use this integration workflow instead of hand-editing RevenueCat dashboards while guessing ASC product IDs.
Common Questions / FAQ
Who is asc-revenuecat-catalog-sync for?
Solo builders and small teams shipping iOS or Mac apps with subscriptions who use App Store Connect plus RevenueCat and want agent-guided catalog reconciliation.
When should I use asc-revenuecat-catalog-sync?
Use it when bootstrapping RevenueCat from ASC, creating missing ASC IAPs then mapping them, or running a drift audit before release; it fits Validate pricing checks, Build integrations, and Ship launch prep.
Is asc-revenuecat-catalog-sync safe to install?
The skill defaults to audit-only and requires confirmation before writes and never deletes resources; review the Security Audits panel on this Prism page before enabling write keys in your agent.
SKILL.md
READMESKILL.md - Asc Revenuecat Catalog Sync
# 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. ## Safety defaults - Start in **audit mode** (read-only). - Require explicit confirmation before writes. - Never delete resources in this workflow. - Continue on per-item failures and report all failures at the end. ## Canonical identifiers - Primary cross-system key: ASC `productId` == RevenueCat `store_identifier`. - Keep `productId` stable once products are live. - Do not use display names as unique identifiers. ## Scope boundary - RevenueCat MCP configures RevenueCat resources; it does not create App Store Connect products directly. - Use `asc` commands to create missing ASC subscription groups, subscriptions, and IAPs before RevenueCat mapping. ## Modes ### 1) Audit mode (default) 1. Read ASC source catalog. 2. Read RevenueCat target catalog. 3. Build a diff with actions: - missing in ASC - missing in RevenueCat - mapping conflicts (identifier/type/app mismatch) 4. Present a plan and wait for confirmation. ### 2) Apply mode (explicit) Execute approved actions in this order: 1. Ensure ASC groups/subscriptions/IAP exist. 2. Ensure RevenueCat app/products exist. 3. Ensure entitlements and product attachments. 4. Ensure offerings/packages and package attachments. 5. Verify and print a final reconciliation summary. ## Step-by-step workflow ### Step A - Read current ASC catalog ```bash asc subscriptions groups list --app "APP_ID" --paginate --output json asc iap list --app "APP_ID" --paginate --output json # for each subscription group: asc subscriptions list --group-id "GROUP_ID" --paginate --output json ``` ### Step B - Read current RevenueCat catalog (MCP) Use these MCP tools (with `project_id` and pagination where applicable): - `mcp_RC_get_project` - `mcp_RC_list_apps` - `mcp_RC_list_products` - `mcp_RC_list_entitlements` - `mcp_RC_list_offerings` - `mcp_RC_list_packages` ### Step C - Build mapping plan Map ASC product types to RevenueCat product types: - ASC subscription -> RevenueCat `subscription` - ASC IAP `CONSUMABLE` -> RevenueCat `consumable` - ASC IAP `NON_CONSUMABLE` -> RevenueCat `non_consumable` - ASC IAP `NON_RENEWING_SUBSCRIPTION` -> RevenueCat `non_renewing_subscription` Suggested entitlement policy: - subscriptions: one entitlement per subscription group (or explicit map provided by user) - non-consumable IAP: one entitlement per product - consumable IAP: no entitlement by default unless user asks ### Step D - Ensure missing ASC items (if requested) Create missing ASC resources first, then re-read ASC to capture canonical IDs. ```bash # create subscription group asc subscriptions groups create --app "APP_ID" --reference-name "Premium" # create subscription asc subscriptions create \ --group-id "GROUP_ID" \ --reference-name "Monthly" \ --product-id "com.example.premium.monthly