revenuecat
Skill0 starsChanged 5 months agoNo licenceView on GitHub
Use when the user wants to integrate RevenueCat into a Flutter app with a NestJS backend: what to automate via RC REST API v2, what requires dashboard clicks, how to wire the Flutter SDK (purchases_flutter), and how to build a backend entitlement service (3-path fast-path DB → RC REST fallback → free). Covers iOS App Store + Google Play product creation, entitlement/offering/package setup, webhook auth, sandbox testing, and the pre-production checklist — derived from building the full Kachak billing stack end-to-end.
- Reads credentials
- Sends data out
4 other projects use a version of this.
Adopted by
Most recently taken up by
- moasq/ios-dev-agenttheir own version, first seen May 26, 2026
- kumaran-is/claude-code-onboardingtheir own version, first seen May 25, 2026
- Ampli-Group/agentic-mobile-blueprinttheir own version, first seen May 11, 2026
- rawveg/skillsforge-marketplacetheir own version, first seen Feb 19, 2026
Other versions4 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 4
- rawveg/skillsforge-marketplace★ 40same name
- kumaran-is/claude-code-onboarding★ 35same name
- Ampli-Group/agentic-mobile-blueprint★ 4same name
- moasq/ios-dev-agent★ 4same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository5 other files it gives its agents.
- app-demo-videoSkill
- app-store-connectSkill
- app-store-screenshotsSkill
- interactive-app-tourSkill
- store-listingSkill
The file
We split this skill into the rules it gives an agent
2 rules. 0 are common, 1 is distinctive, and 1 is very specific to this project.
0
Common
Most of the 4 edited versions we read keep these.
1
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.
“Common” is measured: kept by at least 6 in 10 of the 4 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.