Monetization sdk integration
Skill meyverick/agy-skills/skills/monetization-sdk-integration
A collection of elite, modular, and validated AI agent skills and system rules for Google Antigravity.
npx -y skills add meyverick/agy-skills --skill monetization-sdk-integrationAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Architects multi-network Ad Mediation integrations. Use when integrating AppLovin MAX, IronSource, or handling ad state machines and callbacks.
SKILL.md
2.3 KB, as published. Nobody here has run it
Monetization SDK Integration
This skill standardizes the robust integration of complex Ad Mediation SDKs (e.g., AppLovin MAX, IronSource, AdMob). It explicitly mandates exponential backoff retries and explicit state machine handling to prevent unhandled ad failures and null-reference crashes.
When to Use
- Use when initializing third-party Ad SDKs.
- Use when defining callbacks for rewarded video or interstitial ads.
- Use when implementing consent flows (GDPR/CCPA/ATT).
- NOT for creating playable ad game logic.
Core Process
Phase 1: Explicit Initialization
- Ad networks require network callbacks. Never assume
Init()finishes instantly. - Create an explicit state machine for Ad State:
Uninitialized -> Initializing -> Ready -> Loading -> Showing -> Completed.
Phase 2: Exponential Backoff Retries
- Ad load failures are common due to poor network connectivity.
- Do not immediately retry
LoadAd()upon a failure callback. Implement exponential backoff (e.g., 2s, 4s, 8s) to prevent hammering the ad server and getting rate-limited.
Phase 3: Reward Fulfillment
- Rewards must only be granted inside the
OnAdRewarded(or equivalent) callback. - Do not grant rewards immediately upon clicking the ad.
Common Rationalizations
| Rationalization | Reality |
|---|---|
"I'll just call LoadAd() immediately after Init()." | Initialization is asynchronous. Calling LoadAd() before the OnInitComplete callback fires will result in a hard crash. |
"If the ad fails to load, I'll just call LoadAd() again immediately." | This creates an infinite loop if the user has no internet. You MUST implement an exponential backoff timer. |
Red Flags
- Missing exponential backoff logic in the
OnAdLoadFailedcallback. - Assuming the SDK is initialized synchronously within the
Start()method.
Verification
Before finalizing the integration:
-
Init()strictly utilizes callback delegates before allowingLoadAd(). - The
LoadFailedcallback triggers an exponential backoff Coroutine/Timer, not a direct retry. - Consent structures (GDPR) are passed into the SDK before initialization.
Gives 0 of the 12 instructions most pricing monetisation skills give
Counted across 366 of the 366 authors here whose files we hold, read 2026-08-06
- verify webhook signaturesin 23 of 366, across 19 files
- differentiate tiers using features, limits, or supportin 15 of 366, across 4 files
- read product marketing context before asking questionsin 14 of 366, across 6 files
- base price on perceived value, not costin 14 of 366, across 3 files
- use Van Westendorp to find acceptable price rangein 14 of 366, across 3 files
- use MaxDiff to identify highly valued featuresin 14 of 366, across 3 files
- choose a value metric that scales with customer valuein 14 of 366, across 9 files
- handle webhook events idempotentlyin 12 of 366, across 6 files
- understand the upgrade context before recommendingin 11 of 366, across 4 files
- align the pricing metric with delivered valuein 10 of 366, across 4 files
- install stripe packagein 10 of 366, across 5 files
- calculate unit economics metricsin 10 of 366, across 5 files
Said here and by no other author read
- create an explicit ad state machine
- use callback delegates for initialization
- implement exponential backoff for failed ad loads
- grant rewards only inside the reward callback
- pass consent structures before initialization
- verify load failed callback uses exponential backoff
Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once.