Skip to main content
skill CX Codex

revenuecat-sdk-compatibility — Claude Code skill: SDK versions

This skill checks whether a RevenueCat SDK version supports a feature and how many subscribers are stuck on older versions.

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add RevenueCat/ai-toolkit --skill revenuecat-sdk-compatibility -a claude-code
Open on GitHub

What revenuecat-sdk-compatibility does

The skill answers RevenueCat SDK compatibility questions: does this version include the feature, is an upgrade needed, why is a gated feature failing. It runs on the RevenueCat MCP server, so nothing works without that server connected.

Before making any compatibility claim it calls list-sdk-feature-gates and takes the minimum version from the matching gate. If no gate fits, it says so and lists the close ones instead of guessing. When several gates apply, the most specific wins: experiment-existing-customer-enrollment for enrolling existing customers, experiment-exposure-tracking for exposure status.

The second tool, list-sdk-versions, breaks down subscribers seen in the last 30 days by SDK family, platform, or wrapper such as react-native 10.0.1. To size rollout risk, the skill filters rows below min_version and sums their shares. Those numbers cover a 30-day window, not the all-time install base, and that gap matters when you plan a migration.

What it helps with

  • find the minimum SDK version for a feature
  • debug why a gated feature is not working
  • measure the share of subscribers on incompatible SDK versions
  • estimate how many users an SDK upgrade affects
  • compare native iOS and Android adoption

Example prompts for the agent

  • Check which RevenueCat SDK version first supports enrolling new customers in an experiment
  • How many subscribers in the last 30 days are below the minimum for experiment-exposure-tracking?
  • Break adoption down by platform_flavor and show the React Native share on old versions

How to install revenuecat-sdk-compatibility

1Skills CLI (Vercel)

npx skills add RevenueCat/ai-toolkit --skill revenuecat-sdk-compatibility -a claude-code

2Manually: put the files in place

~/.claude/skills/revenuecat-sdk-compatibility/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/revenuecat-sdk-compatibility/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about revenuecat-sdk-compatibility

How do I install revenuecat-sdk-compatibility in Claude?

Run npx skills add RevenueCat/ai-toolkit --skill revenuecat-sdk-compatibility -a claude-code. The skill lands at ~/.claude/skills/revenuecat-sdk-compatibility/SKILL.md.

What does revenuecat-sdk-compatibility do?

It checks whether a RevenueCat SDK version supports a feature, resolves minimum versions from feature gates, and counts subscribers on older versions.

What does the skill need to run?

The RevenueCat MCP server. Every tool call goes through it, so without the server the skill cannot fetch gates or SDK versions.

Source text

SKILL.md · MIT
---
name: revenuecat-sdk-compatibility
description: Check whether an SDK version supports a RevenueCat feature, whether an SDK upgrade is required, why an SDK-gated feature is not working, or how much of a project's recent subscriber base is on incompatible SDK versions. Use for questions about RevenueCat SDK compatibility, feature gates, minimum SDK versions, SDK adoption, upgrade impact, and rollout risk.
---

# RevenueCat SDK compatibility

Use the RevenueCat MCP server for all tool calls here.

## Check feature compatibility

Call `list-sdk-feature-gates` before making any SDK compatibility claim. Find the gate that matches
the user's feature and use its minimum version for each relevant RevenueCat SDK.

- If the relevant feature gate cannot be identified, say so and explain which gates looked close
  instead of guessing. Consult the docs linked in the tool output to disambiguate.
- When more than one gate could apply, prefer the most specific gate. For example:
  - Existing-customer experiment enrollment: `experiment-existing-customer-enrollment`
  - Experiment exposure status or reporting: `experiment-exposure-tracking`
  - New-customer experiment enrollment: `experiment-new-customer-enrollment`
- If multiple gates jointly matter, evaluate and name each one.

## Analyze SDK adoption

Call `list-sdk-versions` to assess upgrade impact or rollout risk from SDK versions observed in the
project. Each row describes subscribers seen in the last 30 days and includes:

- `sdk_type`: RevenueCat SDK family.
- `sdk_version`: underlying native SDK version for native rows, or the native SDK bundled under a
  wrapper in `platform_flavor` rows.
- `sortable_sdk_version`: normalized value for ordering `sdk_version`.
- `platform`: native platform, such as `ios` or `android`, when grouped by platform or platform
  flavor.
- `platform_flavor` and `platform_flavor_version`: wrapper SDK family and version, such as
  `react-native` `10.0.1`, when grouped by platform flavor.
- `subscribers_last_30days` and `pct_of_subscribers`: recent project usage counts and shares.

Choose the grouping that matches the question:

- Use `sdk_type` for a high-level inventory by RevenueCat SDK family.
- Use `platform` to compare native iOS and Android adoption.
- Use `platform_flavor` for React Native, Flutter, Capacitor, Unity, Kotlin Multiplatform, and other
  wrappers where both the wrapper version and bundled native SDK versions matter.

To compute upgrade impact, filter to the relevant SDK family, compare observed versions with the
feature gate's `min_version`, and sum `subscribers_last_30days` and `pct_of_subscribers` for rows
below the requirement. State that these figures represent subscribers observed in the last 30 days,
not the all-time install base.

Use `jq` for quick filtering or a code execution tool for version comparisons, grouping, and
subscriber-share calculations when the output is too large to analyze reliably by inspection.

© RevenueCat · MIT · RevenueCat/ai-toolkit

Similar skills

Everything for Mobile →

From the same set25

Project sponsors

Companies that keep this analytics open
Gold sponsor

Impressions, clicks and code copies — open statistics. We keep the numbers public for the same reason NeBlask itself is public. Become a sponsor