rc-setup
Use this skill when setting up a RevenueCat project for Android: creating the app in the dashboard, uploading the Google Play service account credentials, configuring entitlements and offerings, and getting the public SDK API key for the Android app.
- Installs
- 643
- 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-setup- 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-setup 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.
RevenueCat Android Setup
Configure a RevenueCat project so the Android SDK can fetch offerings, validate purchases, and grant entitlements. This skill covers the dashboard side of setup and the service account connection to Google Play.
The scope stops at "dashboard ready, API key in hand." SDK initialization code belongs to the rc-configuring-the-sdk skill.
Phase 1: Discovery
Confirm these items before you touch the RevenueCat dashboard. Missing any of them will block the connection step.
| Prerequisite | Where it lives | Why RevenueCat needs it |
|---|---|---|
| Google Play Console app | Play Console | Dashboard connects by package name |
| Package name | Play Console app listing | Must match your Android app exactly |
| In-app products or subscriptions | Play Console monetization | RevenueCat imports the catalog |
| Base plans for subscriptions | Play Console subscription | Billing Library 6+ requires them |
| Google Cloud service account JSON | Google Cloud Console | RevenueCat authenticates to the Play Developer API |
| Financial data viewer permission | Play Console users and permissions | Service account reads subscription state |
Ask the user:
- Is the app already published on Play (even as internal testing)?
- Are products live in Play Console, or still drafts?
- Do you have the service account JSON, or do you need the creation steps?
If products do not exist yet, pause. Product creation is a Play Console task outside this skill.
Phase 2: Plan
Pick the route that matches the user's state.
| State | Route |
|---|---|
| No RevenueCat account | Start at Step 1, create account and project |
| Account exists, no Android app in project | Start at Step 2, add Android app |
| App exists, Play not connected | Jump to Step 3, upload service account |
| Play connected, no entitlements or offerings | Jump to Step 4 |
| Everything configured, need the API key | Jump to Phase 4 verification |
The default flow below runs end to end. Skip steps the user has already completed.
Phase 3: Execute
Step 1: Create the RevenueCat project and Android app
- Sign up or log in at
app.revenuecat.com. - Create a project. One project can hold Android, iOS, and web apps for the same product.
- Inside the project, add an Android app. Enter the Play Console package name.
RevenueCat generates a public SDK API key per platform. You will copy the Android key at the end. Do not reuse iOS or web keys in the Android app.
Step 2: Create a Google Cloud service account (if needed)
In Google Cloud Console, on the project linked to your Play Console:
- Enable the Google Play Android Developer API.
- Create a service account. Skip role grants on the Cloud side.
- Create a JSON key for the service account and download it.
In Play Console, under Users and permissions:
- Invite the service account email.
- Grant app-level access to the app.
- Grant the Financial data viewer permission. RevenueCat needs it to read subscription state.
Step 3: Connect Google Play in RevenueCat
In the RevenueCat dashboard, open the Android app settings:
- Confirm the package name matches Play Console.
- Upload the service account JSON key file.
- Save.
RevenueCat validates the credential by calling the Play Developer API. If validation fails, the common causes are missing API enablement, wrong project, or the service account not yet propagated in Play (allow up to 24 hours).
Step 4: Create entitlements
Entitlements are the access levels your app checks. Define them once, reference them everywhere in client code.
In the dashboard under Entitlements, create one per access tier. Most apps ship with a single entitlement.
| Identifier | Description |
|---|---|
pro_access | Unlocks premium features |
team_access | Unlocks team features (second tier, optional) |
Use a stable identifier. Renaming an entitlement later means rewriting every feature gate.
Step 5: Import products and attach entitlements
Under Products, click Import. RevenueCat pulls the Play catalog through the connected service account.
- Select each product you want RevenueCat to manage.
- Attach each product to an entitlement. Purchasing the product grants that entitlement.
A single entitlement can back many products (monthly, annual, lifetime all unlock pro_access).
Step 6: Create an offering
Offerings drive what a user sees on the paywall. One offering groups multiple packages.
Under Offerings:
- Create an offering (for example,
default). - Add packages. Pick a package type (Monthly, Annual, Lifetime, or custom) and assign a product.
- Mark one offering as Current.
The Android SDK fetches offerings.current to show the default paywall. Swap the current offering later from the dashboard without shipping an app update.
Step 7: Copy the Android API key
In the Android app settings, copy the public SDK API key. This value is the second argument to PurchasesConfiguration.Builder. The skill configuring-the-sdk uses it.
// Handed off to configuring-the-sdk
val revenueCatApiKey = "goog_xxxxxxxxxxxxxxxxxxxxxxxx"
Phase 4: Verify
Confirm the dashboard and Play Console are wired together before moving to SDK work.
| Check | How to verify | Pass signal |
|---|---|---|
| Service account accepted | RevenueCat app settings, Google Play section | Shows connected with a green indicator |
| Products imported | Products tab in dashboard | Play products appear with live prices |
| Entitlement attachments | Open each product | Shows the attached entitlement |
| Offering current | Offerings tab | One offering tagged Current |
| Package product links | Open the current offering | Each package shows a product identifier |
| API key scope | Project settings, API keys | Android key is distinct from iOS and web keys |
Ask the user to confirm each row. If a product shows no price, the service account is connected but the product is not active in Play. Fix the Play listing, then re-import.
Hand off to rc-configuring-the-sdk with:
- The Android API key
- The current offering identifier
- The entitlement identifiers the app will check
References
FAQ
What does the rc-setup skill do?
Use this skill when setting up a RevenueCat project for Android: creating the app in the dashboard, uploading the Google Play service account credentials, configuring entitlements and offerings, and getting the public SDK API key for the Android app.
How do I install rc-setup?
Run npx skills add https://github.com/revenuecat/ai-toolkit --skill rc-setup 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-setup/ (personal) or .claude/skills/rc-setup/ (project).
Which AI agents can use rc-setup?
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-setup 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-setup?
It is published by revenuecat in revenuecat/ai-toolkit. It has 643 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 mobile skills
design-mobile-apps
designed-by-ai/skills
Design mobile app screens with Sleek, edit Sleek projects, and implement their designs in React Native or HTML.
ios-design
uizze.sh
Design and review iOS UI/UX for iPhone apps in SwiftUI, UIKit, or React Native. Use for mobile app design, screen redesigns, navigation flows, typography, forms, keyboard and safe-area layout, and accessibility checks. Apply Apple Human Interface Guidelines and consult real product references through the optional Uizze connection.
vercel-react-native-skills
vercel-labs/agent-skills
React Native and Expo best practices for building performant mobile apps. Use when building React Native components, optimizing list performance, implementing animations, or working with native modules. Triggers on tasks involving React Native, Expo, mobile performance, or native platform APIs.
animate-expo
emilkowalski/skills
Build animations in React Native and Expo, making the decisions in the order that determines whether they feel right — should it animate, which thread it runs on, which properties, spring or timing, how the gesture hands off, how it degrades. Writes the implementation with Reanimated, Gesture Handler, Expo Router and expo-haptics. Use when animating anything in an Expo app, adding gestures, sheets, screen transitions, press feedback or haptics, or fixing motion that stutters on device. For web animation use animate.
xcode-project-setup
firebase/agent-skills
Safely modifies Xcode projects (.pbxproj) to add Swift Packages and link files. Use this skill whenever an iOS project needs dependencies installed (e.g. Firebase, Alamofire).
firebase-remote-config-basics
firebase/agent-skills
Manages Firebase Remote Config templates, feature flags, loading strategies, and SDKs (Android, iOS). Use when downloading/deploying remoteconfig JSON templates, managing version history/feature flags, setting in-app defaults, fetchAndActivate(), real-time listeners, or SDK setup. Don't use for Firebase Hosting, Auth, Firestore, Data Connect, Crashlytics, or App Hosting.