revenuecat-purchase-flow
Implement the RevenueCat purchase and restore flow. Use when the user asks to buy a package, purchase a subscription, fetch offerings, build paywall purchase logic, handle purchase errors, detect user cancelled, or restore previous purchases on iOS, Android, Kotlin Multiplatform, Flutter, or React Native.
72
88%
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 a strong skill description that clearly identifies the specific SDK (RevenueCat), lists concrete actions (purchase, restore, fetch offerings, handle errors), and includes an explicit 'Use when...' clause with natural trigger terms across multiple platforms. It is concise, uses third-person voice, and would be easily distinguishable from other skills in a large skill library.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'buy a package', 'purchase a subscription', 'fetch offerings', 'build paywall purchase logic', 'handle purchase errors', 'detect user cancelled', 'restore previous purchases'. These are all concrete, actionable capabilities. | 3 / 3 |
Completeness | Clearly answers both 'what' (implement RevenueCat purchase and restore flow) and 'when' with an explicit 'Use when...' clause listing specific trigger scenarios. Both dimensions are well-covered. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'buy a package', 'purchase a subscription', 'fetch offerings', 'paywall', 'purchase errors', 'user cancelled', 'restore previous purchases', 'RevenueCat', plus platform names (iOS, Android, Flutter, React Native, Kotlin Multiplatform). These are all terms a developer would naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive due to the specific mention of 'RevenueCat' as the SDK, combined with purchase/subscription-specific terminology and platform targets. Unlikely to conflict with generic payment or billing skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured skill with excellent workflow clarity and conciseness. The shared concepts section is particularly strong, encoding platform-specific nuances (cancellation handling) and critical anti-patterns (don't unlock in callback) that Claude wouldn't know. The main weakness is that all executable implementation is deferred to platform files that aren't present in the bundle, making the skill incomplete as a standalone artifact.
Suggestions
Provide the referenced platform files (platforms/ios.md, platforms/android.md, etc.) in the bundle so the progressive disclosure structure is functional and Claude has access to the executable code.
Consider adding at least one inline code example (e.g., a minimal purchase flow for the most common platform) so the skill has some actionable code even without the platform files.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient. It avoids explaining what RevenueCat is, what purchases are, or how SDKs work in general. Every section delivers information Claude wouldn't already know—platform detection heuristics, SDK-specific cancellation patterns, and the critical 'do not unlock content in the purchase callback' rule. No wasted tokens. | 3 / 3 |
Actionability | The skill provides concrete platform detection logic and clear behavioral rules (e.g., how to handle cancellation per platform), but the actual implementation code is deferred entirely to platform files which are not provided in the bundle. Without those files, Claude has no executable code to work from—just descriptions of what to do. | 2 / 3 |
Workflow Clarity | The workflow is clearly sequenced: detect platform → understand shared concepts → read platform-specific implementation → verify. The verification section (Step 4) provides explicit validation checkpoints covering success, cancellation, duplicate purchase, and restore scenarios. The feedback loop of 'do not claim it works until these 4 conditions pass' is strong. | 3 / 3 |
Progressive Disclosure | The skill correctly references five platform-specific files and two related skills (revenuecat-paywall, revenuecat-entitlements-gate), with clear one-level-deep navigation. However, no bundle files were provided, meaning the referenced platform files (platforms/ios.md, etc.) don't actually exist in the evaluated bundle, which undermines the progressive disclosure structure in practice. | 2 / 3 |
Total | 10 / 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.