🐱 Agent ready instruction recipes for integrating Google Play Billing & RevenueCat SDK: grounded, drop-in guidance for Android in-app purchases.
RevenueCat/play-billing-skills
Skill Claude CodeCodex
Use this skill when a developer is new to Google Play Billing or needs to orient themselves before picking an implementation task. Maps their goal to the right pillar (Play Billing Library, Google Play Developer API, Play Console plus RTDNs) and routes them to the concrete skill to invoke next.
RevenueCat/play-billing-skills
Skill Claude CodeCodex
Use this skill when your backend needs to read or update RevenueCat state on Android. Covers the RevenueCat REST API (v1 subscribers endpoint, grant/revoke entitlements, attributes), secret vs public SDK API key usage, and why you do not build a receipt verification backend with RevenueCat.
RevenueCat/play-billing-skills
Skill Claude CodeCodex
Use this skill when adding and configuring the RevenueCat Android SDK (purchases-kt/purchases) in an app. Covers the Gradle dependency, Purchases.configure with PurchasesConfiguration, initial app user id strategy, and log level.
RevenueCat/play-billing-skills
Skill Claude CodeCodex
Use this skill as a quick reference for the RevenueCat Android SDK 10.x and REST API. Covers SDK init, common Purchases calls, CustomerInfo / Offerings access patterns, and the most used REST endpoints.
RevenueCat/play-billing-skills
Skill Claude CodeCodex
Use this skill to decide whether to use RevenueCat or raw Google Play Billing on Android. Provides a side by side reference of what RevenueCat handles versus what remains your responsibility at both client and backend layers.
RevenueCat/play-billing-skills
Skill Claude CodeCodex
Use this skill to orient an agent to the RevenueCat Android SDK (10.x) architecture. Covers how RevenueCat reorganizes BillingClient, Google Play Developer API, and RTDN into a single SDK, and how Products, Packages, Offerings, Entitlements, and CustomerInfo connect.
RevenueCat/play-billing-skills
Skill Claude CodeCodex
Use this skill when consuming RevenueCat webhooks on your backend. Covers the normalized event schema, the full event type list, idempotency via the event id field, and the correct handling for CANCELLATION versus EXPIRATION versus RENEWAL.
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: