agentsclimarketplace
Sign in

Roblox performance optimization

Skill AshExplained/roblox-skills/roblox-performance-optimization

Analyze and optimize Roblox scene and script performance. Use for mobile frame rate, memory, instance count, rendering cost, physics, particles, lighting, asset budgets, streaming, leaks, and using the rbx-scene-analysis workflow.From its SKILL.md

Install
npx -y skills add AshExplained/roblox-skills --skill roblox-performance-optimization

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

2.1 KB, 398 tokens by cl100k_base, as published. Nobody here has run it

Roblox Performance Optimization

Goal

Keep the experience smooth on lower-end phones. Favor measurable fixes over visual guesses.

Use The Scene Analysis Skill

When available, invoke rbx-scene-analysis before deep performance work. Use it to inspect rendering, memory, instance composition, unparented instances, and animation or audio asset usage.

MCP Workflow

  1. Confirm Studio state with get_studio_state.
  2. Use search_game_tree and inspect_instance to identify heavy hierarchies.
  3. Use execute_luau for targeted counts, tag scans, memory snapshots, or property audits.
  4. Use screen_capture to preserve before/after visuals.
  5. Playtest with start_stop_play and check get_console_output.

Optimization Targets

  • Instance count and deeply nested hierarchies.
  • Unanchored parts causing physics cost.
  • Excessive constraints, touched events, or per-frame loops.
  • Large textures, too many unique materials, and high-poly meshes.
  • Particle emitters with high rate/lifetime combinations.
  • Dynamic lights, shadows, post-processing, and expensive transparency.
  • Scripts that connect events repeatedly or leave stale connections.
  • Workspace content that should stream or load later.

Mobile Budget Habits

  • Build the first area to be visually strong but technically cheap.
  • Prefer fewer meaningful effects over many constant effects.
  • Use Level of Detail thinking for distant props.
  • Keep UI lightweight and avoid per-frame layout work.
  • Test phones and tablet-like viewport sizes, not only desktop Studio.

Report Format

Return:

  • Biggest performance risks.
  • Evidence from scene analysis, instance inspection, console output, or captures.
  • Fixes ranked by likely player impact.
  • Verification steps and any tradeoffs.

Next

Confirm the gains on-device with roblox-mobile-playtest, and re-run roblox-playtest-qa to make sure nothing regressed.

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.

Gives 0 of the 12 instructions most research analysis skills give in 398 tokens

Counted across 1,063 of the 1,754 authors here whose files we hold, read 2026-08-07

  • Generate a markdown reportin 32 of 1063, across 23 files
  • Cite each claim's sourcein 30 of 1063, across 15 files
  • Define the ideal customer profilein 20 of 1063, across 2 files
  • Search for companies matching the criteriain 20 of 1063, across 2 files
  • Assign a fit score from one to tenin 20 of 1063, across 2 files
  • Analyze the codebase to understand the productin 19 of 1063, across 1 file
  • Ask clarifying questions about the value propositionin 19 of 1063, across 1 file
  • Look for signals of immediate needin 19 of 1063, across 1 file
  • Identify the target decision maker rolein 19 of 1063, across 1 file
  • Suggest a personalized contact strategyin 19 of 1063, across 1 file
  • Provide conversation starters for outreachin 19 of 1063, across 1 file
  • Format results in a scannable markdown templatein 19 of 1063, across 1 file

Said here and by no other author read

  • invoke rbx-scene-analysis before deep performance work
  • confirm studio state with get_studio_state
  • identify heavy hierarchies using search_game_tree and inspect_instance
  • use execute_luau for targeted counts and audits
  • preserve before and after visuals with screen_capture
  • playtest with start_stop_play and check get_console_output

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.

Keep looking

Skills are one crate of 326,852. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.