SkillAgentSearch skills...

scenario-roblox-performance

Use when a Roblox experience is slow, laggy, stuttering, crashing or out of memory, or before shipping or updating one: my game lags on mobile, low FPS, frame spikes, server lag or low heartbeat, physics lag, network lag or high KB/s, memory leaks or memory that keeps growing, crashes on phones, lon…

Install / Use

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

Installs into whichever agent you are using.

About this skill
📄

SKILL.md

Installable skill definition

Quality Score

86/100

Category

Other

Supported Platforms

Universal

Our assessment of scenario-roblox-performance

scenario-roblox-performance scores 86/100 on our quality scale, 201st of 354 Other 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-performance 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-performance compared with similar skills

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

SkillScoreStarsUpdatedFormat
scenario-roblox-performance (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-performance?
Run npx skills add scenario-labs/skills --skill scenario-roblox-performance. The install tabs above show the steps for each supported agent.
Which AI agents does scenario-roblox-performance 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-performance 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-performance still maintained?
The repository was last updated 35 days ago, so scenario-roblox-performance is actively maintained.

name: scenario-roblox-performance description: "Use when a Roblox experience is slow, laggy, stuttering, crashing or out of memory, or before shipping or updating one: my game lags on mobile, low FPS, frame spikes, server lag or low heartbeat, physics lag, network lag or high KB/s, memory leaks or memory that keeps growing, crashes on phones, long join or load times, too many parts, instances, draw calls or triangles, MicroProfiler, Script Profiler, Luau heap, Developer Console memory, Scene Analysis, StreamingEnabled tuning, performance budgets, and publishing, releasing an update, restarting servers or rolling back a version." license: MIT

Roblox Performance and Release

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

Expert level here means every claim is a number from the side that hurts, taken before and after one change, and every fix removes work instead of hiding it. Budgets come from the low-end phone, and Studio numbers are labeled as Studio numbers. Release is part of performance: ship with a restart plan and a rollback path, and never publish without 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. Budget for the low-end phone; label Studio numbers as Studio numbers. McNeill's budget card targets a 2 GB phone: 500 draw calls, 500,000 triangles, 1.3 GB, 150,000 instances, 50 KB/s down (RDC 2024). Phones run CPU work about 4 times slower than a desktop. Studio memory "is incorrect in Studio, you need to test live" (McNeill). Studio runs the playtest Server and Client in one process, so server work shows in client frames [added, measured].
  2. Name the cause before the fix. Label every per-frame system with debug.profilebegin and fix the longest lowest-level label (Roblox Learn, MicroProfiler). Studio's execute_luau reaches the Script Profiler, so an agent gets the same answer by code: BasePart.CFrame [C] and the scan label led the lab's server time (measured).
  3. Gate on frame consistency, compared per frame. Fifty-nine 10 ms frames plus one 410 ms frame stutter at "60 fps" (Roblox Learn). Use the lead gate: p95 at most 1.2 times the budget, worst at most 2 times; healthy places read p95 17.2 to 17.4 ms at 60 fps. Compare script time per frame: per-frame work runs more often once a fix raises the frame rate [added, measured].
  4. Remove server work players never see. "Never tween on the server" (Crusherfire). Resizing a welded server part re-replicates the whole assembly (McNeill and Lynn, RDC 2025). Anchoring idle zombies halved one game's server CPU (same talk). Anchoring is not enough when the server still moves the parts: anchored coins spun by the server sent 7.6 to 10 MB/s in Studio, and 12 KB/s once clients spun them (measured; DataSendKbps is in kilobytes per second).
  5. A leak is a rising floor, named by its owner. Healthy memory is a sawtooth (Roblox Learn). Snapshot 3 or 4 times in the same state and trust only rows that keep rising (Crusherfire). Server leaks matter most, because a server outlives hundreds of players (Crusherfire). Destroy does not release a part's connections to other signals: each orb stayed in memory, unparented, held by its Heartbeat closure (measured).
  6. Replication is memory, bandwidth and join time. Tags and attributes on every part replicate to every client: one game's crash rate rose from 3 to 4 percent to 45 percent (McNeill and Lynn). Each server-owned moving assembly costs about 1 KB/s, and a join replicates about 10,000 instances per second (McNeill). Keep server-only data in Luau tables and heavy folders in ServerStorage; tune streaming instead of turning it off (Roblox Learn).
  7. Release is part of performance, and a person ships. Handle ServerRestartScheduled, restart only outdated servers, and investigate a client crash rate above 2 to 3 percent after an update (docs). A rollback is restore, publish, restart: restoring alone publishes nothing (docs). Agents prepare and dry-run; the owner publishes.

Establish first

  • Symptom and side: low client frame rate, server lag (heartbeat under 60, rubber-banding for everyone), crashes or memory, join time, or bandwidth. One owner per symptom.
  • Target devices: the lowest phone you support. Default: a 2 GB phone, 60 fps, budgets in critique.md.
  • Live data: Performance dashboard numbers (crash rate, server memory by age, frame rate by device) if the game is live.
  • Repro: a place or a scripted scenario that shows the problem in a playtest, with a debug spawner for load (N players, N NPCs, N items).
  • Release state: unreleased, live with players, or mid-update; who may publish and restart (always a person).
  • Defaults when unanswered: measure the Server and the Client, change one thing per playtest, no publish.

Procedure

  1. Reproduce under load. Goal: the slow case in a playtest, with numbers on both sides. How: a debug spawner driven by Workspace attributes (N players, N NPCs, N items; McNeill and Lynn), then rbx_perf.measure(pt, 6) on Server and Client at the same server time() (P2). GATE: baseline saved for both sides; the side that fails the frame gate is named.
  2. Audit statically. Goal: costly patterns and counts before playtesting. How: rbx_perf.audit_place(path) in Lune; PerfAudit.all(game) in Edit (P1). GATE: every warn fixed or justified in one line; counts inside the Numbers table.
  3. Name the cause. Goal: the function, label or asset that owns the cost. How: rbx_perf.script_profile(s, side) in the playtest; MicroProf.capture for labels in Edit; SceneScan.all() for triangles, instances and script memory (P3, P6). GATE: the top function or label is named with its ms per frame.
  4. Fix one thing per playtest. Goal: a proven gain, nothing else changed. How: flip one attribute, measure at the same offset, rbx_perf.compare(before, after) with its 5 percent noise floor. Patterns in P4. GATE: the metric the fix touches improves past the noise floor; no other metric gets worse; the frame gate holds on the side that hurts.
  5. Soak for leaks. Goal: memory that never comes down, with its owner. How: PerfProbe.soak, HeapProf.diff and SceneScan UnparentedInstances on the Server over 20 s or more, leak path on and off (P5). GATE: memory category growth and unparented instances stay flat; tracked objects stay bounded.
  6. Check scene, draws and streaming. Goal: the worst view fits the phone budget. How: Client Stats.SceneDrawcallCount and SceneTriangleCount, the batching probe (P7), streaming radii in the project file (P8). GATE: draw calls, triangles and instances inside the Numbers table at the worst view.
  7. Hand the phone list to the owner. Goal: device numbers Studio cannot give. How: the list in P9 and the GUI paths in gui-paths.md. GATE: memory and frame rate from a real phone, or the report says "Studio only".
  8. Release. Goal: an update players survive, with a way back. How: the restart handler (P10), saves from scenario-roblox-data, ShipCheck from scenario-roblox-tooling; the owner publishes and restarts outdated servers. GATE: handler tested in a playtest; the owner's go recorded; the agent never publishes.

Numbers

| Value | Number | Relative to | | ---------------------------- | ------------------------------------------------------------------------------------------------------ | ----------------------------------- | | Scene draw calls | 500 or fewer, UI included | low-end phone, worst view (McNeill) | | Scene triangles | 500,000 or fewer | same | | Shadow draw calls | up to 3 times the scene draws | same | | Client memory | under 1.3 GB; ejections start past about 66 percent of 2 GB | 2 GB phone, on device (McNeill) | | Instances | under 150,000; about 10,000 per second on join | join time (McNeill) | | Replication down | under 50 KB/s | per client (McNeill; Crusherfire) | | Server-owned moving assembly | about 1 KB/s each | McNeill | | Phone CPU | about 4 times a desktop | 10 ms desktop is about 40 ms | | Frame gate | p95 at most 1.2 x budget (20 ms), worst at most 2 x (33.3 ms); healthy places read p95 17.2 to 17.4 ms | 60 fps (lead gate) | | Server memory | 6.25 GiB plus 100 MiB per player; keep under half | docs | | Client crash rate | investigate above 2 to 3 percent | docs | | BulkMoveTo | 0.255 ms against 0.49 ms of per-part writes | Crusherfire's spinner | | Lab, all fixes | Server script 12.0 to 0.36 ms per frame; server sends 6,526 to 11 KB/s; HUD instances 6,002 to 302 | Studio 0.743, desktop, one process |

Quality gates

Measurable:

  • Frame gate on the side that hurts, from PerfProbe.window(...).gate or the lead Stats.frames.
  • rbx_perf.compare rows past the noise floor for the metric each fix touches, with one result file per variant.
  • PerfAudit 0 warn findings, or each one justified.
  • Soak: memory category growth and unparented instances flat; tracked objects bounded.
  • SceneScan and Client Stats: draw calls, triangles and instances inside the Numbers table.
  • Every per-frame system carries a debug.profilebegin label; long-lived threads set debug.setmemorycategory.
  • Restart handler connected in a playtest; P9 phone numbers reported by the owner or marked "Studio only".

Visual: a playtest capture through rbx_review of the worst view before and after (rbx_review.contact_sheet), and the MicroProfiler or Script Profiler capture taken by hand when a claim cites it (gui-paths.md). The full rubric is in critique.md.

Common mistakes

| Mistake | Symptom | Fix | | ---------------------------------------------------------------------------------- | -------------------------------------------- | -------------------------------------------------------------------- | | Gating on fps or Studio memory | Numbers that phones

Truncated for display — read the full file on GitHub.

Related Skills

View on GitHub
GitHub Stars1.0k
CategoryOther
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