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.

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

88%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 a highly actionable, well-sequenced diagnostic workflow: platform detection, an ordered nine-item checklist with specific MCP tool calls and parameters, phased dashboard checks with checkbox lists, and an explicit verify-the-fix section with feedback loops. Conciseness and progressive disclosure are good but not excellent — around 100 lines of reference tables are inlined that could live in separate files, and a few 'common issues' entries restate checklist content.

Suggestions

Move the trailing 'Reference:' sections (SDK error codes, known platform issues, platform configuration checklists) into separate files such as references/error-codes.md and references/known-issues.md, keeping only the highest-frequency entries inline so SKILL.md remains a workflow overview.

Trim the 'Reference: common issues' section — entries like 'Offering returns empty' and 'User purchased but has no entitlement' restate universal checklist steps 3–5 and the Phase B checks.

Consolidate the repeated pacing guidance ('Work them in order. Most reports resolve before you reach the platform specifics.' and 'Most reports are resolved by steps 1 through 5') into a single statement.

DimensionReasoningScore

Conciseness

The body is dense with RevenueCat-specific knowledge Claude would not have (MCP tool parameters, iOS 18 StoreKit bugs, exact sandbox-account settings paths) and never explains generic concepts, so it is largely efficient. Minor trimming is possible: 'Reference: common issues' entries like 'Offering returns empty — Verify a current offering exists, packages have products attached' restate checklist steps 3–5, and the pacing note ('Most reports resolve before you reach the platform specifics' / 'Most reports are resolved by steps 1 through 5') appears twice — anchor 4, not 5.

4 / 5

Actionability

Fully executable throughout: named MCP tools with parameters ('list-offerings … passing limit: 100 and expand=items.package.product'), CLI mappings ('list-offerings → rc offerings list'), runnable snippets ('Purchases.shared.getCustomerInfo(fetchPolicy: .fetchCurrent)'), and exact settings paths ('Settings → Developer → Sandbox Apple Account on iOS 18 and later'). Copy-paste-ready guidance covers the common cases, matching anchor 5.

5 / 5

Workflow Clarity

Clear five-stage sequence (detect platform → ordered nine-item checklist → phased dashboard checks → platform specifics → verify) with explicit ordering ('Walk these nine items in order'), checkbox checklists in Phase B, and a dedicated validation section: 'Do not declare the issue fixed until: 1. The log … shows the expected success line … 2. The dashboard reflects the change … 3. The reproduction steps … now pass', plus error recovery ('If the user cannot reproduce locally, have them send the full debug log'). Matches anchor 5; the destructive-operation cap does not apply because fixes require user confirmation ('confirm with the user, then execute via MCP') and are verified in section 5.

5 / 5

Progressive Disclosure

Platform specifics are correctly split into clearly signaled, one-level-deep files ('Read the platform file that matches detection … platforms/ios.md' … 'platforms/react-native.md'), and related skills are referenced by name. However, roughly 100 lines of trailing 'Reference:' sections (SDK error-code tables, known platform issues, platform configuration checklists) are inlined in SKILL.md when they could be separate reference files, and the iOS/Android configuration checklists overlap with the platform-file layer — anchor 4's 'minor organization gaps', short of anchor 5's fully split content; better than anchor 3 because references are clearly signaled and the workflow overview is appropriately placed. No bundle files were provided, so the referenced platforms/*.md files could not be verified against the bundle.

4 / 5

Total

18

/

20

Passed

Description

91%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: it names concrete capabilities (dashboard inspection via the RevenueCat MCP, walking SDK debug logs) and provides an exhaustive list of natural-language trigger phrases covering every common symptom and all five supported platforms. The only weaknesses are the generic 'covers code-side gotchas' phrase and the unqualified trailing store-setup trigger, which create minor specificity and overlap gaps.

DimensionReasoningScore

Specificity

Names several concrete actions — 'inspects dashboard configuration through the RevenueCat MCP', 'walks the SDK debug logs' — but the third capability, 'covers code-side gotchas', is generic, leaving minor gaps in coverage (anchor 4) rather than the comprehensive action list of anchor 5. It exceeds anchor 3 because more than 1-2 concrete actions are explicitly named.

4 / 5

Completeness

Explicitly answers both questions: 'Diagnose and resolve RevenueCat integration issues — inspects dashboard configuration … walks the SDK debug logs' states what it does, and 'Use when the user says offerings are empty, products not loading …' gives concrete when-triggers. This matches anchor 5 exactly; a 4 would require the 'when' clause to be less explicit or specific.

5 / 5

Trigger Term Quality

The trigger list is exhaustive in natural user phrasing: 'offerings are empty', 'products not loading', 'entitlement not active after purchase', 'paywall won't load', 'transactions not appearing', 'sandbox purchase not working', plus platform names 'iOS, Android, Kotlin Multiplatform, Flutter, or React Native'. These are exactly the phrases a developer would say, matching anchor 5's comprehensive synonym coverage; nothing common is missing.

5 / 5

Distinctiveness Conflict Risk

The niche is unmistakable (RevenueCat integration troubleshooting) and nearly all triggers are product-specific, but the trailing 'Also use when asked to check or validate the store / product setup' is not qualified by RevenueCat and could overlap with closely related store-setup skills — anchor 4's 'minor overlap risk'. Not 5 because of that unscoped clause; not 3 since the description would not trigger for unrelated skills.

4 / 5

Total

18

/

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.