Name: rc-price-changes
Rating: 72 (1 reviews)
Author: RevenueCat

rc-price-changes

Use this skill when rolling out subscription price changes on Android with RevenueCat. Covers opt out decreases versus opt in increases, RevenueCat's automatic handling of the change confirmation flow, and the dashboard configuration involved.

Quality

89%

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

86%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 well-structured, actionable runbook that gives concrete code and dashboard steps without padding. The main improvement would be tightening the small amount of repeated opt-out/opt-in and legacy-cohort content and adding a more explicit verification gate.

Suggestions

Deduplicate the opt-out/opt-in explanation (prose in Phase 1 plus the Phase 2 table) and the legacy-cohort note so each point appears once, trimming tokens.

Add an explicit validate-then-proceed checkpoint between the Play Console price edit and relying on the new price (e.g., confirm propagation before refreshing offerings or notifying users).

Optionally surface a one-line verification for opt-in declines (assert the CANCELLATION webhook is handled in your existing cancellation path) to close the workflow's feedback loop.

Dimension	Reasoning	Score
Conciseness	Lean and assumes Claude's competence throughout (no explanation of what RevenueCat or Google Play are), but the opt-out/opt-in distinction and the legacy-cohort note each appear twice, so not literally every token earns its place.	4 / 5
Actionability	Provides copy-paste-ready Kotlin for refreshing offerings and reading entitlements, concrete Play Console / dashboard steps, and specific webhook event names (SUBSCRIPTION_PRICE_CHANGE_UPDATED, CANCELLATION) covering the common cases.	5 / 5
Workflow Clarity	Clear Understand → Plan → Execute sequence with a gating decision table and 6 numbered steps, plus checkpoints (confirm price propagated, observe CustomerInfo); minor validation gaps rather than a formal validate→fix→retry loop keep it just under 5.	4 / 5
Progressive Disclosure	Well-organized phased sections with a single clearly signaled one-level reference to the full chapter; no bundle files are needed for this single-topic skill, and structure makes navigation easy.	5 / 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, specific description that concretely names the price-change actions RevenueCat handles and gives an explicit use-when trigger. It is highly distinct and complete, with only minor room to broaden natural trigger synonyms.

Dimension	Reasoning	Score
Specificity	Lists multiple specific concrete actions — "opt out decreases versus opt in increases", "RevenueCat's automatic handling of the change confirmation flow", and "dashboard configuration" — giving comprehensive coverage of the Android price-change domain.	5 / 5
Completeness	Explicitly answers both what (rolling out price changes, opt out vs opt in handling, confirmation flow, dashboard config) and when ("Use this skill when rolling out subscription price changes on Android with RevenueCat") with concrete trigger phrases.	5 / 5
Trigger Term Quality	Natural domain terms a user would say ("subscription price changes", "Android", "RevenueCat", "opt out decreases", "opt in increases") with good coverage, but missing some common synonyms and variations that would push it to a 5.	4 / 5
Distinctiveness Conflict Risk	A clear niche — Android + RevenueCat + subscription price changes — with distinct triggers and minimal risk of firing for an unrelated skill.	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-price-changes/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.