SkillAgentSearch skills...

scenario-roblox-monetization

Use when a Roblox game sells something or plans live ops: Developer Products, game passes, experience subscriptions, Roblox Plus perks, ProcessReceipt or BindReceiptHandler, \"bought it but didn't get it\", a purchase granted twice, shop UI prices, eggs, crates or loot boxes with odds (paid random i…

Install / Use

npx skills add scenario-labs/skills --skill scenario-roblox-monetization

Installs into whichever agent you are using.

About this skill
📄

SKILL.md

Installable skill definition

Quality Score

86/100

Supported Platforms

Universal

Tags

Our assessment of scenario-roblox-monetization

scenario-roblox-monetization scores 86/100 on our quality scale, 421st of 598 Data & Analytics skills we index.

Its SKILL.md is 18 KB long, well organised into 10 sections and no code examples: a thorough specification that gives an agent plenty to work with.

With 1,048 GitHub stars, it is one of the more widely adopted skills in the catalogue.

Substance
30/30
Structure
13/20
Description
15/15
Adoption
13/20
Freshness
15/15

Maintenance, license and trust

  • The repository was last updated 35 days ago, so scenario-roblox-monetization is actively maintained.
  • It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
  • Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.

Safety scan

No issues found

Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands.

Automated pattern scan on 2026-11-20. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.

scenario-roblox-monetization compared with similar skills

All 4 of these similar skills score higher than scenario-roblox-monetization; compare them before choosing.

SkillScoreStarsUpdatedFormat
scenario-roblox-monetization (this skill)by scenario-labs861.0k35d agoSKILL.md
algorithmic-artby anthropics100177.9k2mo agoSKILL.md
pptxby anthropics100177.9k2mo agoSKILL.md
prospectingby coreyhaines3110060.1k11d agoSKILL.md
ad-creativeby coreyhaines3110060.1k11d agoSKILL.md

Frequently asked questions

How do I install scenario-roblox-monetization?
Run npx skills add scenario-labs/skills --skill scenario-roblox-monetization. The install tabs above show the steps for each supported agent.
Which AI agents does scenario-roblox-monetization work with?
It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
Is scenario-roblox-monetization safe to use?
Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. It is MIT-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
Is scenario-roblox-monetization still maintained?
The repository was last updated 35 days ago, so scenario-roblox-monetization is actively maintained.

name: scenario-roblox-monetization description: "Use when a Roblox game sells something or plans live ops: Developer Products, game passes, experience subscriptions, Roblox Plus perks, ProcessReceipt or BindReceiptHandler, "bought it but didn't get it", a purchase granted twice, shop UI prices, eggs, crates or loot boxes with odds (paid random items, PolicyService), rewarded video ads, AnalyticsService funnels, economy or custom events, ConfigService live config, A/B experiments, price optimization or regional pricing, game thumbnails and icons, play-through rate, Creator Rewards, Ads Manager campaigns, or a launch and update plan." license: MIT

Roblox Monetization and Live Ops

Target: Roblox Studio (October 2026 build) on macOS, driven through the scenario-roblox-expert toolkit.

Expert level here means every Robux path ends in one server receipt handler that grants only what the saved profile confirms, prices and odds come from one source the engine or a config owns, and every live change ships behind a config with a metric that decides it. The agent builds and tests the code in an unpublished place; product creation, dashboards and store art uploads stay with the owner.

