SkillAgentSearch skills...

scenario-roblox-expert

Use when an agent builds, fixes or tests anything in Roblox Studio: \"make a Roblox game\", \"Roblox Studio\", a Luau script, \"my Roblox game lags\", agent control of Studio, the Studio MCP server (execute_luau, start_stop_play, screen_capture), Rojo or Script Sync projects, offline Luau checks, pl…

Install / Use

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

Installs into whichever agent you are using.

About this skill
📄

SKILL.md

Installable skill definition

Quality Score

89/100

Category

Other

Supported Platforms

Universal

Our assessment of scenario-roblox-expert

scenario-roblox-expert scores 89/100 on our quality scale, 131st of 354 Other skills we index (top 38%).

Its SKILL.md is 20 KB long, well organised into 13 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.

Substance
30/30
Structure
17/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-expert 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 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-expert compared with similar skills

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

SkillScoreStarsUpdatedFormat
scenario-roblox-expert (this skill)by scenario-labs891.0k35d agoSKILL.md
Agent-Reachby Panniantong100114.0ktodayCLAUDE.md
hyperframesby heygen-com10088.2ktodayCLAUDE.md
rufloby ruvnet10082.3ktodayCLAUDE.md
headroomby headroomlabs-ai10080.5ktodayCLAUDE.md

Frequently asked questions

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

name: scenario-roblox-expert description: "Use when an agent builds, fixes or tests anything in Roblox Studio: "make a Roblox game", "Roblox Studio", a Luau script, "my Roblox game lags", agent control of Studio, the Studio MCP server (execute_luau, start_stop_play, screen_capture), Rojo or Script Sync projects, offline Luau checks, playtests driven by code; when the MCP server lists no Studio, a playtest hangs, or 2019 to 2023 Roblox code breaks; or when a Roblox brief (UI, data, networking, combat, monetization, assets, performance) must go to the right scenario-roblox-* specialist." license: MIT

Roblox expert (technical director and agent protocol)

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

Expert Roblox work is a loop run against evidence: set the budget, build one stage, measure it, look at it, fix it, advance. An agent without a mouse gets there through Studio's built-in MCP server, offline checks and text files, passing only on a parsed result and never on one signal alone. This skill is that protocol, the shared toolkit every scenario-roblox-* skill calls (scripts/), and the map of the team. 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.

Status (2026-10-18): the toolkit ran live in Studio 0.743, 36 live tests and 16 offline tests, all pass (references/procedures.md). run_headless is live run pending: it needs a machine with no interactive Studio.

Stance (the expert delta)

  1. Pass on a parsed result, never on tool text. execute_luau returns only the first return value, and prints go to the Output log (observed). rbx_run.run returns ok, result, error, output with your chunk's line numbers. "Audit the results" of anything an agent made over the MCP (Roblox IAS Q&A, KnFJl6z5UN0 [00:21:23]).
  2. One place per agent, opened once, never closed by an agent. Never run code in a window you did not open; the server asks you to confirm with the user before modifying their game. A SIGTERM to a place hung its window and hid every Studio from the server (observed). Closing places belongs to the orchestrator, with the user's agreement.
  3. Frame time against a budget, on the target. Consistent frame time beats average FPS (Andrew, XLCZfGEm9tU [00:02:12]). Triage: works, real device, frame rate, Stats, then MicroProfiler (McNeill, rwLEnBtXr30 [00:29:19]). Studio memory "is incorrect" (McNeill, cWDNVvOh4o0 [00:28:25]): it read 3,800 MB in a small playtest here.
  4. Look AND check. Every visual change gets captures from fixed cameras, image_checks, a before and after compare, and a contact sheet you open. Feel cannot be automated (RDC 2026, vumAuOqSmNA [00:29:36]); AI "doesn't automatically have taste" (SmartyRBX, da-wHJpNhBo [00:07:35]).
  5. Small steps, red before green. One feature per prompt (SmartyRBX, 0ENeVVC9QT0 [00:10:26]). Follow a working answer with a security review, and test death and respawn (SimTek, -0H6JRtrA2Y [00:03:53, 00:06:42]). Write the Spec test first and watch it fail.
  6. Text files, Git, and a gate before Studio. A CI gate on type and lint errors catches "90 percent of what breaks a game" (CJ_Oyer, gapG2tH-etI [00:12:50]); Git is the safety net (Roblox Learn, v8r1d80DxOY [00:00:45]). Gate with rbx_check (luau-lsp with Roblox definitions), not bare luau-analyze.
  7. Know what persists. An Edit change lives in the open session until someone saves, and no MCP tool saves; Server writes vanish when play stops (L24, L25). A Rojo reconnect deletes Studio-only instances without $ignoreUnknownInstances (Distracted Games, Zhl_NAPMztY [00:44:28]).
  8. Be honest about GUI-only tools. The Animation Editor, terrain brushes, Avatar Setup, the Accessory Fitting Tool, Creator Hub dashboards and publishing are GUI steps. Give the substitute (Terrain:WriteVoxels, KeyframeSequenceProvider:RegisterKeyframeSequence, AvatarCreationService:ValidateUGCAccessoryAsync) or the GUI path (references/gui-paths.md). Never publish, upload or spend Robux without the user's go.

Channels

