Monetization · v1.0.0

RevenueCat Subscription Lifecycle

Configure, integrate, verify, launch, operate, diagnose, or migrate RevenueCat subscriptions with store, identity, artifact, and entitlement continuity.

Release candidate
The workflow passed static publication checks, but download remains disabled until its license and final release manifest are approved.

The outcome

Turn a selected RevenueCat architecture into a commercially complete, evidence-backed and reversible subscription capability instead of stopping at dashboard objects, an SDK build, or one successful test callback.

Use it when

  • Invoke automatically when the user asks to add, configure, test, launch, operate, migrate, or troubleshoot RevenueCat subscriptions or in-app purchases for an app.
  • Use for bounded requests such as checking product mappings, repairing entitlement unlock, configuring a Flutter SDK, validating restore/login behavior, hardening webhooks, or proving a release artifact is production ready.

It does not do

  • Does not replace the user’s final authorization for project scope, account access, external changes, or business consequences.
  • Does not represent repository static checks as runtime certification across every platform, provider account, or production environment.

Inputs

  • Requested outcome and stop state, selected business model, platforms/stores, application and RevenueCat project references, store product design, entitlement/feature contract, identity model, repository/framework, backend, public legal URLs, and authorized mutations.
  • Current official provider/store sources, project-bound toolchains, environment-specific key references, candidate artifact identity, test accounts/data aliases, commercial UX, webhook/reconciliation design, rollout, and rollback.

Outputs

  • The exact designed, configured, integrated, sandbox-verified, production-ready, operational, diagnosed, or migrated outcome with a canonical store-to-feature mapping and unchanged/deferred surfaces stated.
  • Evidence for source dates, keys and artifact identity, customer transitions, commercial UX, platform sandbox, backend/webhooks, observability, customer-impact risk, rollout and subscriber-safe rollback, plus a validated secret-safe manifest for nontrivial work.

Natural-language triggers

Add RevenueCat subscriptions to this Flutter app using its project-bound FVM, and stop after platform sandbox verification.
Check why a successful App Store purchase does not unlock premium, but do not grant access or change production configuration yet.
Verify every product, entitlement, offering, package, restore path, and release key before submitting this build for review.
Use $revenuecat-subscription-lifecycle explicitly only when automatic routing needs disambiguation.

Permission map

FilesWrite

May inspect and update explicitly scoped project or configuration files.

CommandsExecute

May run project, platform, validation, and deployment commands.

NetworkExecute

May call declared provider APIs and public verification endpoints.

AccountsChanges state

May read or change authorized provider-account configuration after required confirmation.

BrowserChanges state

May use provider consoles for states not exposed safely through an API or CLI.

External changesChanges state

Can create consequential external state; preview, confirmation, verification, and rollback are required.

Environment & requirements

Agents

  • Codex
  • Claude Code

Platforms

  • macOS
  • Linux
  • Windows

Required tools

  • Git
  • store developer account
  • RevenueCat account

Data handling

May read products, offerings, entitlements, webhooks, and store configuration; API keys, receipts, and user purchase data must not enter reports or artifacts.

Credential handling

Uses only existing secure credential channels authorized by the user; tokens, keys, cookies, private keys, and real user data must not be copied into the Skill, logs, reports, or public artifacts.

Declared network domains

api.revenuecat.com app.revenuecat.com appstoreconnect.apple.com play.google.com

Verification evidence

Passed repository structure, bilingual metadata, and reference checks; this Skill has not entered candidate-artifact generation or runtime verification.

Level
Checked
Checked
2026-10-12
Expires
2027-01-10
Source revision
fac86e9d2646

Environment

  • Repository structure and metadata validation on macOS

Targets checked

  • source metadata
  • package structure

Evidence IDs

  • public-catalog-schema-v3
  • source-repository-validation

Limits & support

Known limitations

  • The current verification level is a repository static check, not an end-to-end validation against a real provider account, physical device, or production environment.
  • Agents, platforms, and provider interfaces continue to change; each run must inspect current state and respect explicit confirmation gates.

Permission changes

  • No permission change is declared for this release; for a first public release, the permission map on this page is authoritative.

Channel
Submit through support@xiaoyuelabs.com or the on-site inquiry form.

Response target
Receipt is acknowledged within two business days; remediation timing is confirmed after reproduction and scope review.

Scope
Free support covers download integrity, documentation errors, and reproducible Skill defects; project adaptation, managed operation, and ongoing maintenance are separate services.

Release notes

v1.0.0
  • Added one naturally invoked RevenueCat lifecycle covering architecture, project/store configuration, SDK integration, commercial paywalls, testing, launch, operations, diagnosis, and migration without forcing RevenueCat as the product choice.
  • Made store-to-product-to-entitlement-to-offering/package-to-feature mapping, App User ID transitions, Flutter FVM binding, restore behavior, environment-specific keys, webhooks, reconciliation, and subscriber-safe rollback explicit gates.
  • Added a bilingual, secret-safe lifecycle manifest and validator that reject global Flutter, leaked credentials, unauthorized production/customer mutations, Test Store release mistakes, incomplete platform-sandbox evidence, and unsupported production-ready claims.

Install & verify

Release access

Available for evaluation, not yet packaged

v1.0.0

This workflow is listed so its scope, permissions, and service fit can be evaluated. It has not entered the first downloadable release batch and no public artifact exists.