CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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, an SDK-gated RevenueCat feature not working, or RevenueCat is broken on iOS, Android, Kotlin Multiplatform, Flutter, or React Native. Also use when asked to check or validate the store / product setup.

73

Quality

92%

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

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.

The body is an exemplary diagnostic workflow — ordered, prioritized, verification-driven, and packed with concrete, executable RevenueCat specifics. Its one structural flaw is progressive disclosure: the five referenced platform files are missing from the bundle, and substantial reference material is inlined rather than split out, so the carefully designed file split is not actually delivered.

Suggestions

Include the five referenced platform files (platforms/ios.md, platforms/android.md, platforms/kmp.md, platforms/flutter.md, platforms/react-native.md) in the bundle — the workflow currently dead-ends at 'read platforms/X.md' steps with no file to read.

Move the inline reference material (SDK error-code tables, known platform issues, and per-platform configuration checklists) into the corresponding platform files or a references/ file so SKILL.md remains a lean overview.

Deduplicate facts repeated across sections: the debug-logging setup in checklist item 1 vs. the 'debug log interpretation' reference section, the 'product_id:base_plan_id' format in Check 2 vs. the Android checklist, and the INVALID_CREDENTIALS explanation in checklist item 2 vs. the error-code table.

DimensionReasoningScore

Conciseness

The body is dense with RevenueCat-specific facts Claude cannot reliably know (API key prefixes, list-offerings pagination limits, iOS 18.x StoreKit bugs, Play testing-track requirements) with no generic concept explanations, but several facts are duplicated across sections — debug-logging setup appears in checklist item 1 and the 'debug log interpretation' reference, the 'product_id:base_plan_id' format appears in Check 2 and the Android checklist, and INVALID_CREDENTIALS is explained twice — leaving minor trimmable redundancy.

4 / 5

Actionability

Guidance is fully executable: named MCP tools with exact parameters ('list-offerings' with 'limit: 100' and 'expand=items.package.product'), rc CLI command mappings, copy-paste Swift/Kotlin snippets for cache-busting getCustomerInfo, exact logLevel settings, specific error codes, and precise settings paths for sandbox accounts.

5 / 5

Workflow Clarity

A clearly sequenced five-stage workflow (detect platform → nine-item ordered checklist → three-phase dashboard inspection → platform specifics → verify the fix) with explicit prioritization ('Most reports are resolved by steps 1 through 5'), a dedicated verification section with three checkpoints, a feedback loop (request full debug logs if reproduction fails), and user confirmation before executing fixes.

5 / 5

Progressive Disclosure

The body instructs 'read platforms/ios.md' (and android, kmp, flutter, react-native) at multiple points, but none of these files exist in the bundle — no platforms/, references/, scripts/, or assets/ directories are present — so navigation dead-ends exactly where the skill delegates detail, and ~100 lines of reference tables (error codes, known platform issues, per-platform checklists) remain inlined in SKILL.md.

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 description that clearly states what the skill does and when to use it, with an unusually comprehensive set of natural-language trigger phrases covering all supported platforms. The only weakness is the slightly vague 'covers code-side gotchas' phrase alongside otherwise concrete actions.

DimensionReasoningScore

Specificity

The description lists several concrete actions — 'inspects dashboard configuration through the RevenueCat MCP, walks the SDK debug logs' — but 'covers code-side gotchas' is vaguer, leaving a minor gap in coverage that fits anchor 4 rather than a fully comprehensive 5.

4 / 5

Completeness

It 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, matching the top anchor.

5 / 5

Trigger Term Quality

Trigger phrases like 'offerings are empty', 'paywall won't load', 'entitlement not active after purchase', 'sandbox purchase not working' are exactly what affected users naturally say, and coverage spans iOS, Android, Kotlin Multiplatform, Flutter, and React Native — comprehensive including synonyms.

5 / 5

Distinctiveness Conflict Risk

The description is tightly scoped to RevenueCat with niche-specific symptom triggers and platform names, creating a clear trigger footprint with minimal conflict risk against non-RevenueCat 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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

RevenueCat/ai-toolkit

Path

revenuecat/skills/revenuecat-troubleshoot/SKILL.md

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.