CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

rc-revenuecat-api-quick-reference

Use this skill as a quick reference for the RevenueCat Android SDK 10.x and REST API. Covers SDK init, common Purchases calls, CustomerInfo / Offerings access patterns, and the most used REST endpoints.

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-revenuecat-api-quick-reference/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 body is an excellent quick-reference artifact: fully executable code with real signatures and defaults, a concrete REST endpoint table, an explicit SDK-vs-REST routing phase, and typical-snippet examples covering the common cases. It is token-efficient with only minor trims available, and full detail is cleanly externalized one level deep. The only structural consideration is that the bulk API reference lives entirely inline in SKILL.md with no bundle split, which is a reasonable trade-off for a lookup skill.

DimensionReasoningScore

Conciseness

The body is dense code tables and executable snippets with minimal padding — every API row earns its place. Minor instances could be trimmed: version pins ('SDK 10.x surface') appear in prose without a deprecated/old-patterns section, and Phase 0's question list partially duplicates the frontmatter description, fitting anchor 4 rather than anchor 5's lean ideal.

4 / 5

Actionability

Fully executable Kotlin with real signatures, types, and defaults (e.g. 'Purchases.sharedInstance.awaitPurchase(PurchaseParams.Builder(activity, packageOrStoreProductOrSubscriptionOption).build())', 'fetchPolicy = CacheFetchPolicy.FETCH_CURRENT'), a concrete REST endpoint table with paths and payload hints ('end_time_ms'), and copy-paste-ready Phase 3 snippets covering the common cases — matching anchor 5.

5 / 5

Workflow Clarity

This is a single-purpose lookup skill whose single action is unambiguous: Phase 1 gives explicit SDK-vs-REST routing rules ('Code runs inside the Android app...' vs 'Code runs on your backend...') before the labeled reference tables. No destructive or batch operations exist, so the validation cap does not apply, and the simple-skill exception holds.

5 / 5

Progressive Disclosure

Good structure with clear phase headers and correct one-level-deep externalization of full detail ('see the [full appendix on revenuecat.com]', sibling-skill links). No bundle files exist, so the entire API reference is inlined in SKILL.md; for a quick-reference skill this is defensible, but it leaves minor organization gaps versus anchor 5's well-split multi-file layout.

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 names a clear, well-scoped niche and enumerates several concrete capability areas with good natural keywords. Its main weakness is the missing explicit 'Use when...' trigger clause, which leaves the activation conditions implied and caps completeness. Adding an explicit when-clause and a few more natural trigger terms (entitlements, subscriptions, in-app purchases) would lift it to the top band.

Suggestions

Add an explicit trigger clause, e.g. 'Use when writing Android code or server logic that calls RevenueCat Purchases, CustomerInfo, Offerings, or entitlement APIs, or when integrating the RevenueCat REST endpoints.'

Include the natural terms users would actually say — 'entitlements', 'subscriptions', 'in-app purchases', 'play store billing' — alongside the existing SDK class names.

Replace the generic phrase 'common Purchases calls' with the specific operations covered (purchase, restore, log in/out, fetch offerings/customer info) to sharpen the capability list.

DimensionReasoningScore

Specificity

Lists several concrete capability areas ('SDK init', 'common Purchases calls', 'CustomerInfo / Offerings access patterns', 'most used REST endpoints'), but 'common Purchases calls' is generic and coverage has minor gaps, matching anchor 4 rather than anchor 5's comprehensive action enumeration.

4 / 5

Completeness

The 'what' is clear (quick reference covering init, Purchases calls, CustomerInfo/Offerings, REST endpoints), but there is no 'Use when...' clause or equivalent explicit trigger guidance — 'Use this skill as a quick reference for X' describes form rather than activation conditions, capping completeness at 3 per the judging guideline.

3 / 5

Trigger Term Quality

Good natural keyword coverage ('RevenueCat', 'Android SDK', 'REST API', 'CustomerInfo', 'Offerings') but misses common variations users would say such as 'entitlements', 'subscriptions', or 'in-app purchases', fitting anchor 4's 'a few natural terms missing' rather than anchor 5.

4 / 5

Distinctiveness Conflict Risk

Clear niche ('RevenueCat Android SDK 10.x and REST API') with distinct triggers, but there is minor overlap risk with the closely related sibling RevenueCat skills referenced in the body (rc-purchase-flow, rc-error-handling, rc-backend, rc-webhooks), matching anchor 4 rather than anchor 5's minimal conflict risk.

4 / 5

Total

15

/

20

Passed

Validation

81%

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

Validation — 13 / 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

relative_links

Relative link issues: 8 suspicious

Warning

Total

13

/

16

Passed

Repository

RevenueCat/ai-toolkit

Path

revenuecat-play-billing/skills/rc-revenuecat-api-quick-reference/SKILL.md

Revision

2aeae8c

Reviewed

Table of Contents

DiscoveryImplementationValidation

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.

Claim skill