CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

rc-understanding-revenuecat

Use this skill to orient an agent to the RevenueCat Android SDK (10.x) architecture. Covers how RevenueCat reorganizes BillingClient, Google Play Developer API, and RTDN into a single SDK, and how Products, Packages, Offerings, Entitlements, and CustomerInfo connect.

Quality

80%

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

Fix and improve this skill with Tessl

tessl review fix ./revenuecat-play-billing/skills/rc-understanding-revenuecat/SKILL.md
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 content is a strong orientation skill: tight tables, executable Kotlin for the common reads and configuration, an explicit validation checklist with a feedback loop, and a concrete routing table to downstream skills. The only notable improvements are minor trims (Phase 0 trigger criteria, the call-path diagram) and moving enumerated detail like the eight subscription states into the downstream skill or a reference file.

DimensionReasoningScore

Conciseness

The body is dense and table-driven with executable snippets and no padding of concepts Claude already knows; the mapping tables ('Raw Google Play stack | RevenueCat replacement') add only RevenueCat-specific knowledge. It is not 5 because Phase 0's start/skip criteria partially duplicate trigger guidance that belongs in the description, the call-path diagram repeats the table's row content, and the enumeration of the eight Play subscription states could be deferred to the rc-subscription-states skill. It is above 3 because the potentially-trimmable material is minor.

4 / 5

Actionability

Copy-paste-ready Kotlin covers the two most common reads ('Purchases.sharedInstance.awaitOfferings()', 'awaitCustomerInfo()' with 'entitlements["pro_access"]?.isActive == true') and startup configuration via the real 'PurchasesConfiguration.Builder(context, "your_api_key")' API, and the Phase 2 routing table gives a concrete next skill per user goal. This matches anchor 5: fully executable examples covering the common cases.

5 / 5

Workflow Clarity

The phases (Intent -> Orient -> Map -> Sanity check) form a clear sequence, and Phase 3 is an explicit four-item validation checklist ('confirm out loud') with a feedback loop for error recovery ('If any of the four fail, reread Phase 1 or the chapter before proceeding'). This matches anchor 5's explicit validation steps and feedback loops; the skill involves no destructive or batch operations, so no cap applies.

5 / 5

Progressive Disclosure

No bundle files exist (references/, scripts/, assets/ are absent), so scoring rests on the body itself: sections are well-organized with a clearly signaled one-level reference ('[Full chapter](https://www.revenuecat.com/guides/...)'). It is not 5 because the body exceeds 50 lines (the simple-skill exception does not apply) and inline detail such as the eight Play subscription states and the offline-entitlements mitigation table could be split into reference files or the downstream skills. It is well above 3 since structure and signaling are good.

4 / 5

Total

18

/

20

Passed

Description

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

The description is specific and distinct, clearly scoping a niche (RevenueCat Android SDK architecture orientation) with strong domain keywords. Its main weakness is the absence of an explicit 'Use when...' trigger clause, leaving the invocation conditions only weakly implied and capping completeness. Adding concrete trigger phrases and natural synonyms like 'in-app purchases' or 'subscriptions' would raise both completeness and trigger term quality.

Suggestions

Add an explicit trigger clause, e.g. 'Use when starting a RevenueCat integration, migrating from raw Play Billing, or when Product/Package/Offering/Entitlement concepts are unclear' — this converts the purpose statement into concrete invocation conditions and lifts completeness above the cap of 3.

Include natural synonyms users actually say, such as 'in-app purchases', 'subscriptions', 'Play Billing', and 'paywall', alongside the existing SDK-specific terms.

State what the skill does not cover (e.g. 'For SDK setup, purchase flow, or entitlement gating, see the downstream rc-* skills') to sharpen the boundary with sibling RevenueCat skills and reduce conflict risk.

DimensionReasoningScore

Specificity

The description names the domain ('RevenueCat Android SDK (10.x) architecture') and several concrete coverage areas ('reorganizes BillingClient, Google Play Developer API, and RTDN into a single SDK', 'how Products, Packages, Offerings, Entitlements, and CustomerInfo connect'), matching the 'several specific actions; minor gaps' anchor. It is above anchor 3 (more than 1-2 concrete items named) but below anchor 5 because the only action verb is the generic 'orient' rather than a comprehensive list of distinct capabilities.

4 / 5

Completeness

The 'what' is clear (orients an agent to the SDK architecture and the listed concepts), but the only 'when' guidance is the purpose statement 'Use this skill to orient an agent to...', with no explicit 'Use when...' trigger clause or equivalent trigger conditions. Per the judging guideline, a missing explicit trigger clause caps completeness at 3; it is not 4 because the when-guidance is only weakly implied, not just imprecise.

3 / 5

Trigger Term Quality

Good keyword coverage of terms a RevenueCat user would naturally say: 'RevenueCat', 'Android SDK', 'BillingClient', 'Offerings', 'Entitlements', 'CustomerInfo'. It falls short of anchor 5's 'comprehensive coverage of natural terms including synonyms' because common phrases like 'in-app purchases', 'subscriptions', 'Play Billing', or 'paywall' are missing, but it is clearly above anchor 3's 'some relevant keywords'.

4 / 5

Distinctiveness Conflict Risk

'RevenueCat Android SDK (10.x)' plus proprietary concept names (Offerings, Packages, Entitlements, CustomerInfo) form a clear niche with distinct triggers. Minor overlap risk remains with closely related sibling skills (rc-setup, rc-purchase-flow, rc-subscription-states) since the description broadly names Entitlements and Offerings that those skills act on, which keeps it at anchor 4 rather than 5.

4 / 5

Total

15

/

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-understanding-revenuecat/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.