This skill turns an agent into a build engineer for Unreal Engine 5.8 projects. It sets the launch map and what gets cooked, validates content, runs RunUAT BuildCookRun from the command line so the build is reproducible, and reads the UAT and cook logs when a build fails.
It covers the usual traps: a black screen from an unset default map, assets missing from the build because nothing references them, Shipping builds with no log, and the Zen store holding cooked output by default in 5.8.
What You Get
- A six-step packaging workflow with a ready BuildCookRun command line
- Verification steps: the UAT result, pak files in the archive and a smoke run with a log file
- Guidance on Development, Test and Shipping builds and what each strips
- A gotcha list covering missing maps, uncooked assets, Zen server output, CI process lifetime and SDK minimums
- Version notes on 5.8 platform SDK requirements, Windows on Arm builds and the Zen default
Common Use Cases
- Producing a test or release build from a terminal or CI
- Finding why a packaged game shows a black screen or an empty level
- Reading a BUILD FAILED result or an AutomationTool exit code in the UAT and cook logs
- Choosing which maps and asset directories are cooked
What Makes It Unique
The skill uses the UAT command line even when the user packages from the editor, because it is reproducible, and it states that a finished cook proves the content converted but not that the game starts. It explains the 5.8 change that puts cooked output in the Zen store, which surprises people who look for uasset files. Store uploads go to the Steam and itch skills.
Under The Hood
The agent loads the SKILL.md only; it has no reference files. It reads your uproject file and config files, runs the editor command line to validate assets, and runs RunUAT to build, cook, stage and archive into a folder you name. It then launches the packaged game with a log file and reads the log. It does not fetch web pages itself. Builds can take long and write many files, so expect heavy disk use.