CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

71

Quality

86%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

77%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-structured, highly actionable troubleshooting skill with a clear validated workflow and rich domain specifics. Its main weakness is progressive disclosure: several referenced platform files are absent from the bundle and large reference sections are inlined rather than split out.

Suggestions

Provide the referenced platforms/{ios,android,kmp,flutter,react-native}.md files in the bundle (e.g. under ./references/) so the one-level-deep navigation actually resolves.

Move the 'Reference: SDK error codes', 'Reference: known platform issues', and 'Reference: platform configuration checklists' sections into a separate reference file (e.g. references/error-codes.md) and link to it from SKILL.md to reduce inlined bulk.

Confirm the cross-skill reference to the 'revenuecat-store-state' skill is intentional and that the skill is available, since it is invoked for store-state changes.

DimensionReasoningScore

Conciseness

Dense with domain-specific, non-obvious knowledge (specific MCP tool names, iOS-version bugs, error-code tables) rather than concepts Claude already knows; minor trimming possible in the diagnostic-report template and some advisory checklist items, but most tokens earn their place.

4 / 5

Actionability

Highly executable guidance throughout — named MCP tools with parameters (e.g. list-offerings with expand=items.package.product), exact logLevel settings, settings paths, and code snippets — with minor gaps where some checklist steps are advisory rather than runnable commands.

4 / 5

Workflow Clarity

Clearly sequenced five-phase workflow (detect platform → universal checklist → dashboard inspection Phase A/B/C with [ ] checklists → platform specifics → verify the fix) with explicit validation in Section 5 and a user-confirmation gate before dashboard mutations, satisfying the destructive-operation feedback-loop requirement.

5 / 5

Progressive Disclosure

Platform-specific content is appropriately deferred to one-level-deep references (platforms/ios.md etc.) and clearly signaled, but those files are not present in the provided bundle and substantial reference material (error-code tables, known issues, configuration checklists) is inlined in SKILL.md rather than split into separate files.

3 / 5

Total

16

/

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, specific description with comprehensive natural trigger phrases covering both symptom language and platform names. It clearly states what the skill does and when to use it with minimal conflict risk.

DimensionReasoningScore

Specificity

Lists several concrete actions — 'inspects dashboard configuration through the RevenueCat MCP', 'walks the SDK debug logs', 'covers code-side gotchas' — but 'covers code-side gotchas' is slightly less concrete than the rest, leaving minor coverage gaps rather than full comprehensiveness.

4 / 5

Completeness

Explicitly answers both 'what' ('Diagnose and resolve RevenueCat integration issues — inspects dashboard configuration... walks the SDK debug logs') and 'when' ('Use when the user says offerings are empty...') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Comprehensive natural-language triggers users would actually say — 'offerings are empty', 'products not loading', 'entitlement not active after purchase', 'paywall won't load', 'sandbox purchase not working' — plus platform synonyms (iOS, Android, Kotlin Multiplatform, Flutter, React Native).

5 / 5

Distinctiveness Conflict Risk

RevenueCat-specific niche with distinct, product-namespaced triggers (RevenueCat MCP, SDK debug logs, entitlement/paywall/offerings) that minimize overlap with other skills.

5 / 5

Total

19

/

20

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.