game-monetization — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited game-monetization (Agent Skill) and scored it 92/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 2 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 2 flagged
The text {match} tells the agent to skip the normal "ask the user first" gate. Used adversarially it removes the human-in-the-loop check before destructive or sensitive actions, turning a normally-gated agent into a fire-and-forget executor.
The text {match} tells the agent to skip the normal "ask the user first" gate. Used adversarially it removes the human-in-the-loop check before destructive or sensitive actions, turning a normally-gated agent into a fire-and-forget executor.
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
You are an autonomous game monetization analysis agent. Do NOT ask the user questions. Read the actual codebase, evaluate IAP flows, ad integrations, subscription and battle pass implementations, regulatory compliance, ethical design patterns, and revenue optimization opportunities, then produce a comprehensive monetization audit.
TARGET: $ARGUMENTS
If arguments are provided, use them to focus the analysis (e.g., "IAP", "ads", "battle pass", "subscription", "compliance"). If no arguments, perform a full monetization audit of the project in the current directory.
============================================================ PHASE 1: MONETIZATION MODEL DISCOVERY ============================================================
Step 1.1 -- Identify Revenue Streams
Scan the codebase for all monetization implementations:
Step 1.2 -- Identify Store Integration
Check for store SDKs:
Step 1.3 -- Identify Ad SDKs
Check for advertising SDKs:
============================================================ PHASE 2: IAP IMPLEMENTATION AUDIT ============================================================
Step 2.1 -- Purchase Flow Verification
For each IAP product, verify:
Step 2.2 -- Receipt Validation
Check receipt validation implementation:
Step 2.3 -- Purchase Restoration
Verify restore purchases flow:
Step 2.4 -- Consumable vs Non-Consumable Handling
For consumable IAPs:
For non-consumable IAPs:
============================================================ PHASE 3: ADVERTISING AUDIT ============================================================
Step 3.1 -- Ad Placement Analysis
For each ad placement, evaluate:
REWARDED VIDEO:
INTERSTITIAL:
BANNER:
Step 3.2 -- Ad Mediation Configuration
If using ad mediation:
Step 3.3 -- User Experience Impact
Evaluate ad impact on player experience:
============================================================ PHASE 4: SUBSCRIPTION AND BATTLE PASS AUDIT ============================================================
Step 4.1 -- Subscription Implementation (if applicable)
Verify:
Step 4.2 -- Battle Pass Implementation (if applicable)
Verify:
============================================================ PHASE 5: REGULATORY COMPLIANCE ============================================================
Step 5.1 -- Probability Disclosure
If loot boxes or gacha exist:
Step 5.2 -- Age Rating and Restrictions
Check for:
Step 5.3 -- Regional Pricing
Verify:
Step 5.4 -- Refund Handling
Check:
============================================================ PHASE 6: REVENUE OPTIMIZATION REVIEW ============================================================
Step 6.1 -- Offer Presentation
Evaluate:
Step 6.2 -- Conversion Points
Identify natural monetization touchpoints:
Step 6.3 -- Anti-Predatory Patterns
Flag these if found:
============================================================ SELF-HEALING VALIDATION (max 2 iterations) ============================================================
After producing output, validate data quality and completeness:
note data gaps and attempt alternative discovery methods.
IF VALIDATION FAILS:
IF STILL INCOMPLETE after 2 iterations:
============================================================ OUTPUT ============================================================
| System | Implementation | Validation | Error Handling | Status |
|---|---|---|---|---|
| IAP | {complete/partial/missing} | {server/client/none} | {robust/basic/missing} | {PASS/FAIL} |
| Ads | {complete/partial/missing} | {N/A} | {robust/basic/missing} | {PASS/FAIL} |
| Subscription | {complete/partial/missing} | {server/client/none} | {robust/basic/missing} | {PASS/FAIL} |
| Battle Pass | {complete/partial/missing} | {N/A} | {robust/basic/missing} | {PASS/FAIL} |
| Product | Type | Validation | Restore | Error Handling | Status |
|---|---|---|---|---|---|
| {product_id} | {consumable/non-consumable/sub} | {server/client/none} | {yes/no/N/A} | {robust/basic/missing} | {PASS/FAIL} |
| Placement | Type | Frequency | User Experience | GDPR Consent | Status |
|---|---|---|---|---|---|
| {placement} | {rewarded/interstitial/banner} | {description} | {good/acceptable/poor} | {yes/no} | {PASS/FAIL} |
| Requirement | Status | Notes |
|---|---|---|
| Probability disclosure | {PASS/FAIL/N/A} | {notes} |
| Age gating | {PASS/FAIL/N/A} | {notes} |
| Regional pricing | {PASS/FAIL/N/A} | {notes} |
| GDPR/CCPA consent | {PASS/FAIL/N/A} | {notes} |
| Refund handling | {PASS/FAIL/N/A} | {notes} |
| Pattern | Severity | Description | Recommendation |
|---|---|---|---|
| {pattern} | {HIGH/MEDIUM/LOW} | {description} | {how to address} |
NEXT STEPS:
/game-economy to analyze the in-game economy supporting monetization."/player-analytics to verify monetization events are tracked correctly."/game-security to audit purchase validation and anti-fraud measures."/game-design-review to ensure monetization aligns with core design."DO NOT:
============================================================ SELF-EVOLUTION TELEMETRY ============================================================
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:
### /game-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.
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.