← RevenueCatCONTENT HISTORY

Update to RevenueCat

Snapshot Sep 30, 2026 · 23:10 UTC · version 2.3.0

Collection source: not recorded for this historical snapshot.

WHAT CHANGED · RULE-BASED ANALYSIS

First saved snapshot

No earlier snapshot is available to establish a change.

Compare saved observations

Download comparison JSON
Full technical diff · 0 changed fields
Full snapshot data
{
  "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.",
  "included_files": [],
  "skill_md_contents": "---\nname: revenuecat-sdk-compatibility\ndescription: 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.\n---\n\n# RevenueCat SDK compatibility\n\nUse the RevenueCat MCP server for all tool calls here.\n\n## Check feature compatibility\n\nCall `list-sdk-feature-gates` before making any SDK compatibility claim. Find the gate that matches\nthe user's feature and use its minimum version for each relevant RevenueCat SDK.\n\n- If the relevant feature gate cannot be identified, say so and explain which gates looked close\n  instead of guessing. Consult the docs linked in the tool output to disambiguate.\n- When more than one gate could apply, prefer the most specific gate. For example:\n  - Existing-customer experiment enrollment: `experiment-existing-customer-enrollment`\n  - Experiment exposure status or reporting: `experiment-exposure-tracking`\n  - New-customer experiment enrollment: `experiment-new-customer-enrollment`\n- If multiple gates jointly matter, evaluate and name each one.\n\n## Analyze SDK adoption\n\nCall `list-sdk-versions` to assess upgrade impact or rollout risk from SDK versions observed in the\nproject. Each row describes subscribers seen in the last 30 days and includes:\n\n- `sdk_type`: RevenueCat SDK family.\n- `sdk_version`: underlying native SDK version for native rows, or the native SDK bundled under a\n  wrapper in `platform_flavor` rows.\n- `sortable_sdk_version`: normalized value for ordering `sdk_version`.\n- `platform`: native platform, such as `ios` or `android`, when grouped by platform or platform\n  flavor.\n- `platform_flavor` and `platform_flavor_version`: wrapper SDK family and version, such as\n  `react-native` `10.0.1`, when grouped by platform flavor.\n- `subscribers_last_30days` and `pct_of_subscribers`: recent project usage counts and shares.\n\nChoose the grouping that matches the question:\n\n- Use `sdk_type` for a high-level inventory by RevenueCat SDK family.\n- Use `platform` to compare native iOS and Android adoption.\n- Use `platform_flavor` for React Native, Flutter, Capacitor, Unity, Kotlin Multiplatform, and other\n  wrappers where both the wrapper version and bundled native SDK versions matter.\n\nTo compute upgrade impact, filter to the relevant SDK family, compare observed versions with the\nfeature gate's `min_version`, and sum `subscribers_last_30days` and `pct_of_subscribers` for rows\nbelow the requirement. State that these figures represent subscribers observed in the last 30 days,\nnot the all-time install base.\n\nUse `jq` for quick filtering or a code execution tool for version comparisons, grouping, and\nsubscriber-share calculations when the output is too large to analyze reliably by inspection.\n"
}

SHA-256: 00a4a1fc81f89ea4e8c2a23d1c152128baef9cdaaec365b9507c877855d60aa1