monetization-model
Skill9 starsChanged 7 months agoMITView on GitHub
Guides through designing or auditing the monetization model. Creates GamePass/DevProduct catalog, pricing strategy, and revenue projections.
In this repository51 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- asset-auditSkill
- asset-from-imageSkill
- balance-checkSkill
- brainstormSkill
- bug-reportSkill
- changelogSkill
- code-reviewSkill
- datastore-reviewSkill
- design-reviewSkill
- design-systemSkill
- doctorSkill
- economy-auditSkill
- estimateSkill
- exploit-checkSkill
- gate-checkSkill
- gddSkill
- generate-assetSkill
- hotfixSkill
- launch-checklistSkill
- luau-lintSkill
- map-systemsSkill
- milestone-reviewSkill
- onboardSkill
- patch-notesSkill
- perf-profileSkill
- project-stage-detectSkill
- prototypeSkill
- publish-reviewSkill
- release-checklistSkill
- remotes-auditSkill
- retention-analysisSkill
- retrospectiveSkill
- reverse-documentSkill
- scope-checkSkill
- sprint-planSkill
- startSkill
- studio-inspectSkill
- studio-screenshotSkill
- studio-testSkill
- team-combatSkill
- team-economySkill
- team-polishSkill
- team-releaseSkill
- team-uiSkill
- tech-debtSkill
- wiki-ingestSkill
- wiki-lintSkill
- wiki-querySkill
- wiki-seedSkill
- wiki-updateSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 85
Never implement changes without explicit sign-off.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
/monetization-model — Monetization Design Workflow
Delegate to: monetization-lead (with economy-designer for currency flow)
Steps
1. Context Gathering
Ask:
- "What game stage are we in?" (pre-launch / launched / live-ops)
- "What's the player audience skew?" (age, platform)
- "What are the creative pillars? (can't contradict them)"
- "What's the target: revenue, retention, engagement?"
2. Ethical Review (NON-NEGOTIABLE)
Before designing, confirm:
- No loot boxes with real-money purchase (Roblox ToS)
- No pay-to-win that makes F2P feel unable to compete
- No FOMO targeting young players
- No misleading pricing
- Free players have a complete, enjoyable experience
3. Design the Catalog
GamePasses (permanent purchases)
For each proposed GamePass:
- Name
- Price (Robux) — use clean values: 49, 99, 199, 299, 499, 799, 999, 1499, 2499
- What it grants
- Target player type (new player / mid game / whale)
- Pay-to-win check
Example:
| Name | Price | Grants | Target | P2W? |
| VIP | 499 | Chat color, +5% coins, VIP room | Engaged player | No |
| Double Inventory | 299 | 2x inventory slots | Mid-game | No |
| Auto-Farm | 799 | Passive resource generation | Whale | Borderline — balance |
DevProducts (consumable purchases)
For each proposed DevProduct:
- Name
- Price (Robux)
- What it grants
- How often players buy (expected frequency)
- Is it pay-to-win?
Example:
| Name | Price | Grants | Frequency | P2W? |
| 1000 Gems | 99 | 1000 premium currency | Variable | No (gems buy cosmetics) |
| Revive Token | 25 | Revive at death | Per-death | Soft |
| XP Boost 2x 1hr | 49 | 2x XP for 1 hour | Occasional | Soft |
4. Pricing Strategy
- Entry Price Point: At least one item at 25-49 R$ (almost everyone has this)
- Mid Tier: 199-499 R$ (engaged players)
- Premium: 999+ R$ (whales)
- Comparable Items: Reference 3-5 successful similar Roblox games' pricing
5. Funnel Design
How does a player discover and decide to buy?
- Touchpoint 1: First mention (tutorial hint, menu badge, etc.)
- Touchpoint 2: Consideration (shop browse, see other players using)
- Touchpoint 3: Decision (purchase prompt with clear value proposition)
- Touchpoint 4: Post-purchase reinforcement (confirmation, immediate use)
6. Revenue Projection
Rough model:
DAU × Conversion Rate × Avg Purchase × Dev Exchange = Revenue
1000 DAU × 3% × 300 R$ × $0.0035 = $31.50/day from conversions7. Generate Plan Document
Save to design/monetization-plan.md using .claude/docs/templates/monetization-plan-template.md.
Output
Present the full plan for user review and approval. Never implement changes without explicit sign-off.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

