Name: revenuecat-troubleshoot
Rating: 72.8 (1 reviews)
Author: RevenueCat

revenuecat-troubleshoot

Diagnose and resolve RevenueCat integration issues — inspects dashboard configuration through the RevenueCat MCP, walks the SDK debug logs, and covers code-side gotchas. Use when the user says offerings are empty, products not loading, entitlement not active after purchase, paywall won't load, transactions not appearing, customer info shows no entitlements, sandbox purchase not working, or RevenueCat is broken 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

77%

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

Actionable and well-sequenced with strong validation feedback loops, but the body is a monolithic wall of inline reference material whose referenced platform bundle files are absent from the bundle, weakening progressive disclosure and conciseness.

Suggestions

Create the referenced platforms/*.md files and move the per-platform "known issues" and configuration checklists out of SKILL.md into them, so the main file is a lean overview with one-level-deep references that actually resolve.

Move time-sensitive version-specific notes (iOS 18.x StoreKit daemon failures, Xcode 26 simulator issues) into a clearly labeled "Known platform issues / version-specific" section or file so they don't penalize conciseness inline.

Trim redundancy between the §2 universal checklist and the §"common issues" reference so each symptom is documented in one place.

Dimension	Reasoning	Score
Conciseness	Mostly domain-specific and valuable, but the body is a long 250+ line monolith with redundancy between the universal checklist and the "common issues" reference, and time-sensitive version numbers ("iOS 18.0–18.3.2", "Xcode 26+") sit inline rather than in a deprecated section — the guideline penalizes conciseness for that.	2 / 3
Actionability	Fully concrete guidance: named MCP tools with parameters ("list-offerings" with "expand=items.package.product"), API key formats ("appl_…", "goog_…"), executable log snippets, and a copy-paste diagnostic report template.	3 / 3
Workflow Clarity	Clear ordered sequence (sections 1–5, nine-item checklist "in order", Phase A/B/C dashboard inspection) with explicit validation checkpoints — "Do not declare the issue fixed until" the log, dashboard, and reproduction steps all pass.	3 / 3
Progressive Disclosure	Platform references ("platforms/ios.md" etc.) are well-signaled and one-level-deep, but those files do not exist in the bundle, and large reference blocks (error codes, known platform issues, config checklists) remain inline in SKILL.md rather than being split out — content that should be separate is inline.	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 highly specific, third-person description with explicit triggers and a clear niche. It answers both what and when without verbosity or fluff.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — "inspects dashboard configuration through the RevenueCat MCP", "walks the SDK debug logs", and "covers code-side gotchas" — matching the anchor for listing several specific concrete actions.	3 / 3
Completeness	Clearly answers what ("Diagnose and resolve RevenueCat integration issues") and when with an explicit "Use when the user says..." clause enumerating concrete triggers — both what and when are explicit.	3 / 3
Trigger Term Quality	Strong coverage of natural phrases users would say: "offerings are empty", "products not loading", "entitlement not active after purchase", "paywall won't load", plus named platforms (iOS, Android, Flutter, React Native, KMP).	3 / 3
Distinctiveness Conflict Risk	The RevenueCat-specific niche with platform-listed triggers is clearly distinct and unlikely to fire for unrelated skills.	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.