Set up a complete RevenueCat project from scratch — creates apps, products, entitlements, offerings, and packages in the correct order.
80
72%
Does it follow best practices?
Impact
90%
1.32xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./revenuecat/skills/create-revenuecat-project/SKILL.mdiOS subscription setup with existing App Store app
list-projects first
100%
100%
Multi-project handling
100%
70%
app_store app type
100%
100%
Correct resource order
100%
100%
create-entitlement used
100%
100%
attach-products-to-entitlement used
100%
100%
Offering lookup_key default
100%
100%
$rc_monthly package identifier
100%
100%
$rc_annual package identifier
100%
100%
API keys public note
60%
100%
Web SaaS setup using rc_billing app type
list-projects first
0%
100%
Discovery questions present
100%
100%
rc_billing app type
0%
100%
rc_billing is Stripe-powered
100%
100%
No extra Stripe Billing/Checkout cost
0%
100%
Correct resource order
100%
100%
Offering lookup_key default
33%
100%
Standard package identifier
100%
100%
list-app-public-api-keys used
0%
100%
Setup summary present
100%
100%
Android app not in Play Store uses test_store
list-projects first
0%
100%
Multi-project ask
50%
100%
Play Console registration question
80%
100%
test_store app type used
0%
15%
Play Console later guidance
100%
100%
Offering lookup_key default
100%
0%
Correct resource order
100%
100%
API keys public note
28%
100%
Setup summary present
100%
100%
407e465
Table of Contents
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.