If a sibling skill named here is missing from your available skills, load it with skill_get (Scenario MCP) or ask the user to install it (https://github.com/scenario-labs/skills#install); unattended, proceed from tool schemas and flag the gap.

REQUIRED BACKGROUND: scenario-roblox-expert (channels, review loop, toolkit, current-Roblox traps).

Stance (the expert delta)

  1. Grant only in the receipt handler, and only after the save. PurchaseGranted means the saved profile holds the PurchaseId; anything else answers NotProcessedYet. Prompt-finished events are not proof of payment (Creator Docs, developer products; Stewiepfing). The docs sample answers granted when the handler returns nil; the receipts suite reproduces that bug.
  2. One handler per server. New code uses BindReceiptHandler; legacy code assigns ProcessReceipt once, in one Script (MarketplaceService reference). Live, a second catch-all bind errors, while a second ProcessReceipt assignment is accepted without a warning.
  3. Prices come from the engine, on the client. Typed prices block price optimization and show Plus subscribers a price they do not pay (Creator Docs, managed pricing, Roblox Plus). The server never needs a price to grant.
  4. One odds table for the roll and the disclosure, gated per player. Show every outcome with numerical odds before spend, and check ArePaidRandomItemsRestricted per player (Creator Docs, paid random items). Prompt random items from the server after that check [added].
  5. Monetize every intended mechanic at launch, cheaply. Starter bundles at 25 to 99 Robux; many small spenders beat one high price; never gate basics such as movement (Roblox monetization leads and studio heads, RDC 2025). Adding payment later reads as pay to win.
  6. Every risky change ships behind a config, and data decides it. Read experiment values on the player snapshot where the player meets the feature, check the minimum detectable effect first, and let guardrails such as disconnects outrank a modest gain (Creator Docs, experiments; Roblox experiments team and studios, RDC 2025).
  7. The click gates discovery. Play-through rate and first-play bounce replaced QPTR; ranking learns only from organic Home traffic, and thumbnails must show the real game (Roblox discovery leads, RDC 2026 and RFY Q&A; studios, RDC 2025).
  8. Rewarded video pays a fixed developer product. It is user-initiated, disclosed, never Robux, never random, never a progress gate (Creator Docs). Reward obsolete paid items so ads do not cannibalize spenders (RDC 2025).

Establish first

  • Published or not: analytics, configs, ads and product lookups need a published experience. Unpublished, test with synthetic receipts and record what Studio does.
  • Product inventory: names, kinds (currency, bundle, pass, subscription), what each grants, and whether ids exist. Only the owner creates ids in Creator Hub (gui-paths.md).
  • Data layer: which profile store, and its getProfile and isPresent functions for scenario-roblox-data Receipts.
  • Audience: age range, regions with paid random restrictions, mobile share, DAU (experiments under about 1,000 DAU rarely reach significance).
  • Ads: owner age-verified 13+ with 2FA and a public game, or no rewarded video.
  • Defaults when unanswered: one catalog module, BindReceiptHandler through Purchases, prices via PriceText, a currency pack plus a starter bundle, no paid random items, telemetry and live config on from day one.

Procedure

Full code and test results are in procedures.md. Server modules (Catalog, Purchases, Entitlements, Telemetry) go in ServerScriptService.MonKit beside the data layer's Receipts; shared modules (Odds, PriceText, LiveConfig, ShopRank) in ReplicatedStorage.MonKit. Status: 16 of 16 live tests pass in Studio 0.743 on an unpublished place (2026-10-19); 61 suite tests pass in Lune and unchanged in Studio. Needs a published game, not yet run: a real RankProductsAsync ranking (unpublished: HTTP 400, catalog order kept) and no-description on your own items.

  1. Audit. Goal: every purchase path, price literal and client-side analytics or config call found. How: rbx_monetization.audit_place(place) offline (Lune), then MonAudit.run(game) through rbx_monetization.run in Edit. GATE: zero errors, and the live tally equals the offline tally.
  2. Catalog. Goal: products, passes and subscriptions in one server table, grants as data, no prices. How: Catalog.new(def), catalog:validate(); in a published test server, catalog:verify(fetch, game.CreatorId). GATE: no duplicate-id, bad-grant, unknown-id or foreign-id finding. A wrong pass id is not an error: live, pass id 1 resolved to another creator's pass.
  3. Receipts. Goal: exactly one grant per PurchaseId. How: Receipts.new{getProfile, isPresent, handlers = catalog:handlers()} from scenario-roblox-data, then Purchases.new{receipts, catalog, telemetry} and purchases:bind(MarketplaceService). Test with synthetic receipt tables, never a real prompt. GATE: a duplicate grants once, an absent player and a failed save answer NotProcessedYet, and the retry grants once.
  4. Perks. Goal: passes, subscriptions and Plus as server-checked perks. How: Entitlements.new{passes, subscriptions, owns, subStatus, onChanged}, ent:connect(MarketplaceService, Players); Entitlements.giveTool writes Backpack and StarterGear. GATE: a check that errors keeps the paid state; the tool survives respawn; the client shows "Owned" from the perk_ attribute.
  5. Prices. Goal: every displayed price is the player's price. How: PriceText.fetch and PriceText.view in a LocalScript when the shop opens. GATE: no price-literal finding; rows show "..." and stay unbuyable until the price loads.
  6. Paid random items. Goal: disclosed odds, a path for restricted players. How: one Odds.fromWeights module required by the server roll and the client panel; Odds.display behind a "Details" button with the disclaimer; restricted players get Odds.directPrice or no offer. GATE: displayed odds sum to 100% or carry the disclaimer; a restricted player cannot reach the prompt.
  7. Rewarded video. Goal: a disclosed, optional ad that pays a fixed product. How: client GetAdAvailabilityNowAsync when the menu opens; server CreateAdRewardFromDevProductId then ShowRewardedVideoAdAsync in pcall; the reward arrives as a receipt with channel AdReward. GATE: the ad row hides when unavailable; the reward path is the receipt path.
  8. Analytics. Goal: onboarding, shop funnel and economy events that survive exploiters and the limits. How: Telemetry on the server only; clients send step numbers, the server accepts forward steps only; log economy events after the save. GATE: invalid steps dropped and counted; event names, currencies and fields within the limits table.
  9. Live config and experiments. Goal: values change without a release. How: LiveConfig.new{defaults} with UpdateAvailable and Refresh, mirrored to cfg_ player attributes plus a cfgReady marker; forPlayer for experiment keys. GATE: defaults apply when ConfigService fails (live: it fails after about 30 s unpublished); the client reads values only after cfgReady.
  10. Store art. Goal: thumbnails, icon and item icons that pass the size rules and show the real game. How: capture a staged playtest view, thumb_from_capture, then Scenario art (see Handoffs); check_art(path, kind). GATE: zero errors from check_art; a contact sheet reviewed; the owner uploads.
  11. Launch and live ops. Goal: a plan with metrics that decide each step. How: rbx_monetization.mde(enrolled, baseline) for each test, rollout at 10, 50 then 100%, ads campaigns run 1 to 2 weeks without targeting for a baseline. GATE: each experiment has a primary metric, guardrails, an MDE under the expected effect and a stop date. Launch checklist and content pacing: launch-liveops.md.

Numbers

| Value | Relative to | Source | | -------------------------------------------- | ------------------------------------------------------------- | ------------------------------------ | | 25 to 99 Robux | Starter bundle price | RDC 2025 | | 100 PurchaseIds | Receipt log kept in the profile | scenario-roblox-data default [added] | | 60,000 transactions in 30 days | Price optimization eligibility; about 3 weeks at a 98/2 split | Docs | | 4 places below the first non-zero digit | Odds rounding, with the disclaimer | Docs | | 120 + 20 x CCU per minute | Analytics requests per server | Docs | | 3 fields, 10 currencies, 20 types, 100 SKUs | Analytics cardinality before "Other" | Docs | | 10 funnels, 100 steps, 100 event names | Analytics per experience | Docs | | 14 to 60 days, up to 2 variants | Experiment length and arms | Docs | | -10% playtime, -20% ARPU or payer conversion | Early harm stop, first 24 h, 10,000+ enrolled | Docs | | About 1,000 DAU | Below this, a useful MDE is hard to reach | Docs | | 10%, 50%, 100% | Rollout steps for risky features | RDC 2025 studios | | Up to 4% of daily earnings | Ads reinvestment; ROAS read over 30 days | RDC 2026 | | 1920x1080, 16:9, under 3 MB | Thumbnail; bottom strip covered by the player count | Docs | | 512x512, legible at 150x150 | Experience icon | Docs | | 512x512 max, circle crop | Pass and product ic

Truncated for display — read the full file on GitHub.

Related Skills

View on GitHub
GitHub Stars1.0k
CategoryData
Updated1mo ago
Forks129

Languages

Python

Trust signals

100/100

From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.

No cautions