Skip to content
SkillModel-led2,230 tokens in use

roblox-datastores

Helps an agent persist Roblox player data safely: load on join, save on leave and shutdown, UpdateAsync, session ownership and leaderboards.

9,684 stars on the repository Apache License 2.0gamedev-skills/awesome-gamedev-agent-skills · skills/other-engines/roblox-datastores
npx skills add gamedev-skills/awesome-gamedev-agent-skills
View source

Install command as written in the repository's README

Skill label

measured from its files

What installing roblox-datastores costs

91tokens idle
2,230tokens in use
4,035tokens, up to

Idle is what sits in context while the skill is installed. In use is its instructions, loaded when it runs. Up to adds the files its instructions link. Counts are approximate, made offline with cl100k_base.

Model dependence Model-led

Script-ledMixedModel-led

Mostly instructions, so how well it works depends on the model that follows them.

This describes the skill's structure, how much of it is scripts. It does not say how well it works.

Touches

shelldetected

Declared tags come from the skill's frontmatter; detected ones from its scripts, its code blocks and the commands it names in inline code. This is detected, not audited.

How it scores

Quality

How well the skill is written, counted from its own files: its frontmatter, its steps, examples, stated output and constraints, its size and whether every file it ships is one it names.How we score it →
Excellent
  • Frontmatter8/15
  • Structure25/25
  • Examples12/15
  • Output10/15
  • Size15/15
  • Resources15/15

Security

Starts at 100 and loses points for each thing in the skill's files that a reader should look at first.How we score it →
Excellent
  • Runs shell commands−5

    does this on the machine, and the frontmatter does not say so

    SKILL.md, line 41

Repository health

Pre-computed score based on development activity, maintenance, community, maturity, and trend momentum.How we score it →
Good
  • Development activity92
  • Maintenance96
  • Community60
  • Maturity24
  • Momentum40

This skill helps an agent write Roblox DataStoreService code that neither loses nor duplicates player data. It looks for an existing persistence layer first, keys data by UserId, wraps every call in pcall and refuses to save after a failed load so defaults never overwrite real progress.

It includes patterns for loading on join, saving with UpdateAsync, saving on leave and in BindToClose, retrying only what is safe to repeat and building a leaderboard with OrderedDataStore. A gotcha list covers server races, yields inside UpdateAsync, throttling, stale reads and values that cannot be stored.

What You Get

  • An eight-step workflow from finding the existing persistence layer to a join, change, leave and rejoin check
  • Luau patterns for load on join, save with UpdateAsync, save on leave and BindToClose, a retry helper and an ordered leaderboard
  • Shell searches that list every DataStore call, the shutdown handler and each SetAsync on a player key for manual review
  • A gotcha list for overwritten data, cross-server races, side effects in callbacks, throttling, stale reads and non-serializable values

Common Use Cases

  • Finding why player data was lost or rolled back
  • Stopping items from duplicating after a teleport
  • Fixing too many requests errors from saving on every change
  • Building a top ten leaderboard

What Makes It Unique

The skill gates saving on a successful load, so a network failure is never mistaken for a new player. It explains why an UpdateAsync callback can run more than once and must not grant items, and it separates retry-safe writes from increments that could apply twice. Version notes record current request budgets and limits.

Under The Hood

The agent loads the SKILL.md and, when needed, a reference on sessions and limits. It runs ripgrep searches over the project’s source to list DataStore calls and edits Luau server scripts. The code it writes makes DataStore network requests when the game runs. For its final check it can use a connected Roblox Studio MCP server to play, change a value, stop, replay and read the value back; this needs a separate test place with Studio access to API services turned on, because Studio reads and writes live data. Without that server it asks you to do the join, change, leave and rejoin steps and report what you see.

Join founders building with open source

Opinionated takes, migration guides, cost-saving tips, and insights from the open source ecosystem.

Subscribe on SubstackJoin 750+ subscribers