asc-revenuecat-catalog-sync

Reconcile App Store Connect subscriptions and IAPs with RevenueCat products, entitlements, and offerings.

Updated Feb 16, 2026
One-click install
npx skills add https://github.com/dustinober1/sundee-fundee-ios --skill asc-revenuecat-catalog-sync-dustinober1
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: asc-revenuecat-catalog-sync
Source: https://github.com/dustinober1/sundee-fundee-ios/tree/main/SundeeFundeeApp/.agents/skills/asc-revenuecat-catalog-sync
Command: npx skills add https://github.com/dustinober1/sundee-fundee-ios --skill asc-revenuecat-catalog-sync-dustinober1

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Keeping App Store Connect (ASC) and RevenueCat catalogs in sync is error-prone: product identifiers drift, entitlements get misattached, and missing ASC metadata blocks RevenueCat mapping. This Skill audits both systems, builds a deterministic diff, and applies approved changes safely. ## Core Features & Use Cases - Read-only drift audit: Compare ASC subscription groups, subscriptions, and IAPs against RevenueCat apps, products, entitlements, offerings, and packages, then present a no-write reconciliation plan. - Guided apply mode: Create missing ASC groups, subscriptions, and IAPs with pricing, localizations, and review screenshots, then map them to RevenueCat products, entitlements, and offerings in a fixed order. - Strict validation gates: Run asc validate subscriptions and asc validate iap in strict mode and block RevenueCat mapping until both exit cleanly. - Use Case: Before a release, audit your ASC catalog against RevenueCat, create a missing annual subscription with pricing and localization, validate it, then attach it to the premium entitlement and $rc_annual package. ## Quick Start Ask the agent to audit your App Store Connect subscriptions and IAPs against your RevenueCat project and show what is missing on either side.

Frequently Asked Questions about asc-revenuecat-catalog-sync

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I sync App Store Connect products with RevenueCat?▼

Audit both catalogs first, then create missing ASC subscriptions or IAPs with the asc CLI, and map them to RevenueCat products using the ASC productId as the RevenueCat store_identifier. Attach products to entitlements and packages only after strict ASC validation passes.

How do I audit drift between App Store Connect and RevenueCat?▼

Run the read-only audit mode: list ASC subscription groups, subscriptions, and IAPs with fully paginated asc commands, list RevenueCat apps, products, entitlements, offerings, and packages via MCP, then diff by productId to find missing items and type or platform mismatches.

Should consumable IAPs be attached to RevenueCat entitlements?▼

No, consumable IAPs should not be attached to entitlements by default because they do not grant durable access. Non-consumable IAPs get one entitlement per product, and subscriptions typically share one entitlement per subscription group.

Why is my RevenueCat product mapping blocked after creating an ASC subscription?▼

Mapping is blocked until the strict ASC validators exit zero. A subscription with MISSING_METADATA, an incomplete review screenshot, or incomplete pricing coverage fails the gate, so finish localization, screenshot delivery, and the full price matrix first.

Can this workflow delete App Store Connect or RevenueCat resources?▼

No, the workflow never deletes resources in either system. It only creates missing items, updates differing localizations, and reuses existing resources matched by exact identifiers, stopping for explicit user input when matches are ambiguous.