测试与安全

rc-security

revenuecat/ai-toolkit

Use this skill when hardening a RevenueCat integration on Android. Covers Trusted Entitlements response verification (INFORMATIONAL vs ENFORCED), why the server is always the authority, API key hygiene (public SDK key vs secret REST key), anonymous user identity, and purchase token protections RevenueCat provides automatically.

  • 667 次安装
  • 76 星标
  • 收录于

安装命令

npx skills add https://github.com/revenuecat/ai-toolkit --skill rc-security

SKILL.md

Phase 0: Intent

Tell the user: "I will review your RevenueCat security posture on Android: verification mode, API keys, user identity, and server side access decisions."

Phase 1: Discovery

Confirm what RevenueCat already covers so you can focus on the real gaps.

Concern Who handles it How
Receipt validation against Google Play RevenueCat backend Runs before awaitPurchase() returns
Purchase token reuse RevenueCat backend Tokens are deduplicated server side
Fabricated purchase tokens RevenueCat backend Fails Google Play verification, no entitlement granted
HTTPS transport to RevenueCat SDK Always on
Retry of token post on network failure SDK Retries on next app launch

Ask the project these questions: