asc-revenuecat-catalog-sync

Reconcile and synchronize App Store Connect catalogs with RevenueCat resources using productId.

954|51|Updated Jan 27, 2026
One-click install
npx skills add https://github.com/rudrankriyam/app-store-connect-cli-skills --skill asc-revenuecat-catalog-sync-rudrankriyam
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: asc-revenuecat-catalog-sync
Source: https://github.com/rudrankriyam/app-store-connect-cli-skills/tree/main/skills/asc-revenuecat-catalog-sync
Command: npx skills add https://github.com/rudrankriyam/app-store-connect-cli-skills --skill asc-revenuecat-catalog-sync-rudrankriyam

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill synchronizes your App Store Connect (ASC) subscriptions and in-app purchases with your RevenueCat products, entitlements, offerings, and packages, ensuring consistency and automating catalog management.

Core Features & Use Cases

  • Catalog Reconciliation: Compares ASC and RevenueCat catalogs to identify discrepancies.
  • Automated Creation: Creates missing items in either ASC or RevenueCat based on your configuration.
  • Deterministic Mapping: Uses productId as the primary key for reliable mapping.
  • Use Case: When launching a new app or updating your in-app purchase offerings, use this Skill to ensure that all products defined in App Store Connect are correctly mirrored in RevenueCat, including their associated entitlements and pricing tiers.

Quick Start

Run an audit of your App Store Connect catalog against RevenueCat to identify any discrepancies.

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 subscriptions with RevenueCat products?

To sync App Store Connect subscriptions with RevenueCat products, you can automate catalog reconciliation using the `productId` as the canonical identifier to map items directly to RevenueCat entitlements, offerings, and packages.

What is the best way to reconcile in-app purchase catalogs between ASC and RevenueCat?

The best way to reconcile in-app purchase catalogs is to compare ASC and RevenueCat data to identify discrepancies, then automatically create missing items in either platform to ensure your offerings match perfectly.

Do I need the `asc` CLI to bootstrap RevenueCat from existing App Store Connect data?

Yes, you need the `asc` CLI and RevenueCat MCP tools to bootstrap RevenueCat from existing App Store Connect data. These tools execute the synchronization and creation of missing subscription and in-app purchase items.

Can I create missing in-app purchases in App Store Connect using RevenueCat data?

Yes, you can create missing in-app purchases in App Store Connect using RevenueCat data. The synchronization process supports creating missing ASC items and mapping them back to RevenueCat resources.

How does deterministic mapping work when syncing RevenueCat and ASC catalogs?

Deterministic mapping works by using the App Store Connect `productId` as the primary key. This reliably maps ASC subscriptions and in-app purchases to their corresponding RevenueCat products and entitlements.

Why are my RevenueCat entitlements not matching my App Store Connect subscription tiers?

RevenueCat entitlements might not match App Store Connect subscription tiers due to catalog discrepancies. Running an audit reconciles both platforms and automatically creates missing items to ensure consistency.