Name: integrate-revenuecat
Rating: 73.6 (1 reviews)
Author: RevenueCat

integrate-revenuecat

End-to-end RevenueCat integration — sets up the dashboard side via the RevenueCat MCP or the `rc` CLI (project, app, public API key) and installs/configures the Purchases SDK in the app. Use when the user asks to add RevenueCat, integrate Purchases, install the RevenueCat SDK, set up a RevenueCat API key, configure Purchases on launch, or set up a brand new RevenueCat integration on iOS, Android, Kotlin Multiplatform, Flutter, or React Native.

Quality

90%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

85%Weight 40%Scale 1-5

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

A well-sequenced, highly actionable integration workflow with strong validation checkpoints. Its main weakness is progressive disclosure: Section 3c delegates the actual SDK install/configure code to five `platforms/*.md` files that are not present in the bundle.

Suggestions

Add the missing `platforms/ios.md`, `platforms/android.md`, `platforms/kmp.md`, `platforms/flutter.md`, and `platforms/react-native.md` files to the references bundle — the body's actionability currently depends on content that isn't shipped.

Tighten conversational asides such as 'Reassure them that store-side setup can come later' to reduce token overhead without losing the useful guidance.

Disambiguate the 'set up a brand new RevenueCat integration' trigger in the description so it does not collide with the `create-revenuecat-project` skill.

Dimension	Reasoning	Score
Conciseness	The body is well-organized and assumes Claude's competence without explaining what RevenueCat is, but a few asides like 'Reassure them that store-side setup can come later' and redundant reassurance text could be trimmed.	4 / 5
Actionability	Concrete, executable guidance throughout — exact commands (`rc projects list`, `rc apps create`), MCP tool names, specific field values (`type: "app_store"`, `bundle_id`), and a precise file-based platform detection algorithm.	5 / 5
Workflow Clarity	Clear five-section sequence (understand → dashboard → app → verify → next steps) with an explicit validation gate in Section 4 (build, launch, confirm config banner, check for auth errors) and a feedback loop for wrong-API-key recovery.	5 / 5
Progressive Disclosure	The structure is well-signaled with one-level-deep references to per-platform files, but the referenced `platforms/ios.md`, `android.md`, `kmp.md`, `flutter.md`, and `react-native.md` files do not exist in the bundle, so the core implementation detail Claude is told to read is missing.	3 / 5
	Total	17 / 20 Passed

Description

96%Weight 40%Scale 1-5

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, third-person description that concretely states what the skill does and when to use it, with rich natural trigger terms and platform coverage. Its only weakness is minor overlap with the related project-bootstrap skill in the 'set up a brand new integration' phrasing.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions across both halves — 'sets up the dashboard side via the RevenueCat MCP or the `rc` CLI (project, app, public API key)' and 'installs/configures the Purchases SDK in the app' — giving comprehensive coverage of the integration scope.	5 / 5
Completeness	Explicitly answers both 'what' (dashboard setup + SDK install/configure) and 'when' via a clear 'Use when...' clause listing concrete trigger phrases, matching the top anchor.	5 / 5
Trigger Term Quality	Comprehensive natural trigger phrases including synonyms (RevenueCat / Purchases) and concrete user asks — 'add RevenueCat', 'integrate Purchases', 'install the RevenueCat SDK', 'set up a RevenueCat API key', 'configure Purchases on launch' — plus all five target platforms.	5 / 5
Distinctiveness Conflict Risk	The RevenueCat/Purchases niche is clear with distinct triggers, but the phrase 'set up a brand new RevenueCat integration' and the project/app setup actions overlap with the sibling `create-revenuecat-project` skill, creating minor conflict risk.	4 / 5
	Total	19 / 20 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
Path: revenuecat/skills/integrate-revenuecat/SKILL.md
Commit: b9b77b1

Reviewed: 3 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.