Name: rc-revenuecat-api-quick-reference
Rating: 69.6 (1 reviews)
Author: RevenueCat

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

86%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

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

An efficient, highly actionable quick-reference skill with copy-paste Kotlin and a clean phased lookup workflow. It is well-organized and concise; minor gains would come from an explicit routing confirmation step and optionally splitting the reference tables into bundle files.

Suggestions

Add a brief confirmation checkpoint in Phase 1 (e.g. 'Confirm you are reading the SDK table, not the REST section, before copying a snippet') to make the routing decision explicit.

Consider moving the per-field reference tables into a references/ bundle file so SKILL.md stays a lean index, retaining only the most-used snippets inline.

Dimension	Reasoning	Score
Conciseness	Lean reference tables with terse inline annotations (defaults, return types, null semantics) and no padding; assumes Claude's competence and every token earns its place.	5 / 5
Actionability	Fully executable, copy-paste-ready Kotlin covering the common cases — init, purchase/upgrade, customer info, offerings, entitlements, errors, and listeners — with concrete signatures and field access.	5 / 5
Workflow Clarity	A clear phased sequence (Intent → Locate → Reference Tables → Typical Snippets) with explicit SDK-vs-REST routing, though there is no explicit confirm/routing-checkpoint step; read-only lookup needs no validation.	4 / 5
Progressive Disclosure	A single well-sectioned file with clearly signaled one-level references (sibling skills and the external appendix); bulk tables are inline, which is appropriate for a quick reference, but no bundle files exist to offload detail.	4 / 5
	Total	18 / 20 Passed

Description

83%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, specific description that names concrete API surfaces and carries an explicit trigger clause. It is highly distinctive and low-conflict; the main room for improvement is richer trigger phrasing and a few more natural keyword variants.

Suggestions

Expand the 'when' clause with concrete trigger phrases (e.g. 'Use when configuring Purchases, fetching Offerings, reading CustomerInfo, or calling RevenueCat REST endpoints').

Add natural synonyms/extensions users might say, such as 'in-app purchases', 'subscriptions', or 'RevenueCat server API', to broaden trigger coverage.

Dimension	Reasoning	Score
Specificity	Enumerates multiple concrete API surfaces — 'SDK init, common Purchases calls, CustomerInfo / Offerings access patterns, and the most used REST endpoints' — giving comprehensive coverage of the skill's scope.	5 / 5
Completeness	Both 'what' (enumerated surfaces) and 'when' ('Use this skill as a quick reference for...') are present, but the 'when' is domain-scoped rather than spelling out concrete trigger scenarios.	4 / 5
Trigger Term Quality	Natural domain keywords are present ('RevenueCat Android SDK', 'REST API', 'CustomerInfo', 'Offerings', 'Purchases') but synonyms and common variations are limited and the trigger phrasing is singular.	4 / 5
Distinctiveness Conflict Risk	Targets a clearly bounded RevenueCat Android SDK 10.x / REST API niche with distinct triggers and minimal overlap risk beyond sibling RevenueCat skills.	5 / 5
	Total	18 / 20 Passed

Validation

81%

Warnings & errors only

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

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning
metadata_field	'metadata' should map string keys to string values	Warning
relative_links	Relative link issues: 6 suspicious	Warning

	Total	13 / 16 Passed

Repository: RevenueCat/ai-toolkit
Path: revenuecat-play-billing/skills/rc-revenuecat-api-quick-reference/SKILL.md
Commit: ccfc038

Reviewed: 20 hours ago

Table of Contents

Discovery Implementation Validation

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.