Name: revenuecat-troubleshoot
Rating: 73.6 (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

89%

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 highly actionable, well-sequenced troubleshooting workflow with concrete MCP/CLI commands and validation checkpoints. Its main weakness is progressive disclosure: referenced platform files are missing from the bundle and substantial reference material is inlined rather than externalized.

Suggestions

Bundle the referenced platforms/*.md files (ios, android, kmp, flutter, react-native) so the detection step's 'read platforms/<x>.md' instructions resolve to real files.

Move the inline reference tables (SDK error codes, known platform issues, platform configuration checklists, common issues) into separate reference files (e.g., references/error-codes.md, references/known-issues.md) linked from SKILL.md to reduce the main file's length.

Trim conversational filler such as 'The SDK narrates what it is doing.' and 'Work them in order.' to tighten the already-dense body.

Dimension	Reasoning	Score
Conciseness	Dense with RevenueCat-specific detail (error codes, MCP tool names, dashboard paths) with no basic-concept padding, but a few filler lines ('The SDK narrates what it is doing.', 'Work them in order.') could be trimmed.	4 / 5
Actionability	Fully executable guidance throughout: named MCP tools with parameters (list-offerings with expand=items.package.product), rc CLI equivalents, copy-paste logLevel and getCustomerInfo snippets, exact dashboard navigation paths, and a concrete diagnostic-report template.	5 / 5
Workflow Clarity	A clearly sequenced five-step process (detect platform → universal checklist → dashboard inspection → platform specifics → verify the fix) with explicit validation checkpoints in section 5, checklists, and confirm-before-execute on fix operations.	5 / 5
Progressive Disclosure	References to platform files (platforms/ios.md, etc.) are well-signaled and one level deep, but those files are absent from the bundle, and large reference tables (error codes, known issues, platform checklists) are inlined in SKILL.md rather than split out.	3 / 5
	Total	17 / 20 Passed

Description

95%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 clearly states what it does and when to use it, with an unusually thorough list of natural trigger phrases and platforms. The only soft spot is the mildly generic 'covers code-side gotchas' action.

Dimension	Reasoning	Score
Specificity	Lists several concrete actions — 'inspects dashboard configuration through the RevenueCat MCP', 'walks the SDK debug logs' — but the third, 'covers code-side gotchas', is comparatively generic, leaving a minor coverage gap versus a 5.	4 / 5
Completeness	Explicitly answers both 'what' (diagnose and resolve via MCP dashboard inspection, SDK debug logs, and code-side gotchas) and 'when' with a concrete 'Use when the user says…' clause listing trigger phrases.	5 / 5
Trigger Term Quality	Comprehensive natural trigger phrases users would actually say ('offerings are empty', 'paywall won't load', 'sandbox purchase not working') plus platform synonyms (iOS, Android, Kotlin Multiplatform, Flutter, React Native).	5 / 5
Distinctiveness Conflict Risk	Occupies a clear niche (RevenueCat integration troubleshooting) with distinct, product-specific triggers, making conflict with other skills minimal.	5 / 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/revenuecat-troubleshoot/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.