asc-revenuecat-catalog-sync

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

70|4|Updated Jul 22, 2025
One-click install
npx skills add https://github.com/AlexW00/Zettel --skill asc-revenuecat-catalog-sync-alexw00
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: asc-revenuecat-catalog-sync
Source: https://github.com/AlexW00/Zettel/tree/main/.agents/skills/asc-revenuecat-catalog-sync
Command: npx skills add https://github.com/AlexW00/Zettel --skill asc-revenuecat-catalog-sync-alexw00

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Keeping App Store Connect (ASC) and RevenueCat catalogs in sync is error-prone manual work: product IDs drift, entitlements get misattached, and missing subscriptions block releases. This Skill audits both systems, builds a deterministic diff, and applies approved changes safely. ## Core Features & Use Cases - Drift Audit: Read the full ASC and RevenueCat catalogs and produce a no-write reconciliation report showing missing items, type mismatches, and platform conflicts. - Deterministic Apply Mode: Create missing ASC subscription groups, subscriptions, and IAPs via the asc CLI, then map them to RevenueCat products, entitlements, offerings, and packages via RevenueCat MCP. - Strict Validation Gates: Run asc strict validators before any RevenueCat mapping, blocking products with missing metadata, incomplete pricing, or failed review screenshots. - Use Case: Before a release, audit your iOS app's subscriptions against RevenueCat, create the missing annual plan in ASC with pricing and localizations, then attach it to the premium entitlement and default offering. ## 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?▼

Run an audit first: list ASC subscription groups, subscriptions, and IAPs with the asc CLI, then list RevenueCat apps, products, entitlements, and offerings via MCP. Match items by productId/store_identifier, present a diff plan, and apply approved creates in order: ASC resources, then RevenueCat products, entitlements, and offerings.

How do I create a missing App Store Connect subscription from the command line?▼

Use asc subscriptions setup with the app ID, group ID, reference name, product ID, subscription period, review screenshot, price, and territories. Then create version localizations and run asc validate subscriptions --strict before mapping the product to RevenueCat.

Should consumable IAPs be attached to RevenueCat entitlements?▼

No, consumables should not be attached to entitlements by default because they are consumed rather than unlocking lasting access. Non-consumable IAPs typically get one entitlement per product, and subscriptions get one entitlement per subscription group.

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

Mapping is blocked when the strict ASC validator reports warnings, MISSING_METADATA, an incomplete review screenshot, or incomplete pricing coverage. Finish localization, screenshot delivery, the complete price matrix, and availability in ASC, then re-run the validator until it exits zero.

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

No, the workflow never deletes resources in either system. It only creates missing items or updates differing localizations after explicit confirmation, and it stops for user input whenever identifier matching is ambiguous.