asc-revenuecat-catalog-sync

Overview of asc-revenuecat-catalog-sync skill

asc-revenuecat-catalog-sync is a workflow skill for keeping App Store Connect and RevenueCat aligned. It helps you audit drift, create missing ASC subscriptions or in-app purchases, and map those items into RevenueCat products, entitlements, offerings, and packages with less manual cross-checking.

This asc-revenuecat-catalog-sync skill is best for ecommerce and subscription teams that already have a catalog in one system and need a reliable way to mirror it in the other. The main job-to-be-done is not “learn RevenueCat” or “learn ASC” in isolation; it is to move from messy, partially matched catalog data to a deterministic sync plan you can review before writing changes.

What this skill is good for

• Bootstrapping RevenueCat from an existing ASC catalog.
• Creating missing ASC subscriptions or IAPs before mapping them to RevenueCat.
• Running a drift audit before release or migration.
• Preserving stable identifiers so live products do not break.

What makes it different

• It is identifier-driven, not guess-driven: ASC productId is the primary cross-system key.
• It is safer than a one-off prompt because it expects an audit-first workflow.
• It is practical for teams using the asc-revenuecat-catalog-sync guide to reduce sync mistakes and manual reconciliation.

When it is a fit

Use asc-revenuecat-catalog-sync if you already have auth set up for ASC and RevenueCat MCP and you want a repeatable sync process. If you only need a high-level product strategy or a one-time naming brainstorm, this skill is probably more machinery than you need.

How to Use asc-revenuecat-catalog-sync skill

Install and read the right file first

Install the asc-revenuecat-catalog-sync install with:

npx skills add rudrankriyam/app-store-connect-cli-skills --skill asc-revenuecat-catalog-sync

Then start with skills/asc-revenuecat-catalog-sync/SKILL.md. In this repository, there are no helper folders to explore, so the skill file itself is the source of truth. That makes the first read especially important: focus on preconditions, safety defaults, and the canonical identifier rules before you try to run anything.

Give the skill input it can actually use

The asc-revenuecat-catalog-sync usage works best when you provide concrete catalog facts, not a vague goal. Include:

• ASC app ID
• RevenueCat project_id
• target app type: app_store or mac_app_store
• bundle ID for create flows
• whether you want audit-only or write mode
• any known mapping pairs between ASC productId and RevenueCat store_identifier

A strong prompt looks like this:

“Audit my ASC catalog against RevenueCat for app 123456789. Use audit mode first. Here is the current list of ASC product IDs and the existing RevenueCat store identifiers. Flag missing items, mismatches, and any unstable identifiers before proposing writes.”

Follow the safest workflow order

A good asc-revenuecat-catalog-sync guide usually follows this sequence:

1. Confirm auth for asc and RevenueCat MCP.
2. Run read-only audit mode first.
3. Review missing items, drift, and identifier mismatches.
4. Confirm any proposed creates or updates explicitly.
5. Apply writes only after you understand the diff.

For asc-revenuecat-catalog-sync for Ecommerce, the biggest quality gain comes from treating identifiers as the source of truth and avoiding ad hoc renames once products are live.

Check the repository rulebook in the skill text

Before execution, verify three things in SKILL.md:

• safety defaults: no deletes, explicit confirmation before writes
• failure handling: continue per item and summarize failures
• canonical mapping: productId should match store_identifier

Those rules are what make the skill usable in production rather than just convenient in a demo.

asc-revenuecat-catalog-sync skill FAQ

Is this only for RevenueCat users?

No. It is for teams using both App Store Connect and RevenueCat, especially when they need a clean mapping layer between the two. If you are not using RevenueCat MCP, this skill will not help much.

Can I use it if my catalog is messy?

Yes, but expect to start with audit mode and manual review. The skill is designed to expose drift and missing items, not magically infer every ambiguous mapping.

Is this better than a generic prompt?

Usually yes. A generic prompt can describe the goal, but the asc-revenuecat-catalog-sync skill bakes in the important operational constraints: auth, stable identifiers, audit-first behavior, and no-delete safety. That reduces the chance of accidental catalog drift.

What blocks adoption most often?

Missing auth, missing app IDs or project IDs, and unclear identifier strategy. If you cannot confirm the ASC productId to RevenueCat store_identifier mapping, the sync becomes guesswork and output quality drops fast.

How to Improve asc-revenuecat-catalog-sync skill

Provide exact source-of-truth data

The best improvement is cleaner input. Send the current ASC catalog, the current RevenueCat catalog, and any known mapping table in a structured list. The asc-revenuecat-catalog-sync skill performs better when it can compare exact identifiers instead of reading prose about “the monthly plan” or “the premium offering.”

State your intended change scope

Tell the skill whether you want:

• audit only
• create missing ASC items
• map existing items into RevenueCat
• full reconciliation for a release

That scope choice changes what the model should optimize for. Without it, the skill may over-prepare a write plan when you only wanted a drift report.

Treat mismatches as workflow bugs, not naming bugs

If results look wrong, the issue is often unstable IDs, missing auth, or incomplete source data. Fix those first before re-running. For asc-revenuecat-catalog-sync usage, the most useful iteration is usually to tighten identifiers and rerun audit mode, not to ask for broader brainstorming.

Ask for a diff, then validate it

A strong second pass is to request a concise list of:

• missing ASC items
• RevenueCat items without ASC matches
• identifier conflicts
• proposed create/update actions

That format makes it easier to review and approve changes, especially in ecommerce subscription catalogs where small mismatches can create real billing and entitlement issues.