Who it is forAn indie game artist who needs a props-ready asset for Unreal and does not know the optimization steps by heart.
The problemPreparing a prop for a game engine means reducing geometry, baking detail into textures, setting up LODs and exporting in the right format, which takes many manual steps.
The outcomeA crate asset exported for Unreal with baked normals and LOD levels, produced by agent-run steps from the matching skills.
What you need first
- Blender 5.2 or newer installed
- git to clone the repository
- An AI coding agent such as Claude Code, Codex, Gemini CLI or Cursor
- Optional: a Blender MCP server so agents can work in your open Blender session
Steps
- Clone the repository:
git clone https://github.com/EL4CTEO/blender-skills - Install the skills for your agent:
./blender-skills/install/install.sh(macOS / Linux) or.\blender-skills\install\install.ps1(Windows) - Open your agent in the project folder and describe the crate and the target engine.
- Ask the agent to run the game optimization, texture baking and export skills in that order.
- Import the exported file into Unreal and check the LOD switch distances and normal map appearance.
Prompt for your agent
Using the blender-skills repo, make <target crate model> game-ready for Unreal with baked normal maps and LODs, then export it. Expect the exported file, a list of LOD levels and the baked texture files. Verify that the export contains every LOD and that the normal map maps to the correct UV set.
Caveat. The README lists Unreal among export targets but does not say how the exported crate will look in Unreal, so check the import yourself.
Get 5 new use cases every morning. Free, one short email, unsubscribe anytime.
Get them freeShare: X LinkedIn Hacker News Email Copy link
Disclaimer
Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page