CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

rc-purchase-flow

Use this skill when implementing a RevenueCat purchase on Android. Covers awaitPurchase, PurchasesTransactionException, reading CustomerInfo entitlements to grant access, restoring purchases, and the six SDK managed steps that happen inside a single call.

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

92%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.

Excellent executable content: complete Kotlin examples with error branches, explicit rules, and a clearly phased workflow. The only issues are minor token redundancy from the duplicated chapter link and the exception table repeating the Phase 5 note.

DimensionReasoningScore

Conciseness

The body is lean and SDK-specific (six-step table, exception types, Poko rules) without explaining concepts Claude already knows, but has minor trims available: the chapter link appears in both Phase 1 and References, and the "Exception types at a glance" table restates the note in Phase 5. Not 5 because of this duplication; not 3 because the padding is minimal.

4 / 5

Actionability

Phases 2, 3, and 5 give copy-paste-ready Kotlin with complete error branching (userCancelled, ProductAlreadyPurchasedError, else), plus concrete rules ("Do not destructure", "entitlements[\"<id\"]?.isActive == true is the gate") and the EU pricing builder flag. Specific examples cover the common purchase and restore cases.

5 / 5

Workflow Clarity

Phases 1-5 give a clear understand -> prepare -> execute -> inspect -> restore sequence, with the entitlement check serving as an explicit post-purchase and post-restore checkpoint and catch branches providing error-recovery paths. No destructive or batch operations, so no validation cap applies.

5 / 5

Progressive Disclosure

A single-file skill with well-organized section headers, tables only where they add scanning value, and one clearly signaled one-level-deep external reference (the full chapter link). Nothing here warrants splitting into bundle files, and navigation is easy.

5 / 5

Total

19

/

20

Passed

Description

92%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 with an explicit use-when trigger, concrete API names, and a well-defined niche. The only gap is missing natural synonyms (in-app purchase, Play Billing, subscriptions) that would broaden trigger coverage.

DimensionReasoningScore

Specificity

"Covers awaitPurchase, PurchasesTransactionException, reading CustomerInfo entitlements to grant access, restoring purchases, and the six SDK managed steps" lists multiple concrete API-level actions that comprehensively cover the purchase-flow domain. Anchor 4 would require noticeable coverage gaps, but the description spans execution, error handling, entitlement gating, and restore.

5 / 5

Completeness

"Use this skill when implementing a RevenueCat purchase on Android" explicitly answers when with a concrete trigger phrase, and the "Covers ..." list explicitly answers what with specific capabilities. Not 4, because the when-clause is explicit and specific rather than merely present.

5 / 5

Trigger Term Quality

"RevenueCat purchase on Android", "awaitPurchase", "restoring purchases", "CustomerInfo entitlements" are terms users would naturally say when needing this skill. Falls short of anchor 5 because common variations like "in-app purchase", "Google Play Billing", or "subscriptions" are absent.

4 / 5

Distinctiveness Conflict Risk

"RevenueCat purchase on Android" plus SDK-specific terms like "awaitPurchase" and "PurchasesTransactionException" carve out a clear niche with distinct triggers. Minimal conflict risk with any generic skill; no other skill would trigger on these phrases.

5 / 5

Total

19

/

20

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

metadata_field

'metadata' should map string keys to string values

Warning

Total

14

/

16

Passed

Repository

RevenueCat/ai-toolkit

Path

revenuecat-play-billing/skills/rc-purchase-flow/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.