scenario-roblox-tooling
Use when setting up or repairing a Roblox team project outside Studio: Rojo or Script Sync, Wally packages, Rokit pins, luau-lsp type checking, Selene, StyLua, unit tests in Lune or the engine, GitHub Actions CI on pull requests, Open Cloud place publishing, Luau Execution or API key scopes, merging…
Install / Use
npx skills add scenario-labs/skills --skill scenario-roblox-toolingInstalls into whichever agent you are using.
SKILL.md
Installable skill definition
Quality Score
Category
AutomationSupported Platforms
Our assessment of scenario-roblox-tooling
scenario-roblox-tooling scores 86/100 on our quality scale, 1793rd of 2,758 Automation skills we index.
Its SKILL.md is 23 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.
Maintenance, license and trust
- The repository was last updated 35 days ago, so scenario-roblox-tooling 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 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-tooling compared with similar skills
All 4 of these similar skills score higher than scenario-roblox-tooling; compare them before choosing.
| Skill | Score | Stars | Updated | Format |
|---|---|---|---|---|
| scenario-roblox-tooling (this skill)by scenario-labs | 86 | 1.0k | 35d ago | SKILL.md |
| Agent-Reachby Panniantong | 100 | 114.0k | today | CLAUDE.md |
| rufloby ruvnet | 100 | 82.3k | today | CLAUDE.md |
| headroomby headroomlabs-ai | 100 | 80.5k | today | CLAUDE.md |
| Claude-Code-Game-Studiosby Donchitos | 100 | 40.6k | 12d ago | CLAUDE.md |
Frequently asked questions
- How do I install scenario-roblox-tooling?
- Run
npx skills add scenario-labs/skills --skill scenario-roblox-tooling. The install tabs above show the steps for each supported agent. - Which AI agents does scenario-roblox-tooling 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-tooling 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-tooling still maintained?
- The repository was last updated 35 days ago, so scenario-roblox-tooling is actively maintained.
Skill content
View source on GitHubname: scenario-roblox-tooling description: "Use when setting up or repairing a Roblox team project outside Studio: Rojo or Script Sync, Wally packages, Rokit pins, luau-lsp type checking, Selene, StyLua, unit tests in Lune or the engine, GitHub Actions CI on pull requests, Open Cloud place publishing, Luau Execution or API key scopes, merging builders' Team Create map with code from files, Studio plugins, or proving a pipeline works. Also when users say "set up Rojo", "CI for my Roblox game", "run tests in CI", "publish from GitHub", "Script Sync stopped syncing", "Rojo deleted my parts", "wally packages not found", "luau-lsp can't find ReplicatedStorage", "selene errors on types", "the release wiped the map" or "my LocalScript doesn't run"." license: MIT
Roblox Tooling and Build Pipeline
Target line: Roblox Studio (October 2026 build) on macOS, driven through the scenario-roblox-expert toolkit.
Expert level here means a repository that rebuilds every place from empty, a gate seen failing before it is trusted, and one spec format for Lune and the engine. Only an approved release job publishes.
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)
- Build the place from the repository. Never publish a dev place edited by hand: a deleted object would ship silently (CJ_Oyer, Connect 2023, 00:42:51).
- The gate exists to fail. Type and lint errors block the publish; that catches the typo class of bugs, "90 percent" in his words, not design bugs, so keep a playtest before big releases (CJ_Oyer 00:12:50 to 00:13:55). [added] Plant one fault per check and watch exactly that step turn red before trusting green.
- Only the pipeline publishes, all places together. People and agents get repository access (CJ_Oyer 00:22:44). An old place reading a newer DataStore shape errors, so every place ships in one run (00:26:27). [added] Upload all places as Saved first, then promote all to Published.
- One sync tool per folder. Script Sync suits code-only, Studio-centric teams; Rojo suits whole-project builds, Wally and CI (Distracted Games, 2026; Script Sync docs). Rojo can still run beside Script Sync as a sourcemap generator only (xlxnmAFmu6c 00:12:57).
- Packages are code you ship. Wally packages can arrive mis-packaged, with no entry module;
require the real entry (
lib) or copy the module (xlxnmAFmu6c 00:01:44). ShipCheckpackage-entryfails on such a package. - One spec format, two runtimes. [added] A spec requires its subject by string
(
require("./Damage")), so the same file runs underlune runand in Studio or Open Cloud. Pure logic runs in Lune in milliseconds; engine facts run in the engine. - Verify by code, not by eye. The official setup video has the agent touch every synced folder,
read
InstanceFileSyncService:GetStatusand playtest before any commit (Roblox Learn, 2026, 02:45 to 03:34). Script Sync can stop silently (SmartyRBX, 00:12:19): poll status. - Typed Luau for agents. roblox-ts loses Studio editing, Luau line numbers and fast API typings (Adam, Last Level Studios, 00:06:01); agents driving Studio through MCP stay on strict Luau.
Establish first
- Sync tool in use: a
*.project.json(Rojo) or Script Sync links (InstanceFileSyncService:GetAllInstances()not empty). Never add the second one on the same folder. - Who owns the map: Rojo cannot live-sync Terrain, CSG or
MeshPart.MeshId, so builders' work reaches the release as.rbxmxfiles in the project or as a base place merged with the code build (P15). - Who edits what: builders in Team Create on a build experience; scripters in the repository, one owner per synced script, since two people syncing one script overwrite each other (Script Sync docs); only the release job holds the production key (P16).
- Places of the experience: universe id, place ids, start place. They go in
places.json. - CI host and keys: GitHub Actions by default. The user creates every key; an agent never creates, prints or stores one. One key per job, only its scopes (table below); for a group experience, keys on a dedicated account with a minimal group role; IP restriction off for GitHub-hosted runners, whose IPs change (API keys guide; CJ_Oyer 00:38:26).
- A test universe separate from production for engine tests [added]: Luau Execution DataStore calls hit real data.
- Defaults when unstated: the template below,
emitLegacyScripts: false, client entry as a RunContext Client Script inReplicatedStorage.Client, strict mode, tabs.
Procedure
Full code, tests and results: procedures.md. Runner script: rbx_tooling.py.
- Scaffold.
python3 scripts/rbx_tooling.py scaffold <repo> --name <game>, thenrokit installandwally install. It copies the template and the TestRunner and ShipCheck modules intotools/testkit/. GATE:rbx_tooling.py lint <repo>/default.project.jsonreports no error (it also catches properties Rojo drops silently). - Local gate.
rbx_tooling.py gate <repo>runs the CI steps in order: Wally,rojo sourcemap --include-non-scripts, luau-lsp twice, Selene, StyLua, Lune tests, ship build, ShipCheck. luau-lsp 1.70.1 runs the old solver unless given--flag:LuauSolverV2=true, while Studio uses the new one for nonstrict scripts, so the gate runs both (P2). GATE: every step exits 0, then each planted fault (type, solver-only, lint, format, failing spec, test in release) fails exactly its steps. The gate needs this skill's scaffold (tools/,ship.project.json); in another repository, gate with the lead'srbx_checkandlint_project. - Engine tests in Studio. Build a dev place and open it once with
rbx_env.open_placeinsiderbx_env.place_slot()(binding: the lead's procedures). Thenrbx_tooling.check_target(s)checks throughlist_roblox_studiosthat one window is bound and holds a test place (P18); allowlist the Studio MCP tools first, or each call stalls on a prompt (coding harness tutorial). Run the CI one-liner throughrbx_run.runin Edit, then on the Server in aPlaytest:
GATE:return require(game:GetService("ServerStorage").TestKit.EngineTests)()failed == 0andtotal > 0. A spec that fails to load counts as a failure. - Client placement probe. Before trusting a layout, count client script runs in a playtest (P7). GATE: each entry runs once per player.
- Sync health (Script Sync teams).
rbx_tooling.run_kit(studio, "return SyncCheck.run(game)", kit=["SyncCheck"])with SyncCheck, andrbx_tooling.lint_scriptsync(folder)on disk. GATE: no error findings; every root reads SyncedAsRoot. - CI. Commit ci.yml: a
staticjob with no secrets on every pull request, and anenginejob for pushes and same-repository pull requests. The engine job checks its key and scopes (tools/check_key.luau --require-scope ...), uploads the dev build as a Saved version of a test place, and runs the one-liner through Open Cloud Luau Execution (tools/cloud_luau.luau --expect-tests).- A place accepts 10 unfinished tasks, then HTTP 429 (Open Cloud reference): engine jobs share
one concurrency group and
cloud_luauretries 429 with backoff. GATE:rbx_tooling.check_workflowok and actionlint 0; the first pull request is green, and a planted fault turns it red.
- A place accepts 10 unfinished tasks, then HTTP 429 (Open Cloud reference): engine jobs share
one concurrency group and
- Release. publish.yml runs on a tag or by
hand in the protected
productionenvironment: key check,tools/place_versions.luau(newest Version History number of each builders' place), ship build,tools/merge_place.luau --manifest places.json --live-versions ...(each base place plus the code, then ShipCheck), thentools/publish.luau --manifest places.json --published. P10 quotes the whole job.- Builders hand over with File > Save to File into
assets/<place>.rbxland record that save's Version History number asbaseVersion(P15). An outdated copy silently ships the old map, so the merge refuses abaseVersionolder than the newest version. - The place publishing API does not update PartOperation (CSG), SurfaceAppearance, EditableImage,
EditableMesh or BaseWrap content (place publishing guide):
merge_placeexits 2 on them and keeps the merged file for a person to publish from Studio. - Restarting outdated servers (
tools/restart_servers.luau, Open Cloud:restartServers) runs only when a manual run setsrestart_servers. GATE: merge exit 0 withfreshnesschecked anddroppedandbaseScriptsreviewed; Saved versions exist for every place before any Published upload. Agents run phase 1 or--dry-runonly, and never restart servers.
- Builders hand over with File > Save to File into
- Studio command line on a CI Mac. Use the lead's wrapper
rbx_run.run_headless(place, code): it refuses while any Studio runs and parses a result marker (no live run yet).RobloxStudio --task RunScriptitself (4 runs here, 6.0 s each) exits 0 even on a runtime error and, on macOS, took over the open Studio and closed its window (P12). GATE: the parsed marker, never RunScript's exit code.
API keys, one per job; scope strings from the Open Cloud reference; each job's
check_key --require-scope list matches its row (P13):
| Job | Scopes |
| -------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------- |
| ci.yml static | no key |
| ci.yml engine, test experience | universe-places:write (Saved upload of the test place) and universe.place.luau-execution-session:write (Luau Execution) |
| publish.yml, production | universe-places:write; universe:write to restart servers; universe.place:read (builders' experience) for the stale base check |
| check_key (introspect) | none extra |
Where each check runs. The Studio column needs Studio's MCP server on: toggle in the lead's gui-paths.md.
| Check | Lune or CLI (CI) | Studio through MCP | Open Cloud |
| ------------------------------------ | ------------------------ | ------------------------- | ----------------------------------------- |
| Types, lint, format | yes | no | no |
| Pure specs | yes, milliseconds | yes | yes |
| Engine specs | no | Edit, Server, Client | yes, no physics, place scripts do not run |
| Release tree audit, base place merge | ShipCheck, merge_place | ShipCheck on game | no
Truncated for display — read the full file on GitHub.
Related Skills
Agent-Reach
114.0kGive your AI agent eyes to see the entire internet. Read & search Twitter, Reddit, YouTube, GitHub, Bilibili, XiaoHongShu — one CLI, zero API fees.
ruflo
82.3k🌊 The original agent harness. Deploy intelligent multi-player swarms, coordinate autonomous workflows, and build conversational AI systems. Features adaptive memory, self-learning intelligence, federation, vector RAG integration, and native Claude Code / Codex / Hermes and many more Integrated
headroom
80.5kCompress tool outputs, logs, files, and RAG chunks before they reach the LLM. 20% fewer tokens for coding agents, 60-95% fewer tokens for JSON, same answers. Library, proxy, MCP server.
Claude-Code-Game-Studios
40.6kTurn Claude Code into a full game dev studio — 49 AI agents, 75 workflow skills, and a complete coordination system mirroring real studio hierarchy.
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.
