Name: rc-testing
Rating: 72.8 (1 reviews)
Author: RevenueCat

rc-testing

Use this skill when testing a RevenueCat Android integration. Covers the RevenueCat Test Store (test_ API key prefix, in dialog Success/Fail/Cancel choice), mockk based unit testing with an interface wrapper around Purchases, and a GitHub Actions CI pattern. Avoids Google Play sandbox for day to day test iteration.

Quality

90%

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

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.

A tight, highly actionable skill body: phased workflow with tables, executable code for every step, and explicit verification and pre-ship checkpoints. The only notable gaps are undefined symbols in the mockk test example and inline code that could be split into reference files.

Suggestions

Define or annotate the placeholder symbols in the mockk test example (mockActivity, mockPackage, PaywallState) so the snippet is fully copy-paste ready.

Move the full BillingService implementation and GitHub Actions workflow into reference files (e.g. references/billing-service.md, references/ci.yml) to slim the main file and improve progressive disclosure.

Dimension	Reasoning	Score
Conciseness	Lean and efficient throughout: discovery and planning use compact tables instead of prose, explanations are limited to non-obvious facts ('The Purchases singleton is not mockable'), and no section explains concepts Claude already knows — matching the 5 anchor rather than the 4 anchor's 'minor instances of over-explanation'.	5 / 5
Actionability	Mostly executable guidance with copy-paste-ready gradle, Kotlin, and workflow YAML plus concrete dashboard navigation ('Apps & providers, then Create Test Store'), but the mockk test references undefined symbols (mockActivity, mockPackage, PaywallState) — minor gaps that fit the 4 anchor rather than 5's 'fully executable'.	4 / 5
Workflow Clarity	A clearly sequenced Discovery → Plan → Execute (Steps 1–7) → Verification → Pre-Ship Checklist flow with explicit validation checkpoints: the discovery gap-analysis table, 'Walk every branch of your error handling', a dedicated dashboard Verification section, and a shipping checklist — matching the 5 anchor. The destructive/batch cap does not apply since this is not a destructive operation.	5 / 5
Progressive Disclosure	Well-organized single-file structure with clear sections and a one-level-deep external reference ('Full chapter'), so most content is appropriately placed — but at ~180 lines with complete code examples and CI configuration inlined, some content could live in reference files, fitting the 4 anchor's 'minor organization gaps' rather than the 5 anchor.	4 / 5
	Total	18 / 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 this skill when…' trigger, third-person voice, and multiple concrete, domain-specific capabilities including a clear scope boundary. The only weakness is keyword coverage that omits some natural synonyms (in-app purchases, subscriptions, paywall).

Suggestions

Add natural trigger variations such as 'in-app purchases', 'subscriptions', 'paywall', or 'purchase testing' so users phrasing the need differently still match.

Consider mentioning the Google Play sandbox by the names users say ('Play Billing sandbox', 'license testers') since the description leans on avoiding it.

Dimension	Reasoning	Score
Specificity	Names multiple concrete capabilities — 'RevenueCat Test Store (test_ API key prefix, in dialog Success/Fail/Cancel choice)', 'mockk based unit testing with an interface wrapper around Purchases', and 'a GitHub Actions CI pattern' — which is comprehensive coverage of the domain, matching the 5 anchor rather than the 4 anchor's 'minor gaps'.	5 / 5
Completeness	Explicitly answers both: what ('Covers the RevenueCat Test Store… mockk based unit testing… GitHub Actions CI pattern') and when ('Use this skill when testing a RevenueCat Android integration'), plus a scope boundary ('Avoids Google Play sandbox for day to day test iteration') — matching the 5 anchor's concrete trigger phrases rather than the 4 anchor where 'when' could be more explicit.	5 / 5
Trigger Term Quality	Good natural keywords ('testing', 'RevenueCat Android integration', 'unit testing', 'Test Store', 'mockk', 'GitHub Actions', 'CI') that users would plausibly say, but common variations like 'in-app purchases', 'subscriptions', 'paywall', or 'sandbox' are missing, so it fits the 4 anchor ('a few natural terms missing') rather than 5's comprehensive synonym coverage.	4 / 5
Distinctiveness Conflict Risk	A clear niche (RevenueCat Android integration testing) with distinct triggers ('RevenueCat', 'Test Store', 'test_ API key', 'mockk') and minimal realistic conflict risk with other skills, matching the 5 anchor.	5 / 5
	Total	19 / 20 Passed

Validation

87%

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 — 14 / 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

	Total	14 / 16 Passed

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

Reviewed: 21 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.