CtrlK
BlogDocsLog inGet started
Tessl Logo

integrate-revenuecat

End-to-end RevenueCat integration — sets up the dashboard side via the RevenueCat MCP (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.

72

Quality

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

SKILL.md
Quality
Evals
Security

Quality

Content

77%

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

A well-sequenced, concise integration workflow with strong validation checkpoints, but its core executable code and its progressive-disclosure targets both depend on `platforms/*.md` files that are not present in the bundle, leaving the two lowest dimensions incomplete.

Suggestions

Ship the missing platform detail files (platforms/ios.md, android.md, kmp.md, flutter.md, react-native.md) — or, if no bundle is intended, inline each platform's install command and the full Purchases.configure(...) snippet so the core action is executable from SKILL.md alone.

Resolve the deferred configure code: replace the `Purchases.configure(…)` ellipsis with copy-paste-ready per-platform snippets, since the referenced files currently do not exist.

Verify every referenced path (platforms/*.md and sibling skill names) resolves to a real file before relying on the disclosure structure, so Claude does not hit dead links mid-integration.

DimensionReasoningScore

Conciseness

The body is dense and operational — it never explains concepts Claude already knows (no "what is RevenueCat" padding) and contains no filler, with its length justified by two integration halves across five platforms. Every section earns its tokens.

3 / 3

Actionability

It gives concrete MCP tool names and params, exact detection markers, and build commands, but the central deliverable — the per-platform install command and `Purchases.configure(…)` snippet — appears only as an ellipsis deferred to `platforms/*.md` files, so the executable core detail is missing from the body.

2 / 3

Workflow Clarity

A clear Section 1→5 sequence with an explicit Section 4 validation gate ("Do not claim setup is complete until: builds, launches with config banner, no auth errors") and an error-recovery signal (auth error ⇒ wrong API key), matching the anchor for clear sequence with validation checkpoints.

3 / 3

Progressive Disclosure

The body is structured as a clean overview with one-level-deep, well-signaled references to `platforms/{ios,android,kmp,flutter,react-native}.md`, but none of those files exist in the bundle, so the disclosure points to dead targets rather than resolvable detail.

2 / 3

Total

10

/

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, third-person description that names concrete actions across both the dashboard and app halves, pairs them with an explicit 'Use when' trigger covering natural user phrasings, and occupies a clear non-conflicting niche. No specificity voice penalty applies.

DimensionReasoningScore

Specificity

"sets up the dashboard side via the RevenueCat MCP (project, app, public API key) and installs/configures the Purchases SDK in the app" lists multiple specific concrete actions across both halves, matching the anchor for listing several concrete actions.

3 / 3

Completeness

It explicitly answers what ("sets up the dashboard side… and installs/configures the Purchases SDK") and when ("Use when the user asks to…"), satisfying both halves with an explicit trigger clause.

3 / 3

Trigger Term Quality

"Use when the user asks to add RevenueCat, integrate Purchases, install the RevenueCat SDK, set up a RevenueCat API key, configure Purchases on launch" gives strong coverage of natural phrasings a user would actually say, plus all five platforms.

3 / 3

Distinctiveness Conflict Risk

The RevenueCat/Purchases niche is product-specific with distinct triggers ("integrate Purchases", "RevenueCat API key"), making it unlikely to fire for an unrelated skill.

3 / 3

Total

12

/

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
RevenueCat/rc-claude-code-plugin
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.