Agent skill · AI & Agents

asc-revenuecat-catalog-sync

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.

rorkaigithub.com/rorkaiGitHub ↗
claude-codeMIT
Install
npx skills add rorkai/app-store-connect-cli-skills --skill asc-revenuecat-catalog-sync --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 3
SKILL.md size: 14 KB
Bundled scripts: none
Path: skills/asc-revenuecat-catalog-sync/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 948
Language: Python

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# 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 - Start in **audit mode** (read-only). - Require explicit confirmation before writes. - Never delete resources in this workflow. - Continue on per-item failures and report all failures at the end. ## Canonical identifiers - Primary cross-system key: ASC `prod

What's inside
Steps it walks through
  1. When to use
  2. Preconditions
  3. Safety defaults
  4. Canonical identifiers
  5. Scope boundary
  6. Modes
  7. 1) Audit mode (default)
  8. 2) Apply mode (explicit)
  9. Step-by-step workflow
  10. Step A - Read current ASC catalog
  11. Step B - Read current RevenueCat catalog (MCP)
  12. Step C - Build mapping plan
  13. Step D - Ensure missing ASC items (if requested)
  14. Step E - Ensure RevenueCat app and products
Ships with 2 files
  • examples.md
  • references.md
Commands it runs
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-id "GROUP_ID" --paginate --output json
Resolve GROUP_ID by exact referenceName.
If and only if the fully paginated list has zero exact matches:
asc subscriptions groups create --app "APP_ID" --reference-name "Premium" --output json
For one match, reuse its ID. For more than one, stop and require an explicit GROUP_ID.
Resolve SUB_ID by exact productId within GROUP_ID. Run setup only for a missing
parent or an explicitly approved reconciliation of that same product ID.
More from app-store-connect-cli-skills
All skills →
About this skill
What does the asc-revenuecat-catalog-sync skill do?

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.

How do I install it?

Run `npx skills add rorkai/app-store-connect-cli-skills --skill asc-revenuecat-catalog-sync --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From rorkai/app-store-connect-cli-skills, a repository with 948 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going