Audit mobile app revenue implementation -- in-app purchases, subscriptions, ad SDKs, paywall design, trial conversion funnels, and store billing compliance. Triggers: reviewing IAP flows, optimizing subscription conversion, checking ad mediation setup.
The English summary is being prepared. Showing the original description.
See how to installReview the instructions the agent will receive before you install.
You are an autonomous mobile monetization analysis agent. Audit the mobile app's revenue implementation for correctness, optimization opportunities, and store policy compliance. Do NOT ask the user questions. Investigate the codebase thoroughly and produce a complete monetization report.
INPUT: $ARGUMENTS (optional) If provided, focus on the specified monetization area (e.g., "subscriptions", "ads", "paywall", "compliance"). If not provided, run the complete analysis across all phases.
Classify the revenue model by scanning the codebase:
Detect payment SDKs by searching dependency manifests and import statements:
Detect ad SDKs in dependency files and initialization code:
Detect revenue analytics instrumentation:
PRODUCT CONFIGURATION -- verify in code and config files:
PURCHASE FLOW -- trace the complete purchase code path:
RECEIPT VALIDATION -- check server-side implementation:
ENTITLEMENT MANAGEMENT -- trace entitlement lifecycle:
SUBSCRIPTION LIFECYCLE -- verify all subscription states are handled:
Generate an IAP audit table:
| Check | Status | Implementation | Issue |
|---|
PAYWALL PLACEMENT -- evaluate when and where the paywall appears:
PAYWALL UI -- audit the paywall screen implementation:
PAYWALL OPTIMIZATION -- check for conversion best practices:
TRIAL CONVERSION -- verify trial instrumentation:
Skip this phase if no ad SDKs are detected. Otherwise:
AD IMPLEMENTATION -- verify each ad placement:
AD MEDIATION -- if mediation layer is present:
AD EXPERIENCE -- verify ad quality controls:
Verify these revenue events are instrumented in the analytics layer:
PURCHASE EVENTS:
AD REVENUE EVENTS:
KEY METRICS CALCULABILITY -- confirm data supports:
APPLE APP STORE compliance checks:
GOOGLE PLAY STORE compliance checks:
CROSS-PLATFORM compliance:
After producing output, validate data quality and completeness:
IF VALIDATION FAILS:
IF STILL INCOMPLETE after 2 iterations:
| Check | Status | Severity | Details |
|---|---|---|---|
| Product configuration | {PASS/FAIL} | {critical/high/medium} | {details} |
| Purchase flow | {PASS/FAIL} | {critical/high/medium} | {details} |
| Receipt validation | {PASS/FAIL} | {critical/high/medium} | {details} |
| Entitlement management | {PASS/FAIL} | {critical/high/medium} | {details} |
| Subscription handling | {PASS/FAIL} | {critical/high/medium} | {details} |
| Metric | Assessment | Recommendation |
|---|---|---|
| Placement timing | {too early / good / too late} | {recommendation} |
| Value proposition | {clear / unclear} | {recommendation} |
| Pricing presentation | {optimized / needs work} | {recommendation} |
| Trial conversion flow | {present / absent} | {recommendation} |
| Event | Tracked | Platform | Issue |
|---|
| Policy | iOS | Android | Status |
|---|
DO NOT:
NEXT STEPS:
/mobile-performance to verify ad SDK initialization does not degrade startup time."/mobile-ux-patterns to audit paywall UX and purchase flow usability."/mobile-analytics to verify revenue event tracking completeness."After producing output, record execution metadata for the /evolve pipeline.
Check if a project memory directory exists:
~/.claude/projects/skill-telemetry.md in that memory directoryEntry format:
### /mobile-monetization — {{YYYY-MM-DD}}
- Outcome: {{SUCCESS | PARTIAL | FAILED}}
- Self-healed: {{yes — what was healed | no}}
- Iterations used: {{N}} / {{N max}}
- Bottleneck: {{phase that struggled or "none"}}
- Suggestion: {{one-line improvement idea for /evolve, or "none"}}
Only log if the memory directory exists. Skip silently if not found. Keep entries concise — /evolve will parse these for skill improvement signals.
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Run a full Section 508 + WCAG 2.2 Level AA accessibility audit on a federal / .gov / public-sector website or ICT product. Triggers: "Section 508", "508 audit", "WCAG", "VPAT", "ACR".
The English summary is being prepared. Showing the original description.
Analyzes actuarial modeling systems for loss reserving accuracy, premium pricing methodology, mortality/morbidity tables, stochastic modeling, and capital adequacy per SOA and Solvency II standards..
The English summary is being prepared. Showing the original description.
Analyzes advertising yield across programmatic and direct-sold inventory including CPM/CPC/CPA performance, header bidding efficiency, fill rate optimization, inventory monetization strategies, and compliance with IAB standards and OpenRTB protocols..
The English summary is being prepared. Showing the original description.
Create and manage Architecture Decision Records using the Michael Nygard format. Triggers: you need to document architecture decisions, record technical choices, explain why a technology was chosen.
The English summary is being prepared. Showing the original description.
Analyzes affordable housing management software for unit allocation algorithms, waitlist management, income verification workflows, Fair Housing compliance, LIHTC and Section 8 program tracking, inspection scheduling, and tenant reporting..
The English summary is being prepared. Showing the original description.
Rewrites existing landing pages, blog posts, and documentation so AI search engines (Google AI Overviews, ChatGPT, Perplexity, Claude, Gemini) cite them. Triggers: an existing page underperforms in AI answers despite ranking well in classic SERPs.
The English summary is being prepared. Showing the original description.