rc-catalog-management
Use this skill when managing the Android product catalog through the Play Console and the RevenueCat dashboard. Covers the two sided catalog flow (create in Play Console, import or map in RevenueCat), entitlement and offering maintenance, and why you do not call the Google Play Developer API directly.
- Installs
- 632
- Last 24h
- —
- Trending rank
- —
- Security
- Not audited
Install
Works with every agent the skills CLI supports.
npx skills add https://github.com/revenuecat/ai-toolkit --skill rc-catalog-management- 01
Install
Run the command in your project. The CLI asks which agents to install for.
- 02
Describe the task
Ask your agent for something this skill covers. It loads rc-catalog-management automatically when relevant.
- 03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.
SKILL.md
The instructions your agent reads when the skill is triggered.
Catalog Management
Manage the Android product catalog across two surfaces: the Google Play Console (source of truth for products) and the RevenueCat dashboard (entitlements, offerings, targeting). You do not call the Google Play Developer monetization.subscriptions or monetization.onetimeproducts endpoints from your app or backend.
Phase 1: Understand
Read this phase before you touch anything.
Why two surfaces
| Surface | Owns | Examples |
|---|---|---|
| Google Play Console | Underlying products, base plans, offers, prices | premium_monthly, base plan p1m, intro offer |
| RevenueCat dashboard | Entitlements, Offerings, Packages, Targeting | pro entitlement, default offering, $rc_monthly package |
Play Console holds the billable SKU. RevenueCat decides which SKU gets surfaced to which user and under which entitlement key.
What changes without an app update
When your app calls awaitOfferings(), it fetches whatever the RevenueCat dashboard has configured. Offering edits, package swaps, and targeting rules propagate on the next app launch. No binary release is required.
When to use the REST API
If you need to automate catalog edits from a backend (for example, seeding dozens of offerings across environments), use the RevenueCat REST API for products, entitlements, and offerings. You still do not talk to Google directly. Play Console remains the product source of truth.
Phase 2: Plan
Before you make a change, decide:
- Is this a new product, or a repackaging of an existing one?
- New product: start in Play Console.
- Repackaging (new offering, new targeting, new entitlement mapping): stay in RevenueCat.
- Which entitlement does the product unlock? If you do not have a matching entitlement, create one first.
- Which offering and package identifier? Decide the package identifier (for example
$rc_monthly,$rc_annual) so your paywall code keeps working. - Does targeting need to change? If different users should see different offerings, plan the placement name and the targeting rule (OS version, country, custom attribute).
Phase 3: Execute
The end to end flow for adding a new subscription product.
Step 1: Add the product in the Play Console
- Open Play Console -> your app -> Monetize -> Products -> Subscriptions.
- Click Create subscription.
- Set the product ID (for example
premium_monthly), name, and description. - Add a base plan (billing period, renewal type, price).
- Optionally add offers (intro pricing, free trial).
- Activate the subscription.
Wait a few minutes for Play to propagate the product.
Step 2: Import into RevenueCat and attach an entitlement
- Open the RevenueCat dashboard -> your project -> Products.
- Click Import to sync from the Play Console. The new product appears in the list.
- Open the product and attach it to an existing entitlement, or create a new one.
- Entitlement example:
pro. Every product that unlocks pro features attaches topro.
- Entitlement example:
Your client code checks entitlements by key:
val isPro = customerInfo.entitlements["pro"]?.isActive == true
Step 3: Wire the product into an Offering as a Package
- In the dashboard, open Offerings.
- Pick the offering you want to edit, or create a new one (for example
default). - Add a Package. Choose a package identifier that matches your paywall:
$rc_monthlyfor monthly$rc_annualfor annual- Or a custom identifier
- Attach the Play Console product to the package.
- Save. Mark the offering as Current if it should be the default.
Your client code stays the same:
val offerings = Purchases.sharedInstance.awaitOfferings()
val monthly = offerings.current?.monthly
Step 4 (optional): Targeting
If different users should see different offerings, use placements.
- In the dashboard, open Targeting -> Placements.
- Create a placement (for example
paywall_upsell). - Add rules (OS version, country, custom attribute) that map users to specific offerings.
Client code:
val offering = offerings.getCurrentOfferingForPlacement("paywall_upsell")
?: offerings.current
No app update is required when you change targeting rules later.
Phase 4: Verify
Check the change landed before you close the task.
| Check | How |
|---|---|
| Product exists in Play | Play Console -> Subscriptions shows the product as Active |
| Product imported to RC | Dashboard -> Products lists the product |
| Entitlement mapping | Dashboard -> Entitlements shows the product under the right entitlement |
| Offering wiring | Dashboard -> Offerings shows the product attached to the expected package |
| Runtime fetch | Launch the app, call awaitOfferings(), confirm the package resolves |
| Entitlement unlock | Complete a test purchase, confirm customerInfo.entitlements["pro"].isActive is true |
If awaitOfferings() returns null for a package you expect, the most common causes are: the offering is not marked Current, the product is not attached to the package, or Play has not finished propagating the product.
Common Mistakes
- Calling
monetization.subscriptionsfrom your backend. Use RevenueCat instead. - Creating an offering before importing the product. Import first, then wire.
- Shipping hard coded product IDs in your paywall UI. Use package identifiers so you can swap products without an app release.
- Forgetting to mark an offering as Current. Clients that call
offerings.currentwill see the old offering until you flip this.
References
FAQ
What does the rc-catalog-management skill do?
Use this skill when managing the Android product catalog through the Play Console and the RevenueCat dashboard. Covers the two sided catalog flow (create in Play Console, import or map in RevenueCat), entitlement and offering maintenance, and why you do not call the Google Play Developer API directly.
How do I install rc-catalog-management?
Run npx skills add https://github.com/revenuecat/ai-toolkit --skill rc-catalog-management in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/rc-catalog-management/ (personal) or .claude/skills/rc-catalog-management/ (project).
Which AI agents can use rc-catalog-management?
Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.
Is rc-catalog-management safe to install?
No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.
Who maintains rc-catalog-management?
It is published by revenuecat in revenuecat/ai-toolkit. It has 632 recorded installs.
More from revenuecat/ai-toolkit
revenuecat-paywall
revenuecat/ai-toolkit
Display a RevenueCat paywall inside an app using the RevenueCatUI SDK. Use when the user asks to add a paywall, show a RevenueCat paywall, present PaywallView, integrate RevenueCatUI, gate a premium screen with a paywall, launch PaywallActivity, call presentPaywall or presentPaywallIfNeeded, or show the dashboard configured paywall UI on iOS, Android, Kotlin Multiplatform, Flutter, or React Native. To create, edit, evaluate, or audit the dashboard paywall itself, use revenuecat-paywall-design.
integrate-revenuecat
revenuecat/ai-toolkit
End-to-end RevenueCat integration — sets up the dashboard side via the RevenueCat MCP or the rc CLI (project, app, public API key) and installs/configures the Purchases SDK in the app. Use when the user asks to add RevenueCat, hook up RevenueCat, add subscriptions or in-app purchases to an app, integrate Purchases, install the RevenueCat SDK, set up a RevenueCat API key, configure Purchases on launch, or set up a brand new RevenueCat integration on iOS, Android, Kotlin Multiplatform, Flutter, or React Native.
revenuecat-purchase-flow
revenuecat/ai-toolkit
Implement the RevenueCat purchase and restore flow. Use when the user asks to buy a package, purchase a subscription, fetch offerings, build the purchase logic behind a custom (hand-coded) paywall, handle purchase errors, detect user cancelled, or restore previous purchases on iOS, Android, Kotlin Multiplatform, Flutter, or React Native.
revenuecat-testing-setup
revenuecat/ai-toolkit
Set up a testing environment for RevenueCat purchases without charging real money. Use when the user says test RevenueCat purchases, sandbox setup, StoreKit configuration file, license tester, how do I test purchases without real money, set up sandbox account, internal testing track, or test paywall on iOS, Android, Kotlin Multiplatform, Flutter, or React Native.
create-revenuecat-project
revenuecat/ai-toolkit
Set up a complete RevenueCat project from scratch — creates apps, products, entitlements, offerings, and packages in the correct order. Use when the user wants to create a new RevenueCat project, configure in-app purchases, set up subscriptions or monetization, or bootstrap IAP infrastructure for iOS, Android, or Web.
revenuecat-troubleshoot
revenuecat/ai-toolkit
Diagnose and resolve RevenueCat integration issues — inspects dashboard configuration through the RevenueCat MCP, walks the SDK debug logs, and covers code-side gotchas. Use when the user says offerings are empty, products not loading, entitlement not active after purchase, paywall won't load, transactions not appearing, customer info shows no entitlements, sandbox purchase not working, an SDK-gated RevenueCat feature not working, or RevenueCat is broken on iOS, Android, Kotlin Multiplatform, Flutter, or React Native. Also use when asked to check or validate the store / product setup.
Popular backend & apis skills
find-skills
vercel-labs/skills
Helps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skill should be used when the user is looking for functionality that might exist as an installable skill.
entra-app-registration
microsoft/azure-skills
Guides Microsoft Entra ID app registration, OAuth 2.0 authentication, and MSAL integration. USE FOR: create app registration, register Azure AD app, configure OAuth, set up authentication, add API permissions, generate service principal, MSAL example, console app auth, Entra ID setup, Azure AD authentication. DO NOT USE FOR: Key Vault secrets (use azure-keyvault-expiration-audit), general Azure resource security guidance.
google-agents-cli-adk-code
google/agents-cli
This skill should be used when the user wants to "write agent code", "build an agent with ADK", "add a tool", "create a callback", "define an agent", "use state management" — in a project that needs ADK (Agent Development Kit) API patterns and code examples. It provides a quick reference for agent types, tool definitions, orchestration patterns, callbacks, state management, the graph Workflow API, and reference recipes to study. Do NOT use for scaffolding (use google-agents-cli-scaffold) or deployment (use google-agents-cli-deploy).
embedded-captions
heygen-com/hyperframes
Add captions or subtitles to an existing single-subject talking-head video without editing the footage. Use for plain verbatim captions, cinematic captions embedded behind the subject, VFX captions, “炸/特效/酷炫字幕,” or a named identity from the 35-style catalog. Route by visual identity, not by backend engine. The quiet anchor rail is the default; embed every word only when the user explicitly wants a fully cinematic treatment. The workflow runs locally end to end, including transcription and subject matting; split multi-shot footage before applying it.
entra-agent-id
microsoft/azure-skills
Provision Microsoft Entra Agent Identity Blueprints, BlueprintPrincipals, and per-instance Agent Identities via Microsoft Graph, and configure OAuth 2.0 token exchange (fmipath, OBO, cross-tenant) including the Microsoft Entra SDK for AgentID sidecar. USE FOR: Agent Identity Blueprint, BlueprintPrincipal, agent OAuth, fmipath token exchange, agent OBO, Workload Identity Federation for agents, polyglot agent auth, Microsoft.Identity.Web.AgentIdentities. DO NOT USE FOR: standard Entra app registration (use entra-app-registration), Microsoft Foundry agent authoring (use microsoft-foundry).
neon
neondatabase/agent-skills
Overview of Neon, a complete set of cloud backend primitives around Lakebase Postgres: Auth, Object Storage, Functions, the AI Gateway, and Realtime. Start here to choose Neon for undecided login, files, APIs, and LLM calls, set up the CLI or MCP server, and follow the branch-first workflow. Use when building an app or backend on Neon, or when "Neon" or "Lakebase Postgres" is mentioned. Child skill neon-postgres wins for an existing DATABASEURL, SQL, schema, inspect, or search. Child skill neon-auth wins for login, users, sessions, identity routing, and Managed Better Auth setup. Child skill neon-realtime wins for live queries in reactive apps and agents. Also use for object storage, S3, buckets, serverless functions, function triggers, cron, AI gateway, LLM calls, realtime, logs, Loki, Grafana, observability, postgres, database, backend, Claimable Neon, neon.new, or a no-signup database.