Name: revenuecat-purchase-flow
Rating: 77.60000000000001 (1 reviews)
Author: RevenueCat

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.

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Advisory

Suggest reviewing before use

Quality

Content

92%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A lean, actionable skill body with a well-sequenced workflow and an explicit verification checklist. Its main defect is that the per-platform files it tells the reader to load are not bundled, so the progressive-disclosure pointers dangle.

Suggestions

Bundle the referenced platform files (platforms/ios.md, platforms/android.md, platforms/kmp.md, platforms/flutter.md, platforms/react-native.md) so the "read the platform file" instructions in Sections 1 and 3 resolve.

Verify each bundled platform file actually contains the complete purchase and restore functions promised in Section 3, matching the shared concepts in Section 2.

Consider adding a brief fallback note or minimal inline guidance for the case where a detected platform's file is missing, so the flow is still usable when a reference cannot be loaded.

Dimension	Reasoning	Score
Conciseness	The body is lean, assumes Claude's competence (no explanation of what RevenueCat or a subscription is), and every bullet earns its place — the per-platform cancellation codes are non-obvious detail Claude would not reliably recall.	3 / 3
Actionability	Provides concrete, executable guidance: detection rules tied to real files (package.json, pubspec.yaml, build.gradle.kts), real API calls (getOfferings(), purchase(package), restorePurchases()), and real per-platform error codes rather than vague direction or pseudocode.	3 / 3
Workflow Clarity	A clear four-step sequence (Detect platform → Shared concepts → Implementation → Verify) with an explicit verification checklist of four checkpoints covering success, cancellation, duplicate purchase, and restore on a fresh install.	3 / 3
Progressive Disclosure	The overview is well-organized and signals one-level-deep references to platforms/ios.md, android.md, kmp.md, flutter.md, and react-native.md, but none of those referenced files exist in the bundle (no platforms/, references/, scripts/, or assets/ directories are present), so navigation to the detailed content is broken.	2 / 3
	Total	11 / 12 Passed

Description

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.

A strong, specific description that clearly states both the capability and the trigger conditions with natural user-facing language. It is distinguishable from sibling RevenueCat skills and avoids vague fluff.

Dimension	Reasoning	Score
Specificity	Lists many concrete actions — "buy a package, purchase a subscription, fetch offerings, build paywall purchase logic, handle purchase errors, detect user cancelled, or restore previous purchases" — matching the anchor for multiple specific concrete actions.	3 / 3
Completeness	Explicitly states what it does ("Implement the RevenueCat purchase and restore flow") and when to use it ("Use when the user asks to..."), answering both what and when with explicit triggers.	3 / 3
Trigger Term Quality	Phrases like "buy a package", "purchase a subscription", "handle purchase errors", and "restore previous purchases" are natural terms a user would actually say, giving good coverage.	3 / 3
Distinctiveness Conflict Risk	Scoped specifically to purchase/restore actions across named platforms with distinct purchase-oriented triggers, and the body disambiguates it from sibling paywall and entitlements skills, giving it a clear niche.	3 / 3
	Total	12 / 12 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: RevenueCat/rc-claude-code-plugin
Commit: 5cb348c

Reviewed: 4 days ago

Table of Contents

Discovery Implementation Validation

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.