scenario-roblox-data
Use when a Roblox game saves or loads player data, or when players report data not saving, lost progress, rollbacks, duplicated items or a purchase granted twice.
Install / Use
npx skills add scenario-labs/skills --skill scenario-roblox-dataInstalls into whichever agent you are using.
SKILL.md
Installable skill definition
Quality Score
Category
CommunicationSupported Platforms
Tags
Our assessment of scenario-roblox-data
scenario-roblox-data scores 89/100 on our quality scale, 234th of 397 Communication skills we index.
Its SKILL.md is 15 KB long, well organised into 10 sections with 1 code example: 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.
Maintenance, license and trust
- The repository was last updated 35 days ago, so scenario-roblox-data is actively maintained.
- Our last check on 2026-11-22 found the source still online.
- 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 foundOur 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-data compared with similar skills
All 4 of these similar skills score higher than scenario-roblox-data; compare them before choosing.
| Skill | Score | Stars | Updated | Format |
|---|---|---|---|---|
| scenario-roblox-data (this skill)by scenario-labs | 89 | 1.0k | 35d ago | SKILL.md |
| algorithmic-artby anthropics | 100 | 177.9k | 2mo ago | SKILL.md |
| pptxby anthropics | 100 | 177.9k | 2mo ago | SKILL.md |
| prospectingby coreyhaines31 | 100 | 60.1k | 11d ago | SKILL.md |
| ad-creativeby coreyhaines31 | 100 | 60.1k | 11d ago | SKILL.md |
Frequently asked questions
- How do I install scenario-roblox-data?
- Run
npx skills add scenario-labs/skills --skill scenario-roblox-data. The install tabs above show the steps for each supported agent. - Which AI agents does scenario-roblox-data 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-data 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-data still maintained?
- The repository was last updated 35 days ago, so scenario-roblox-data is actively maintained.
Skill content
View source on GitHubname: scenario-roblox-data description: "Use when a Roblox game saves or loads player data, or when players report data not saving, lost progress, rollbacks, duplicated items or a purchase granted twice. Triggers: DataStoreService, UpdateAsync, SetAsync, BindToClose, ProfileStore, ProfileService, DataStore2, session locking, data schema or migration, Developer Product ProcessReceipt, player trading, OrderedDataStore leaderboards, MemoryStore, MessagingService, TeleportService and reserved servers, DataStore budgets and throttling (errors 301 to 306), 'You must publish this place to the web to access DataStore', and testing data code in an unpublished place." license: MIT
Roblox Data and Backend
Roblox Studio (October 2026 build) on macOS, driven through the scenario-roblox-expert toolkit.
Expert level here means the data layer stays correct when a server crashes, a write fails after it landed, or two servers want the same player. Prove those cases against a simulated multi-server backend before any published test, because an unpublished place cannot reach DataStores at all.
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)
- Session locks stop duplication, UpdateAsync alone does not. One ProfileStore profile per
player holds the lock (loleris, ProfileStore docs).
UpdateAsyncis safer thanSetAsynconly when the transform reads the old value (Suphi Kaner, 00:04:43). - A failed write may have landed. Read with
UseCache = falsebefore redoing it (Roblox best practices). Put an operation id inside the value so a repeat is a no-op [added]. With 30% of writes failing after they landed, naive retries stored 39 for 30 operations in the mock run. - Retries on one key stay in order. A late retry of an old value overwrites newer data (Roblox
best practices).
KeyQueueserializes per key. - A purchase is granted once and confirmed saved. Log each
PurchaseIdin the profile. ReturnPurchaseGrantedonly whenLastSavedDataholds it (Rileybytes, 00:29:08; Roblox purchasing doc). Every other path returnsNotProcessedYet. - Migrate before
Reconcile.Reconcilecopies the template'sSchemaVersioninto old data, and the migration is skipped [added, proven against the real ProfileStore]. - Old servers never save newer data. During an update, old and new servers run side by side.
Refuse a higher
SchemaVersion, release the lock untouched, and kick [added]. Publish every place of a multi-place game together (CJ_Oyer, 00:27:33). - Two profiles never save atomically. Editing both without a yield protects memory only (loleris). Escrow both sides, then let one trade-log record decide [added]. Without escrow a crash between the two saves duplicated a Shield and lost a Sword.
- Test against an injected store. Write the data code so
DataStoreServicecan be swapped forMockDataStoreand run several simulated servers with the unmodified ProfileStore [added].
Establish first
- Published, and Studio API access on? Unpublished: every DataStore call throws, so test with
mocks. Published with access on: Studio writes live keys, so use a separate test experience
(Roblox docs) or
ProfileStore.Mock. - What persists where. Player state goes in one profile. Leaderboards use an
OrderedDataStore. Matchmaking and short-lived shared state use MemoryStore. Announcements use MessagingService. - Trading, Developer Products, multi-place? Each adds a stage below.
- Peak CCU, players per server, profile size. Feed
rbx_data.budget. - Data already live? Then keys and store names are frozen; every change becomes a migration step.
Defaults: ProfileStore at the pinned commit, store PlayerData, key Player_<UserId>, a
SchemaVersion field, a 100-entry PurchaseIds log.
Procedure
Modules live in scripts/agentkit/data/ and have no requires. Inline them with
rbx_data.run(studio, code, dm, data=[...]), or build them into a place with
rbx_data.build_place(dir). Full code and results: procedures.md.
- Probe the environment. Goal: know which services answer here. How:
rbx_data.probe_services(studio, "Edit"), then"Server"in a playtest. GATE: the error texts are recorded, and the store choice (real or mock) follows from them. - Design the schema. Goal: a profile that saves as-is and grows safely. How:
DataCheck.report(template)and a maxed sample,DataCheck.key(key, {userId}). GATE: zero error findings, size under 25% of 4,194,304 characters, and a JSON round trip equal to the input. - Plan the budget. Goal: no throttling at peak. How:
rbx_data.budget(players, ccu, kb, saves_per_min). GATE:okis true at peak CCU, and the per-key writes per minute cover autosave plus purchases. - Wire sessions. Goal: one owner per profile. How:
PlayerDatarunsStartSessionAsyncwithCancel, kicks on nil, thenAddUserId, migrate,Reconcile, a kick onOnSessionEnd, andEndSessionon leave. GATE: thesessionssuite passes, and a playtest shows the profile loaded withDataStoreState"NoAccess".
local Players = game:GetService("Players")
local ServerStorage = game:GetService("ServerStorage")
local ProfileStore = require(ServerStorage.Packages.ProfileStore)
local PlayerData = require(ServerStorage.DataKit.PlayerData)
local Migrate = require(ServerStorage.DataKit.Migrate)
local data = PlayerData.new({
ProfileStore = ProfileStore,
Players = Players,
storeName = "PlayerData",
template = { SchemaVersion = 2, Coins = 0, Inventory = {}, PurchaseIds = {} },
migrate = Migrate.new({
latest = 2,
steps = {
-- v1 kept owned items as an array of names; v2 counts them by id.
[2] = function(d: any)
d.Inventory = d.Inventory or {}
for _, item in ipairs(d.Items or {}) do
d.Inventory[item] = (d.Inventory[item] or 0) + 1
end
d.Items = nil
end,
},
}),
})
data:Start()
- Version the schema. Goal: old data upgrades once. How:
Migrate.new{latest, steps}, one fixture per old version. GATE: theschemasuite passes, including the Reconcile trap and the "newer" refusal. - Grant purchases. Goal: exactly one grant per
PurchaseId. How:Receipts.new{getProfile, isPresent, handlers}; assignProcessReceiptin one script. GATE: thereceiptssuite passes with ghost writes, crashes and server changes. - Raw stores. Goal: leaderboards, counters and logs that survive retries. How:
KeyQueue.new(store)with an op id in the value and averifyfunction. GATE: thekeyqueuesuite passes. - Trades. Goal: no item created or lost by a crash. How:
Trade.paidTradingAllowedfor both players (PolicyServiceIsPaidItemTradingAllowed, fail closed),Trade.new{log = KeyQueue.new(tradeLogStore)},trade:Recover(profile)inonLoaded. GATE: thetradesuite passes at every crash stage. - Teleports. Goal: parties arrive together. How:
SafeTeleport.new{TeleportService},TeleportPartyfor groups. GATE: theteleportsuite passes against the fake service; a real teleport needs a published experience. - Audit. Goal: no known mistake left in the code. How:
DataAudit.place(game)in Edit, orrbx_data.py audit place.rbxloffline. GATE: zero error findings outside test fixtures. - Operate. Rollbacks with
PlayerData:Restore(ProfileStoreVersionQuery), final edits inOnLastSave, RTBF templates withrbx_data.rtbf_config: procedures 13 to 15. - Prove and report. Run the offline suites, then the same suites in Studio Edit through
rbx_run, then the playtest checks. List what still needs a published place.
Numbers
| Value | Relative to |
| -------------------------------------------------------------------- | -------------------------------------------------------------- |
| Server read or write: 60 + 40 x players per minute | Per server, default, tunable |
| Experience read 300 + 40 x CCU, write 300 + 20 x CCU per minute | Whole experience, shared with Open Cloud |
| UpdateAsync, so every ProfileStore save, spends 1 read and 1 write | Both budgets |
| Per key: write 4 MB per minute, read 25 MB per minute | Rounded up to whole KB per request |
| Value 4,194,304 characters; key, name, scope 50 | Per key |
| Queue of 30 per request type, then errors 301 to 306 | Per server |
| GetAsync cache 4 s | Per data store instance |
| One version kept per key per UTC hour, 30 days after overwrite | Per key |
| Storage 500 MB + 1 MB x lifetime users | Compressed latest versions |
| ProfileStore autosave 300 s, steal 40 s, assume dead 630 s | Pinned source; assume dead compares os.time() across servers |
| ProfileStore first retry 5 s, then every 10 s | While another server holds the lock |
| Profile load over 5 s | Treat as a bug (loleris) |
| BindToClose budget 30 s | Per server shutdown |
| MessagingService message 1 kB | Per publish |
Quality gates
run_offline.sh: all Lune suites pass, rbx_check reports zero errors in kit, place and snippets.run_live.py: the same suites pass in Studio Edit, and the playtest checks pass.DataAudit: zero error findings outside fixtures.- Console: one "[ProfileStore]: Roblox API services unavailable" line in an unpublished playtest, and no save errors.
- Published test experience (later): two real servers hand a player over in under 5 s.
Common mistakes
| Mistake | Symptom | Fix |
| ---------------------------------------------------------------- | --------------------------------------------- | ---------------------------------------------- |
| SetAsync on PlayerRemoving, no lock | Rollbacks, duplicated items after server hops | ProfileStore through PlayerData |
| Key from player.Name | Data lost after a rename | Player_<UserId> |
| Reconcile before migration | Old fields stranded, new fields empty | Migrate first |
| Retry by recalling the same write | Counters too high | Op id in the value, KeyQueue |
| PurchaseGranted before the save | Paid but not granted after a crash | Receipts |
| Handler that yields
Truncated for display — read the full file on GitHub.
Related Skills
algorithmic-art
177.9kCreating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems.
pptx
177.9kUse this skill any time a .pptx or .potx file is involved in any way — as input, output, or both. This includes: creating slide decks, pitch decks, or presentations; reading, parsing, or extracting text from any .pptx or .potx file (even if the extracted content will be used elsewhere, like in an em…
prospecting
60.1kWhen the user wants to find and qualify prospects for outbound, or asks who to target first, which signal to prioritize, or where to spot buyers with the problem: buying signals, enrichment, verification, account research.
ad-creative
60.1kWhen the user wants to write or judge ad creative, or asks which ad, hook, or angle to run or kill: headlines, primary text, and variations for Google, Meta, LinkedIn, and TikTok, fresh angles when creative fatigues. Test hypotheses name the metric, comparison, and expected direction.
Languages
Trust signals
From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.
