scenario-unity-performance
Use when a Unity 6.3 game is slow or stutters: low fps, frame spikes, hitches when entering areas or on first effects, GC spikes, too many draw calls or SetPass calls, CPU vs GPU bound questions, Profiler, Profile Analyzer, Memory Profiler, Frame Debugger or Project Auditor work, GPU Resident Drawer…
Install / Use
npx skills add scenario-labs/skills --skill scenario-unity-performanceInstalls into whichever agent you are using.
SKILL.md
Installable skill definition
Quality Score
Category
OtherSupported Platforms
Tags
Our assessment of scenario-unity-performance
scenario-unity-performance scores 86/100 on our quality scale, 206th of 354 Other skills we index.
Its SKILL.md is 20 KB long, well organised into 11 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-unity-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 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-unity-performance compared with similar skills
All 4 of these similar skills score higher than scenario-unity-performance; compare them before choosing.
| Skill | Score | Stars | Updated | Format |
|---|---|---|---|---|
| scenario-unity-performance (this skill)by scenario-labs | 86 | 1.0k | 35d ago | SKILL.md |
| algorithmic-artby anthropics | 100 | 177.9k | 2mo ago | SKILL.md |
| pptxby anthropics | 100 | 177.9k | 2mo ago | SKILL.md |
| prospectingby coreyhaines31 | 100 | 60.1k | 11d ago | SKILL.md |
| ad-creativeby coreyhaines31 | 100 | 60.1k | 11d ago | SKILL.md |
Frequently asked questions
- How do I install scenario-unity-performance?
- Run
npx skills add scenario-labs/skills --skill scenario-unity-performance. The install tabs above show the steps for each supported agent. - Which AI agents does scenario-unity-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-unity-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-unity-performance still maintained?
- The repository was last updated 35 days ago, so scenario-unity-performance is actively maintained.
Skill content
View source on GitHubname: scenario-unity-performance description: "Use when a Unity 6.3 game is slow or stutters: low fps, frame spikes, hitches when entering areas or on first effects, GC spikes, too many draw calls or SetPass calls, CPU vs GPU bound questions, Profiler, Profile Analyzer, Memory Profiler, Frame Debugger or Project Auditor work, GPU Resident Drawer or SRP Batcher setup, LOD and Mesh LOD, shader warm-up and variants, memory or VRAM budgets, IL2CPP and build size, or proving a fix with numbers from a player." license: MIT
Unity performance (performance engineer)
Expert performance work is a measurement discipline: a budget in milliseconds, the bounding thread
named before any change, the biggest measured cost fixed first, structure before tuning, and every
fix proven with before/after numbers from a development player. An agent does all of it headless:
AgentProfile in Editor Play mode to iterate, PerfProbe in a batch-mode player for verdicts,
PerfCapture to attribute costs from a Profiler capture, metal_trace for GPU time, PerfBuild
for size. Target: Unity 6000.3.21f1, URP 17.3, macOS Apple Silicon. 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-unity-expert (channels, review loop, 6.3 traps, ut_* toolkit).
Stance (the expert delta)
- Name the bound before touching anything. "If you speed up the GPU when your profile looks like this it's not going to run any faster" (Peter Hall, Unity Profiler team, _cV1B2hqXGI [00:05:50]). Observed: removing 1.36 MB of garbage per frame did not move a frame bound by 5,946 SetPass calls. GPU bound needs GPU timing; the Frame Debugger has none (Hall [frame 00:09:18]).
- Players decide, the Editor iterates. The authority is a development build on the lowest target device (profiling e-book p. 18). GRD: 4.4x in a 2M-instance stress test, 2.07x in the Editor but 1.45x standalone in a real game (Oc6T4hh5gaI [frame 00:12:41]); here the Editor swung 1.5x to 3.0x, players 1.9x to 2.8x on a stress fixture. Forecast about 1.5x.
- GC.Alloc sample time is not the cost. Unity records only timestamp and size (e-book p. 27):
54,021 allocations shown as 1.01 ms caused 19.97 ms of
GC.Collect(Hall [frame 00:21:52]). Observed: 27,000 allocations per frame displayed 0.8 to 1.1 ms; the allocating code cost 3.8 to 5.4 ms. Count bytes and calls, measure collections, target 0 B per gameplay frame, and keep the probe itself allocation-free (git-amend ham_w48aRJ4 [00:11:30]). - 6.3 URP draw calls = SRP Batcher + GPU Resident Drawer; the 2024 advice is Built-in-only.
Material "Enable GPU Instancing" off, static batching off, no MaterialPropertyBlock (6.3 Manual
table). GRD silently does nothing unless BatchRendererGroup Variants = Keep All and every
renderer of the URP asset is Forward+ or Deferred+ (URP 17.3 source, observed). Then prove
coverage: GRD draws are named "Hybrid Batch Group" in the Frame Debugger (GUI editor only), each
other draw is a renderer that fell out (MPB, LPPV, realtime GI, non-DOTS shader, skinned; 6.3
Manual); headless, check eligibility per renderer after
Start. - Data layout first; spreading work over frames hides cost. 200,000 objects: MonoBehaviour Update 27 ms to 0.13 ms through manager, structs, Burst, SoA; "it's just spreading the work around" (Jason Booth, NAVbI1HIzCE [00:06:38]-[00:18:17]).
- Attribute every hitch before fixing it, with markers kept in code. Streaming and spawn
systems carry their own ProfilerMarkers and counters; Deep Profile only finds what fills a gap
(Hall [00:18:39]-[00:19:12]). Compiles show as
Shader.CreateGPUProgram(warm a traced GraphicsStateCollection during loading, Nicolas Borromeo CmD8MVGkDxQ [00:11:14]-[00:14:35]); here warm-up removed all 18 first-use compiles, yet the first frame stayed about 250 ms onMono.JIT. - Resident memory kills, untracked usually does not. 0.75 GB untracked was 140 MB resident (Borromeo [00:32:22]); Editor memory is about 5x the player's (Uuzd39AjFWQ [00:10:03]). On a laptop, paging and VRAM overflow are stutter causes of their own.
- Counts are exact, times drift [added, observed]. On a shared machine (load average 50 to 210 here), interleave A/B runs and require a consistent sign.
Establish first
Target platforms and min-spec device per tier; frame budget (16.67 ms desktop, mobile x 0.65);
resolution and quality tier; what may change (code only, or art, design, feel); a repeatable
benchmark, time-based when judging streaming (a fixed step per frame reaches boundaries sooner after
a speed-up) [added]; scripting backend and build type; the machine actually measured (discrete GPU,
on power; probe JSON device) [added]. Defaults: PC-tier URP asset, 60 fps, 1920x1080, development
Mono player for iteration, IL2CPP release for size.
Workflow
- Budget and benchmark. GATE: a baseline CSV.
- Iterate in the Editor.
ut_perf.profile(render=False isolates scripts),ab_profilefor time deltas. GATE: numbers labeled "Editor, iteration". - Static baseline.
PerfRendering.Audit(batching, GRD eligibility per renderer, graphics jobs per platform, Build Profile, stack traces, upload buffer, culling),lint_scripts, Project Auditor (project_auditor, Major first,triage_auditorkeeps per-frame lines),PerfAudit.AudioImport,bundle_duplicates. GATE: findings triaged by call frequency. - Measure the player.
build_player(development=True),run_player(..., shot=png, markers=[...]). GATE:draw_calls> 0, PNG opened,budget_check. - Classify the bound. Capture wait markers (
capture_player,analyze_capture), longest vs median frame. GPU:metal_trace+metal_gpu_frames(GPU busy and per-pass ms; Rendering Debugger Display Stats in the GUI), then the pixel-bound test (4K vs 1080p, render scale). GATE: bound named with a number. - Attribute.
attribute_spikes(your markers, GC.Collect, compiles, MeshCollider cooking, synchronous reads, physics steps),physics_catchup,memory_budget,density_check, allocations per block (AllocScope,Is.Not.AllocatingGCMemory()), GRD coverage (PerfFrameDebug.Captureor the window). GATE: top three costs named, no unexplained spike. - Fix one thing at a time, structure first. Scripts: allocations, managers, then Burst. Render
CPU: Material Variants, SRP Batcher shaders,
EnableGpuResidentDrawer, one camera, Split graphics jobs on DX12/Vulkan. GPU: dynamic resolution or STP, depth priming and less transparency, LOD where triangles are pixel-sized, post-processing on a fixed slice; shadows with scenario-unity-rendering-lighting. Hitches: async loads, prewarmed pools, PSO warm-up in loading, baked MeshColliders, audio load types, no duplicated bundle dependencies. GATE:compare_lineshows the target down, nothing else up, image parity. - Ship config. IL2CPP release, stripping and code generation chosen, variants stripped against
the used set (P15), flags through
BuildPlayerOptions(platform profiles share settings). GATE: build succeeded, size explained, smoke run clean. - Guard. Allocation tests and Performance Testing sample groups per commit, lint on changed scripts. GATE: tests pass.
Numbers
| Value | Relative to | Source |
| ------------------------------------------------------------------------------ | -------------------------------------------------------------------------------- | ---------------------------- |
| 16.67 / 33.33 ms; x 0.65 mobile | frame budget at 60 / 30 fps; thermal headroom | profiling e-book p. 9, 36 |
| 0 B | managed allocation per gameplay frame | 6.3 Manual; e-book p. 66 |
| up to about 1 ms | per-frame cost of incremental GC write barriers | e-book p. 69 |
| 4.4x / 2.07x / 1.45x | GRD gain: 2M-instance stress / game in Editor / same game standalone | Oc6T4hh5gaI [frame 00:12:41] |
| 217 / 199 / 176 / 161 fps | DX12 Split / Legacy / plain DX12 / Native graphics jobs | Oc6T4hh5gaI [frame 00:03:52] |
| 256 vertices | below it GPU instancing is inefficient: combine instead | 6.3 Manual |
| about 250 ms | one PSO creation stall | Oc6T4hh5gaI [frame 00:04:48] |
| 4 pixel invocations | per one-pixel triangle (2x2 quads); gate 1 triangle per rendered pixel [added] | CmD8MVGkDxQ [00:27:26] |
| 48.55 of 80 ms | per-frame Debug.Log in a development frame | xjsqv8nj0cw [00:10:23] |
| < 200 / > 400 KB | audio: Decompress On Load / Streaming | console e-book p. 104-105 |
| up to 1 ms | CPU per extra active camera on mobile | console e-book p. 89 |
| up to 10 s | startup added by Autoconnect Profiler | e-book p. 47 |
| 50% / 70% / 80% of RAM | memory budget: 2 GB phones / general / dedicated devices | Hall; Unity tutorial; e-book |
| 5,946 to 33 SetPass; 58-60 to 5.2-6.2 ms | 3,000 spheres, MPB tint to 8 Material Variants, dev player | observed |
| 18 to 0 | first-use Shader.CreateGPUProgram after warming 10 PSOs (3.6 ms at load) | observed |
| 177.9 / 110.5 / 116.3 MB | macOS app: IL2CPP Minimal + speed / IL2CPP High + size / Mono | observed |
| 14.75 M to 0.26 M triangles (7.1 to 0.12 per pixel) | 400 dense meshes after Mesh LOD, draw calls unchanged | observed |
| 57.1 ms frame = Spawn.Burst 26.9 ms + 4 compiles; next frame 3 physics steps | burst of 3,000 Instantiate read through its own marker | observed |
| 48-80 ms vs 0 ms | MeshCollider cooking at spawn vs Physics.BakeMesh in a job at load (40 meshes) | observed |
| 33 us vs 2.6-3.9 us | per Debug.Log, stack traces ScriptOnly vs None (dev player) | observed |
| 2.5 vs 5.8 ms; 1.2x at 4x pixels | GPU bus
Truncated for display — read the full file on GitHub.
Related Skills
algorithmic-art
177.9kCreating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems.
pptx
177.9kUse this skill any time a .pptx or .potx file is involved in any way — as input, output, or both. This includes: creating slide decks, pitch decks, or presentations; reading, parsing, or extracting text from any .pptx or .potx file (even if the extracted content will be used elsewhere, like in an em…
prospecting
60.1kWhen the user wants to find and qualify prospects for outbound, or asks who to target first, which signal to prioritize, or where to spot buyers with the problem: buying signals, enrichment, verification, account research.
ad-creative
60.1kWhen the user wants to write or judge ad creative, or asks which ad, hook, or angle to run or kill: headlines, primary text, and variations for Google, Meta, LinkedIn, and TikTok, fresh angles when creative fatigues. Test hypotheses name the metric, comparison, and expected direction.
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.
