plan-changes

Automate subscription plan changes in Android apps using the RevenueCat SDK.

45|Updated Jun 2, 2026
One-click install
npx skills add https://github.com/RevenueCat/play-billing-skills --skill plan-changes-revenuecat
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plan-changes
Source: https://github.com/RevenueCat/play-billing-skills/tree/main/revenuecat/plan-changes
Command: npx skills add https://github.com/RevenueCat/play-billing-skills --skill plan-changes-revenuecat

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill simplifies implementing subscription changes in RevenueCat-managed Android apps, addressing the complexities of handling upgrades, downgrades, and plan switches, including Google replacement modes and linkedPurchaseToken chaining.

Core Features & Use Cases

  • Subscription Upgrades and Downgrades: Execute smooth transitions between different subscription plans.
  • Google Replacement Modes: Utilize various replacement modes for controlling how plan changes affect users' billing cycles.
  • LinkedPurchaseToken Chaining: Handle the complex process of managing token chains server-side, eliminating manual token management.
  • Use Case: If a user with an active subscription needs to switch to a new plan, use this Skill to process the change, ensuring a seamless transition.

Quick Start

Apply the plan-changes skill to a RevenueCat Android app to initiate an upgrade for a user to the 'premium_annual_package'.

Frequently Asked Questions about plan-changes

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I handle subscription upgrades and downgrades in Android using RevenueCat?

Subscription upgrades and downgrades in Android using RevenueCat are handled by automating plan transitions through the RevenueCat Android SDK. This incorporates Google replacement modes and linkedPurchaseToken chaining to ensure seamless billing cycle changes.

What are Google replacement modes for subscription plan changes?

Google replacement modes control how subscription plan changes affect users' billing cycles during upgrades or downgrades. They dictate the replacement behavior applied when a user switches between different subscription packages in the Android app.

How does linkedPurchaseToken chaining work for Android subscription switches?

LinkedPurchaseToken chaining automates the complex process of managing token chains server-side for Android subscription switches. This eliminates manual token management when users change plans, ensuring accurate subscription tracking across upgrades and downgrades.

Can I use this to process an immediate subscription upgrade to a different package?

Yes, you can process an immediate subscription upgrade by applying the plan-changes logic to a RevenueCat Android app. It initiates the transition to a target package like 'premium_annual_package' automatically, handling the underlying token chaining.

Do I need to manually manage purchase tokens when users switch subscription plans?

No, you do not need to manually manage purchase tokens when users switch subscription plans. The Skill automates linkedPurchaseToken chaining server-side, eliminating manual token management for Android downgrades and upgrades.