| Channel | Use for | Cost (measured) | Rules | | ----------------------------------------------- | ----------------------------------------------------------- | --------------------------------- | ------------------------------------------------------- | | Studio MCP, Edit (rbx_run.run) | build, audit, inspect, edit scripts | 67 ms per call; first open 18.3 s | your own place; chunks yield every 1,000 items | | Playtest (rbx_play.Playtest) | Server and Client code, keys, walking, mouse, play captures | ready in 4.2 s | one server, one client; stops even after an exception | | Offline (rbx_check, Lune, lune_audit) | gate before Studio, CI, pure-logic tests | seconds | Lune has no physics, no network | | Files (Rojo, Script Sync) | durable code in Git | rojo build 0.04 s | never rebuild a .rbxl that Studio holds open | | Headless RunScript (rbx_run.run_headless) | CI with no interactive Studio | about 6 s per run | refuses while any Studio runs | | Open Cloud Luau Execution | CI assertions on a published place | 5 tasks per minute | API key and the user's go; no physics, nothing persists |

Concurrency: at most RBX_MAX (default 3) agents hold a place through rbx_env.place_slot(). Each place is its own Studio process of about 2.9 GB, and every window renders all the time. open_place waits while RBX_MAX_PLACES (default 4) place windows are open machine-wide, GPU use or GPU memory is above 85%, or RAM is above 75%. Close a place as soon as its run ends. Several StudioMCP proxies share one port, so Studio.call retries for 45 s while the host proxy changes.

Establish first

Ask once, then run:

  • target devices and the lowest one (default: phone, 60 fps, 16.67 ms);
  • players per server and genre;
  • Rojo, Script Sync or Studio-only;
  • whether Server Authority or streaming is wanted (StreamingEnabled is on in new places);
  • which place is the agent's own, and the deliverable.

Then rbx_env.doctor() and an Audit.all(game) of the starting place. Write the budget, sync tool, data model plan and owners into the plan.

The expert loop

  1. Brief in numbers. Budgets per device, players, memory, art style. GATE: every later check has a number.
  2. Place. new_place then open_place inside place_slot, once. GATE: open_places() lists it; Audit tally has no error.
    • new_place overwrites <dir>/default.project.json: dir is a new folder of your own, never the user's project.
    • Existing game: ask the user to save first, since edits in their open window are not on disk. Merge a copy of the saved place with the code build (scenario-roblox-tooling P15, merge_place, any repository) and open the merge, never the user's file.
    • Edit a worktree or copy of their sources: their rojo serve syncs src/ into their window.
  3. Baseline. Audit, Spec tests that fail first, captures from fixed cameras, Stats.frames in a playtest. GATE: numbers recorded, sheet opened.
  4. Build one stage with idempotent chunks or files; route domain work to its owner (below). Adding instances to the open place: procedures.md P2.
  5. Measure. rbx_check 0 errors, Spec all green, Audit clean, Stats.frames on Server and Client within the frame gate: p95 at most 1.2 x the frame budget (20 ms at 60 fps) and worst at most 2 x (33.3 ms). Heartbeat steps jitter around the vsync interval, so a healthy 60 fps place reads p95 17.2 to 17.4 ms and a bare 16.67 ms gate fails it; a dropped frame reads about 33 ms.
  6. Look AND check. Same cameras, image_checks ok, compare changed where it should, contact sheet opened, judged with the owner's critique.
  7. Fix before advancing, one change at a time.
  8. Deliver with evidence: Verified (what ran, result file, numbers, frames) and Assumed (not run). List what a human must still play for feel.

Toolkit (scripts/, the contract for every scenario-roblox-* skill)

import sys
from pathlib import Path
sys.path.insert(0, str(Path(__file__).resolve().parents[1].parent / "scenario-roblox-expert" / "scripts"))

| Module | Main calls | Returns | | --------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------ | | rbx_env | doctor(), new_place(dir, name, template, src), open_place(path), open_places(), place_slot(), machine_load(), wait_for_gpu() | dict; Path; bound Studio; [{id, name}]; slot index; percents | | rbx_mcp | Studio(place=...): .call(tool, args), .luau(code, dm), .capture(png, extra), .studios(), .tools() | MCP result dict; text; Path | | rbx_run | run(studio, code, dm="Edit", kit=[...]), run_headless(place, code, kit) | {ok, result, error, output} | | rbx_play | Playtest(studio): .server(code, kit), .client(code, kit), .wait_for, .press(key, hold), .walk_to([x, y, z]), .keys, .mouse, .console, .capture, .mode | rbx_run dicts; tool text | | rbx_check | check(paths, code, sourcemap, selene, stylua, solver="both") | {ok, errors, warnings, tools}, findings tagged old or new solver | | rbx_review | image_checks(png), compare(a, b), contact_sheet(pngs, out) | flags and ok; changed_fraction; path | | AgentKit | Audit.all(game), Stats.snapshot(), Stats.frames(s), Stats.diff, Spec.new() | findings and tally; numbers; {passed, failed, total} |

Full signatures, return shapes and tool arguments: references/procedures.md section 1. Domain code goes in each sibling's scripts/rbx_<domain>.py and scripts/agentkit/<domain>/. rbx_env.close_place is orchestrator-only and refus

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