Skip to content

The-Artificer-of-Ciphers-LLC/skills-from-the-artificer / asc-revenuecat-catalog-sync

asc-revenuecat-catalog-sync

Verified

Reconcile App Store Connect subscriptions and in-app purchases with RevenueCat products, entitlements, offerings, and packages using asc and RevenueCat MCP. Use when setting up or syncing subscription catalogs across ASC and RevenueCat.

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 and agent behavior

  • Start in audit mode (read-only), and run the audit first even when apply mode was requested.
  • Ask for explicit confirmation before any create or update; never delete resources in this workflow.
  • Match by store_identifier first; never use display names as identifiers.
  • Use full pagination (--paginate for ASC, starting_after for RevenueCat tools).
  • Continue past per-item failures and report every failure together 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

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 "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.

# create subscription group
asc subscriptions groups create --app "APP_ID" --reference-name "Premium"

# create subscription
asc subscriptions create \
  --group "GROUP_ID" \
  --ref-name "Monthly" \
  --product-id "com.example.premium.monthly" \
  --subscription-period ONE_MONTH

# create iap
asc iap create \
  --app "APP_ID" \
  --type NON_CONSUMABLE \
  --ref-name "Lifetime" \
  --product-id "com.example.lifetime"

Step E - Ensure RevenueCat app and products

Use MCP:

  • create app if missing: mcp_RC_create_app
  • create products: mcp_RC_create_product
    • store_identifier = ASC productId
    • app_id = RevenueCat app ID
    • type from mapping above

Step F - Ensure entitlements and attachments

Use MCP:

  • list/create entitlements: mcp_RC_list_entitlements, mcp_RC_create_entitlement
  • attach products: mcp_RC_attach_products_to_entitlement
  • verify attachments: mcp_RC_get_products_from_entitlement

Step G - Ensure offerings and packages (optional)

Use MCP:

  • list/create/update offerings:
    • mcp_RC_list_offerings
    • mcp_RC_create_offering
    • mcp_RC_update_offering (is_current=true only if requested)
  • list/create packages:
    • mcp_RC_list_packages
    • mcp_RC_create_package
  • attach products to packages:
    • mcp_RC_attach_products_to_package with eligibility_criteria: "all"

Recommended package keys:

  • ONE_WEEK -> $rc_weekly
  • ONE_MONTH -> $rc_monthly
  • TWO_MONTHS -> $rc_two_month
  • THREE_MONTHS -> $rc_three_month
  • SIX_MONTHS -> $rc_six_month
  • ONE_YEAR -> $rc_annual
  • lifetime IAP -> $rc_lifetime
  • custom -> $rc_custom_<name>

Expected output format

Return a final summary with:

  • ASC created counts (groups/subscriptions/IAP)
  • RevenueCat created counts (apps/products/entitlements/offerings/packages)
  • attachment counts (entitlement-products, package-products)
  • skipped existing items
  • failed items with actionable errors

Example:

ASC: created groups=1 subscriptions=2 iap=1, skipped=14, failed=0
RC: created apps=0 products=3 entitlements=2 offerings=1 packages=2, skipped=27, failed=1
Attachments: entitlement_products=3 package_products=2
Failures:
- com.example.premium.annual: duplicate store_identifier exists on another RC app

Common pitfalls

  • Wrong RevenueCat project_id or app ID.
  • Creating RC products under the wrong platform app.
  • Accidentally assigning consumables to entitlements.
  • Skipping the post-create ASC re-read step.
  • Missing offering/package verification after product creation.

Additional resources

reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.Stars: 323kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 323kUpdated Claude CodeCodexVerifiedInstall
executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is availableStars: 323kUpdated Claude CodeCodexVerifiedInstall