Query RevenueCat metrics and search documentation.
Works with
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionrevenuecatExecute the skills CLI command in your project's root directory to begin installation:
Fetches revenuecat from revenuecat/revenuecat-skill and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate revenuecat. Access via /revenuecat in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
0
total installs
0
this week
13
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
13
stars
Query RevenueCat metrics and search documentation.
Set RC_API_KEY environment variable, which should be a v2 secret API key.
Query the RevenueCat API (GET /projects) to get information about the project you have access to. Your RevenueCat API key allows access to a single project. Use the project ID in subsequent API calls.
{baseDir}/scripts/rc-api.sh <endpoint>
Example: {baseDir}/scripts/rc-api.sh /projects to list projects.
Start with {baseDir}/references/api-v2.md for auth, pagination, and common patterns. Then load the domain file you need:
| Domain | File | Covers |
|---|---|---|
| Customers | references/customers.md |
CRUD, attributes, aliases, entitlements, subscriptions, purchases, invoices, virtual currencies, actions |
| Subscriptions | references/subscriptions.md |
List, get, transactions, cancel, refund, management URL |
| Products | references/products.md |
CRUD, create in store, test prices |
| Offerings | references/offerings.md |
Offerings, packages, package products |
| Entitlements | references/entitlements.md |
CRUD, attach/detach products |
| Purchases | references/purchases.md |
List, get, refund, entitlements |
| Projects | references/projects.md |
Projects, apps, API keys, StoreKit config |
| Metrics | references/metrics.md |
Overview metrics, charts, chart options |
| Paywalls | references/paywalls.md |
Paywall creation |
| Integrations | references/integrations.md |
Integrations CRUD |
| Virtual Currencies | references/virtual-currencies.md |
Virtual currencies CRUD |
| Error Handling | references/error-handling.md |
Error handling |
| Rate Limits | references/rate-limits.md |
Rate limits |
Only load the reference file relevant to the current task — don't load them all.
The RevenueCat documentation is available at https://www.revenuecat.com/docs. Use https://www.revenuecat.com/docs/llms.txt and /sitemap.xml as a guide to the content that is available. Add .md to the end of a documentation URL to get the markdown version of the page.
Make data-driven prioritization decisions faster
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Prerequisites
Time Estimate
30-60 minutes to see productivity improvements
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid when
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
mattpocock/skills
parcadei/continuous-claude-v3
cursor/plugins
ailabs-393/ai-labs-claude-skills
pproenca/dot-skills
mattpocock/skills
revenuecat is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
revenuecat fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
Keeps context tight: revenuecat is the kind of skill you can hand to a new teammate without a long onboarding doc.
Solid pick for teams standardizing on skills: revenuecat is focused, and the summary matches what you get after install.
I recommend revenuecat for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
revenuecat has been reliable in day-to-day use. Documentation quality is above average for community skills.
Keeps context tight: revenuecat is the kind of skill you can hand to a new teammate without a long onboarding doc.
Solid pick for teams standardizing on skills: revenuecat is focused, and the summary matches what you get after install.
We added revenuecat from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
I recommend revenuecat for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
showing 1-10 of 72