asc-revenuecat-catalog-sync

Audits and reconciles App Store Connect catalogs with RevenueCat resources via ASC/RMCP workflows.

1|Updated Aug 16, 2025
One-click install
npx skills add https://github.com/barronlroth/Cubby --skill asc-revenuecat-catalog-sync-barronlroth
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: asc-revenuecat-catalog-sync
Source: https://github.com/barronlroth/Cubby/tree/main/.agents/skills/asc-revenuecat-catalog-sync
Command: npx skills add https://github.com/barronlroth/Cubby --skill asc-revenuecat-catalog-sync-barronlroth

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps align App Store Connect subscriptions and in-app purchases with RevenueCat resources (entitlements, offerings, and packages) using asc and RevenueCat MCP, enabling consistent catalogs across platforms.

Core Features & Use Cases

  • Audit-first reconciliation: read ASC and RevenueCat catalogs, compare differences, and present a deterministic plan.
  • Deterministic mapping: align ASC product identifiers to RevenueCat store_identifiers and attach products to entitlements and offerings.
  • Safe apply workflow: create missing ASC items and RevenueCat resources only after explicit confirmation, with non-destructive reconciliation.

Quick Start

Start by auditing your ASC catalog against RevenueCat to identify gaps, then apply approved changes to bootstrap or fix the catalog.

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, the skill audits both catalogs, maps ASC product identifiers to RevenueCat store_identifiers, and attaches them to entitlements and offerings. It enforces an audit-first approach with explicit write confirmation.

What is the best way to audit RevenueCat entitlements against App Store Connect in-app purchases?

Auditing RevenueCat entitlements against App Store Connect in-app purchases involves reading both catalogs via their respective MCPs to identify drift. The skill presents a deterministic reconciliation plan to compare differences and map products safely.

Can I bootstrap RevenueCat offerings from an existing App Store Connect catalog?

Yes, you can bootstrap RevenueCat offerings from an existing App Store Connect catalog. The skill identifies missing RevenueCat resources and creates them only after explicit confirmation, ensuring a non-destructive reconciliation process.

Does the RevenueCat and App Store Connect reconciliation support multiple apps?

Yes, the deterministic product mapping and reconciliation workflow support multiple apps across both App Store Connect and RevenueCat, aligning subscriptions and in-app purchases with entitlements, offerings, and packages.

How does deterministic IAP mapping work between App Store Connect and RevenueCat?

Deterministic IAP mapping aligns ASC product identifiers with RevenueCat store_identifiers using a strict execution order. This ensures products are correctly attached to entitlements and offerings without ambiguous or destructive writes.

Why do I need explicit confirmation before applying App Store Connect catalog changes to RevenueCat?

Explicit confirmation is required to maintain a non-destructive reconciliation process. The skill enforces this safe apply workflow to ensure missing ASC items and RevenueCat resources are only created after you approve the deterministic plan.