unity-performance-audit
/unity-performance-audit
Use when the task is to measure CPU, GPU, memory, batching, and asset-loading costs.
- Author
- voyager67 ↗
- Repository
- Agentic-Skill-Garage ↗
- Licence
- Apache-2.0
- Last repository change
- 07.11.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 07.11.2026, without references to retired models or APIs.
Apache-2.0, otwarta: można używać i zmieniać, z zachowaniem licencji i informacji o zmianach.
What it does and when to use it
Use when the task is to measure CPU, GPU, memory, batching, and asset-loading costs.
Original author description
Use when the task is to measure CPU, GPU, memory, batching, and asset-loading costs.
How it works
- Outcome
- Inputs and prerequisites
- Procedure
- Quality gates
- Deliverable
- Boundaries
SKILL.md preview
--- name: unity-performance-audit description: Use when the task is to measure CPU, GPU, memory, batching, and asset-loading costs. license: Apache-2.0 --- # Unity Performance Audit ## Outcome Measure CPU, GPU, memory, batching, and asset-loading costs. The result must be traceable to supplied inputs and pass the checks below. ## Inputs and prerequisites - Project version, target platform, render pipeline, plugin/package set, asset specifications, and acceptance criteria. - The installed Unreal Editor or Unity Editor, their scripting/command-line interfaces, profilers, and project logs. - Confirm the target application's version and the actual capabilities available in this environment. ## Procedure 1. Inspect project version, target platform, render pipeline, plugins/packages, and existing conventions. 2. Import assets into a dedicated staging location with correct units, pivots, materials, collisions, and LODs. 3. Use engine-native systems and keep generated assets separate from hand-authored source content. 4. Profile the target scene/build; do not optimize from visual guesswork or editor-only timing. 5. Build from a clean state and inspect logs, missing references, shader compilation, and startup behavior. 6. Test on the intended platform or report the exact platform that was not available. ## Quality gates - A successful editor import does not prove a package build works. - Do not change project-wide rendering or package versions without a scoped impact review. - Performance claims require a captured baseline and comparable test conditions. ## Deliverable Engine project changes, imported asset manifest, build/profile evidence, and platform-specific limitations. Include the exact commands or application operations used, the files changed, and the checks that were actually run. ## Boundaries - Keep source files unchanged; write new versions to an explicit output path. - Do not transmit private assets or prompts to an external provider unless the user has explicitly approved that destination. - Do not run paid generation or destructive application operations without clear authorization and a stated budget or scope. - If a required application, plugin, model, or entitlement is absent, report the limitation and stop at the last verified stage. - Separate measured results from visual judgment, assumptions, and recommendations.
Versions
The database has no other skills named unity-performance-audit.
Database snapshot: 13.11.2026 · package version 4125adacac4f (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100unity-optimization
Use when profiling, diagnosing, optimizing, or reviewing Unity performance, including CPU/GPU bottlenecks, GC allocations, Update/Input/UI hot paths, physics cost, rendering, shaders, batching, Addressables/loading, mobile thermal/battery constraints, memory, and before/after performance evidence. - 90unity-project-audit
Use when the task is to inspect Unity project settings, packages, scenes, and build targets. - 100unity-performance
Unity performance — Profiler, Frame Debugger, Memory Profiler, GC allocation hunting, object pooling, IL2CPP build settings, Burst, batching, LOD, GPU Resident Drawer. USE WHEN: frame drops, GC spikes, long load times, memory growth, draw-call storms, mobile thermal/battery… - 100unity-dev
Use when implementing a Unity C# feature or fix, or when the user requests Unity architecture, implementation, review, or tests. - 100scenario-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… - 100unity-asset
アセット管理ワークフロー。依存関係調査、参照整合性チェック、パッケージ管理。 Use for: "アセット依存", "参照切れ", "パッケージ管理", "不要アセット