revenuecat-migrate
Migrate to RevenueCat from raw StoreKit or Google Play Billing, or upgrade the RevenueCat SDK across a major version. Use when the user says migrate to RevenueCat, switch from StoreKit to RC, upgrade RevenueCat SDK, from v4 to v5, observer mode, RevenueCat major version upgrade, or already have in app purchases and want to add RevenueCat on iOS, Android, Kotlin Multiplatform, Flutter, or React Native.
68
81%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Advisory
Suggest reviewing before use
Quality
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is an excellent skill description that clearly defines a narrow, specific domain (RevenueCat migration and SDK upgrades), provides comprehensive trigger terms covering multiple user phrasings and platforms, and explicitly separates the 'what' from the 'when'. The description is well-structured, concise, and uses proper third-person voice throughout.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: migrate to RevenueCat from raw StoreKit or Google Play Billing, upgrade the RevenueCat SDK across a major version. These are clear, actionable capabilities. | 3 / 3 |
Completeness | Clearly answers both 'what' (migrate to RevenueCat from raw StoreKit/Google Play Billing, upgrade SDK across major versions) and 'when' with an explicit 'Use when...' clause listing numerous trigger phrases and platform contexts. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'migrate to RevenueCat', 'switch from StoreKit to RC', 'upgrade RevenueCat SDK', 'from v4 to v5', 'observer mode', 'RevenueCat major version upgrade', 'in app purchases', plus platform names (iOS, Android, Kotlin Multiplatform, Flutter, React Native). | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive niche targeting RevenueCat migration and SDK upgrades specifically, with clear triggers mentioning specific SDKs (StoreKit, Google Play Billing), version numbers (v4 to v5), and the RevenueCat brand. Very unlikely to conflict with other skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
62%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill has strong workflow structure with clear sequencing, platform detection logic, and explicit verification steps. However, it defers nearly all concrete implementation to platform files that don't exist in the bundle, significantly undermining actionability. The shared concepts section is useful but could be more concise, particularly around observer mode explanation.
Suggestions
Provide the referenced platform files (platforms/ios.md, platforms/android.md, etc.) in the bundle so the skill is actually actionable end-to-end.
For Path B (version upgrade), add at least one concrete code example showing a typical breaking change pattern (e.g., old API → new API) rather than only saying 'read the CHANGELOG'.
Tighten the observer mode explanation by removing the conceptual description ('The SDK observes transactions...') and keeping only the configuration snippets and the critical constraint about not double-processing.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Generally efficient but includes some explanatory content Claude already knows (e.g., explaining what observer mode does conceptually before giving the configuration). The 'Do not double process transactions' section is useful but slightly verbose. The shared concepts section could be tighter. | 2 / 3 |
Actionability | Provides concrete configuration snippets for observer mode across platforms and specific API calls like `Purchases.logIn(existingAppUserID)`, but the actual migration implementation is deferred entirely to platform files that are not provided. The version upgrade path (Path B) gives no concrete code—just 'read the CHANGELOG and fix compile errors.' | 2 / 3 |
Workflow Clarity | Clear sequenced workflow: detect platform → identify migration path → apply shared concepts → implement per-platform → verify. The verification section (step 5) provides explicit validation checkpoints including sandbox purchase verification, entitlement state checks, and debug log removal. The 'Plan then migrate' subsection gives a clear 4-step sequence with validation. | 3 / 3 |
Progressive Disclosure | Well-structured with clear references to platform-specific files (platforms/ios.md, platforms/android.md, etc.), but no bundle files are provided, so the referenced files don't exist. The skill appropriately keeps shared concepts in the main file and defers platform specifics, but the missing bundle files mean the actual implementation guidance is entirely absent. | 2 / 3 |
Total | 9 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- RevenueCat/rc-claude-code-plugin
- Commit
407e465
- Reviewed
Table of Contents
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.