Skip to content
Back to search

blender-game-skills

Claude Code agent skills for game dev in Blender. Turn concept art into rigged, game-ready 3D assets, measured against your references.

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked today
Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/majidmanzarpour--blender-game-skills/badge.svg)](/listings/majidmanzarpour--blender-game-skills)

HTML

<a href="/listings/majidmanzarpour--blender-game-skills"><img src="/api/listings/majidmanzarpour--blender-game-skills/badge.svg" alt="findsafeskills safety rating" /></a>

Install

i

Install instructions from the README

As written by the repo's author. findsafeskills has not verified these steps.

With `npx skills` (recommended)

The [`skills` CLI](https://github.com/vercel-labs/skills) from Vercel Labs installs skills from a GitHub repository into the skill folders of Claude Code and other agents. `npx` runs it without a global install; it needs Node.js 22.20 or newer.

# One skill, for all your projects (~/.claude/skills/blender-image-to-3d):
npx skills add majidmanzarpour/blender-game-skills --skill blender-image-to-3d -g -a claude-code

# One skill, for the current project only (./.claude/skills/blender-image-to-3d):
npx skills add majidmanzarpour/blender-game-skills --skill blender-image-to-3d -a claude-code

# Every skill in this repository:
npx skills add majidmanzarpour/blender-game-skills --skill '*' -g -a claude-code

# See what the repository contains without installing anything:
npx skills add majidmanzarpour/blender-game-skills --list

Without `--skill` and `-a`, the CLI asks which skills and agents you want. It copies only each skill's folder (`skills/<name>/`) into the agent's skills directory; the rest of the repository stays out. The full URL, `https://github.com/majidmanzarpour/blender-game-skills`, works in place of `majidmanzarpour/blender-game-skills`, and `-y` skips confirmation prompts.

Update or uninstall (add `-g` for a global install):

npx skills update blender-image-to-3d
npx skills remove blender-image-to-3d

The CLI sends anonymous usage telemetry. Set `DISABLE_TELEMETRY=1` to turn it off.

Manual install

Copy a skill's folder into a Claude Code skills directory and keep its folder name.

git clone https://github.com/majidmanzarpour/blender-game-skills.git
cd blender-game-skills

# For all your projects:
mkdir -p ~/.claude/skills
cp -R skills/blender-image-to-3d ~/.claude/skills/

# Or for one project:
mkdir -p /path/to/project/.claude/skills
cp -R skills/blender-image-to-3d /path/to/project/.claude/skills/

Claude Code picks up a new skill in an existing skills directory during the session. If `~/.claude/skills` or the project's `.claude/skills` did not exist when the session started, restart Claude Code.

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

README.md · README · 323 lines

View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)

  1. # Blender Game Skills
  2. [Agent Skills](https://agentskills.io) for [Claude Code](https://code.claude.com/docs/en/skills) that
  3. build game assets in Blender. Each skill is a self-contained folder of instructions, reference
  4. notes and scripts that the agent follows and runs for you.
  5. By [Majid Manzarpour](https://x.com/majidmanzarpour).
  6. ## Skills
  7. | Skill | What it does |
  8. | --- | --- |
  9. | [`blender-image-to-3d`](skills/blender-image-to-3d/SKILL.md) | Turns reference images (concept art, model sheets, photos, turnarounds, sketches) into game-ready 3D assets: characters, creatures, architecture, vehicles, props, weapons and environment pieces. Gated phases from brief to rigged, exported GLB or FBX, each passed on rendered and measured evidence. |
  10. The repository is set up to hold several skills. Each one lives in its own folder under
  11. [`skills/`](skills/) and installs on its own, so more Blender skills can be added here over time.
  12. ## Installation
  13. ### With `npx skills` (recommended)
  14. The [`skills` CLI](https://github.com/vercel-labs/skills) from Vercel Labs installs skills from a
  15. GitHub repository into the skill folders of Claude Code and other agents. `npx` runs it without a
  16. global install; it needs Node.js 22.20 or newer.
  17. ```bash
  18. # One skill, for all your projects (~/.claude/skills/blender-image-to-3d):
  19. npx skills add majidmanzarpour/blender-game-skills --skill blender-image-to-3d -g -a claude-code
  20. # One skill, for the current project only (./.claude/skills/blender-image-to-3d):
  21. npx skills add majidmanzarpour/blender-game-skills --skill blender-image-to-3d -a claude-code
  22. # Every skill in this repository:
  23. npx skills add majidmanzarpour/blender-game-skills --skill '*' -g -a claude-code
  24. # See what the repository contains without installing anything:
  25. npx skills add majidmanzarpour/blender-game-skills --list
  26. ```
  27. Without `--skill` and `-a`, the CLI asks which skills and agents you want. It copies only each
  28. skill's folder (`skills/<name>/`) into the agent's skills directory; the rest of the repository
  29. stays out. The full URL, `https://github.com/majidmanzarpour/blender-game-skills`, works in place
  30. of `majidmanzarpour/blender-game-skills`, and `-y` skips confirmation prompts.
  31. Update or uninstall (add `-g` for a global install):
  32. ```bash
  33. npx skills update blender-image-to-3d
  34. npx skills remove blender-image-to-3d
  35. ```
  36. The CLI sends anonymous usage telemetry. Set `DISABLE_TELEMETRY=1` to turn it off.
  37. ### Manual install
  38. Copy a skill's folder into a Claude Code skills directory and keep its folder name.
  39. ```bash
  40. git clone https://github.com/majidmanzarpour/blender-game-skills.git
  41. cd blender-game-skills
  42. # For all your projects:
  43. mkdir -p ~/.claude/skills
  44. cp -R skills/blender-image-to-3d ~/.claude/skills/
  45. # Or for one project:
  46. mkdir -p /path/to/project/.claude/skills
  47. cp -R skills/blender-image-to-3d /path/to/project/.claude/skills/
  48. ```
  49. Claude Code picks up a new skill in an existing skills directory during the session. If
  50. `~/.claude/skills` or the project's `.claude/skills` did not exist when the session started,
  51. restart Claude Code.
  52. ## blender-image-to-3d
  53. The agent works through gated phases: brief, calibration, blockout, forms, topology, UVs and
  54. baking, rig, secondary motion, animation, export, and acceptance. Each gate is passed on evidence:
  55. renders compared against the reference from the same camera, and measured numbers. Looking at the
  56. viewport and deciding it seems fine is not accepted.
  57. ### Example prompts
  58. Attach the images to the message (drag them into the terminal, or paste with Ctrl+V, Alt+V on
  59. Windows) or give their paths. Any number of images works in one prompt: separate views, a single
  60. model sheet that holds several views, extra concepts and detail callouts.
  61. ```text
  62. Here are front and side views of a knight (ref/knight_front.png, ref/knight_side.png). Build him
  63. in Blender as a game-ready character for a third-person action game in Unity, about 1.85 m tall,
  64. rigged, with LOD0 to LOD2.
  65. ```
  66. ```text
  67. This model sheet has front, side and back views plus face and belt callouts in one image, and the
  68. second image is a painted three-quarter concept of the same character. Build her in Blender for
  69. Unreal: about 1.70 m, rigged, hair as strands in the master and cards for the game mesh, GLB with
  70. LOD0 and LOD1. Measure proportions from the sheet only.
  71. ```
  72. ```text
  73. Recreate this dune buggy from the concept art as a drivable vehicle asset for Godot: separate
  74. wheels with pivots at the axles, doors that open, a collision hull, GLB export.
  75. ```
  76. ```text
  77. Here's a photo of a stone chapel. Make a modular kit that snaps together on a 2 m grid in
  78. three.js: wall, window wall, doorway, corner, pillar, arch, roof segment, and the door as a
  79. separate hinged object. Tileable materials with a trim sheet.
  80. ```
  81. ```text
  82. Turn these three sketches of a sword (side, edge-on, pommel detail) into a game-ready prop:
  83. about 1.1 m long, a socket at the grip, under 3k triangles, textured, FBX for Unity.
  84. ```
  85. ```text
  86. Use these front, side and back renders of a stylised fox creature and build it as a quadruped
  87. for a mobile game: rigged for walk, run and idle, one 1024 texture set, glTF. Don't ask me
  88. questions unless you really have to.
  89. ```
  90. Claude picks the skill up on its own when you supply a reference image and ask for a 3D model or
  91. game asset, even without mentioning Blender. To make sure it is used, type
  92. `/blender-image-to-3d` followed by your request.
  93. ### Why gates and measurements
  94. Most wasted work in reference-driven modelling is detail added on top of wrong proportions, and
  95. the eye forgives drift that numbers catch. The skill makes the agent measure instead of judging
  96. by eye:
  97. - Every constant in the build scripts is a measured value with a comment naming the reference
  98. view it came from, or it is marked `# inferred`.
  99. - Each phase ends with renders from a camera matched to the reference and at gameplay pixel size,
  100. and a compare sheet with numbers: silhouette IoU and a ten-band width profile. For orthographic
  101. sheets, a world-registered gate also catches a model that is the wrong height or off its axis,
  102. which bounding-box alignment would hide.
  103. - Mismatches are written as measurements ("head 12 percent too tall", "wheelbase 0.3 m short"),
  104. fixed in the build script, and re-rendered until they are inside the phase tolerance. Nothing
  105. gets detail until its silhouette passes.
  106. - Exports are re-imported into an empty Blender scene and checked against the manifest, because
  107. the modelling viewport is not what the engine receives.
  108. - Anything the references do not show is listed as inferred in the brief, the final report and
  109. the export manifest.
  110. ### Phases
  111. | Phase | What happens | Evidence at the gate |
  112. | --- | --- | --- |
  113. | 0. Brief | Reads every image and writes `asset-brief.md`: views and camera estimates, real scale and its evidence, 8 to 15 proportions to check, parts, materials, what must be inferred, target engine and budget | The brief; questions only for what the images cannot tell |
  114. | 1. Calibration | Master `.blend` with reference images as planes at real scale, a ruler, grid cell, door clearance, collision capsule and the game camera | Everything after this is measured in the same file and scale |
  115. | 2. Blockout | Primary masses, separate appendages, joint centres and pivots | Clay and silhouette compare sheets: IoU 0.85 or more, band widths within 0.05, proportions within 5 percent |
  116. | 3. Forms | Secondary and tertiary forms, layered parts in their real overlap order | IoU 0.90 or more, band widths within 0.03, proportions within 2 percent, clay turntable |
  117. | 4. Topology | LOW delivery meshes over the approved forms, LOD1 and LOD2 | `validate.py` within the triangle budget, wire render, no silhouette loss |
  118. | 5. UVs, baking, materials | UVs, original materials, baked portable maps | Material turntable under a moving light, greyscale at gameplay size, clean checker render |
  119. | 6. Rig | Deformation skeleton, controls, pivots, sockets and weights (skipped for static props) | Extreme-pose sheet; no unweighted or over-influenced vertices |
  120. | 7. Secondary motion | Cloth, chains, tails, wings or cables, only where the brief asks for them | Posed renders without penetration |
  121. | 8. Animation | Named clips with loop flags and event markers, only when requested | Clips rendered at the game camera, loop seams and event timings checked |
  122. | 9. Export and round trip | GLB or FBX with `asset-manifest.json` and `animation-contract.json`, then a reimport into an empty scene | Triangle counts, bones, clips and images match the manifest; height within 1 percent |
  123. | 10. Acceptance | Acceptance checklist and a `review/final/` handover folder | Report of what matches, the deviations that remain, what was inferred and the budgets used |
  124. ### What to expect
  125. - The agent saves the references into `<asset>/ref/`, studies every image and writes
  126. `<asset>/asset-brief.md` first. It asks only for what the images cannot tell: target engine and
  127. format, real size when nothing in the image gives scale, budget tier, whether to rig and
  128. animate, and the game camera. It offers defaults (1 unit = 1 m, Z up, GLB, the standard budget
  129. tier, a three-quarter camera at 50 mm, 128 px subject height) and uses them if you tell it to
  130. just go.
  131. - At the end of each phase it shows a compare sheet (reference, render, overlay, gameplay-size
  132. strip), the measured deviations and what was inferred, then waits for your approval. If you
  133. tell it not to ask, it continues whenever the tolerance is met and keeps the sheets in
  134. `<asset>/review/`.
  135. - Claude Code asks for permission before it runs Blender or Python commands, unless you have
  136. allowed them.
  137. - A Blender session connected through an MCP server is optional. The agent can use it to inspect
  138. the scene and reload the master file in your open Blender after each rebuild; the build itself
  139. still runs through the scripts.
  140. A typical asset folder:
  141. ```text
  142. CH_Knight/
  143. |-- asset-brief.md
  144. |-- ref/ # the references, including crops of multi-view sheets
  145. |-- CH_Knight_master.blend # source of truth: REF, HIGH, LOW, RIG_DEF, COLLISION, SOCKETS ...
  146. |-- CH_Knight_baked.blend # after Phase 5: delivery materials wired to the baked maps
  147. |-- build/ # 02_blockout.py, 03_forms.py, ...: re-runnable phase scripts
  148. |-- review/ # compare sheets, gate JSON, turntables, final/
  149. |-- textures/ # baked maps
  150. `-- exports/ # GLB or FBX, asset-manifest.json, animation-contract.json
  151. ```
  152. ### Requirements
  153. - **Blender 4.2 or newer.** Tested on Blender 5.2. Blender 5.x changed several APIs;
  154. [`references/blender-5-notes.md`](skills/blender-image-to-3d/references/blender-5-notes.md)
  155. lists the ones these scripts deal with. The skill looks for Blender in `$BLENDER_BIN`, then
  156. `blender` on `PATH`, then `/Applications/Blender.app/Contents/MacOS/Blender`; set
  157. `BLENDER_BIN` if yours is somewhere else.
  158. - **Python 3 with Pillow** for `compose_review.py`, the one script that runs outside Blender:
  159. `python3 -m pip install pillow`. The other scripts run in Blender's bundled Python and need
  160. nothing else.
  161. - **Claude Code.** The skill uses the open Agent Skills format, so other agents that support
  162. skills and can run shell commands may work, but only Claude Code has been tested.
  163. GPU notes:
  164. - No GPU is required. Clay, silhouette and wire review renders, `world_gate.py` and
  165. `roundtrip.py` use the Workbench engine, which needs no GPU on macOS or Windows.
  166. - On a headless Linux machine without a GPU, pass `--engine cycles` to `review_render.py` (it
  167. also falls back to Cycles by itself when Workbench fails).
  168. - Checker and material review renders use Cycles on the CPU. Baking uses Cycles on the CPU by
  169. default; `bake_maps.py --device GPU` uses the device enabled in Blender's Preferences > System >
  170. Cycles Render Devices. On Apple Silicon, enable only the Metal device there.
  171. ### Scripts
  172. The scripts live in `skills/blender-image-to-3d/scripts/`. The agent runs them for you; you only
  173. need them to rerun a gate yourself or to work without an agent.
  174. | Script | Runs in | Purpose |
  175. | --- | --- | --- |
  176. | `init_master.py` | Blender | Creates the master `.blend`: units, collections, reference planes at real scale (one per view plus any number of extra images), calibration objects and the game camera. |
  177. | `review_render.py` | Blender | Clay, silhouette, wire, checker or material renders from fixed views and a reference-matched camera, at gameplay size, as turntables or in posed frames. |
  178. | `compose_review.py` | Python 3 + Pillow | Compare sheet (reference, render, overlay, gameplay strip) with silhouette IoU and a ten-band width profile. |
  179. | `world_gate.py` | Blender | World-registered silhouette IoU against a cleaned orthographic reference matte, so scale and placement errors count. |
  180. | `validate.py` | Blender | Checks topology, transforms, UVs, weights, armature, sockets, colliders, naming and the triangle budget; exits 1 on any FAIL. |
  181. | `bake_maps.py` | Blender (Cycles) | Bakes normal and AO from HIGH to LOW, plus base colour, roughness and metallic; can rebuild export-ready materials. |
  182. | `export_delivery.py` | Blender | Exports GLB, glTF or FBX with `asset-manifest.json` and `animation-contract.json`. |
  183. | `roundtrip.py` | Blender | Imports the export into an empty scene, reports what arrived and renders a check frame. |
  184. `assets/build_template.py` is the template for the per-phase build scripts. Each copy opens the
  185. master file, deletes the objects it owns, rebuilds them and saves, so any phase can be rerun.
  186. Every script prints its options with `--help`. For the Blender scripts, put it after the `--`
  187. separator: `blender --background --python scripts/validate.py -- --help`.
  188. Example: the review and gate loop. The values come from the skill's example, a 1.85 m knight; in
  189. a real build they come from the brief.
  190. ```bash
  191. SKILL=~/.claude/skills/blender-image-to-3d # where the skill is installed
  192. BLENDER=${BLENDER_BIN:-blender}
  193. # 1. Clay renders of the LOW collection from the fixed views and the reference-matched camera
  194. "$BLENDER" --background --python "$SKILL/scripts/review_render.py" -- \
  195. --blend CH_Knight/CH_Knight_master.blend --out CH_Knight/review/02_blockout \
  196. --collections LOW --views front,side,threequarter --ref-cam 35 12 50 --mode clay --gameplay-px 128
  197. # 2. Compare sheet and numbers against the front reference (--measure also writes compare_front.json)
  198. python3 "$SKILL/scripts/compose_review.py" --ref ref/front.png \
  199. --render CH_Knight/review/02_blockout/clay_front.png \
  200. --out CH_Knight/review/02_blockout/compare_front.png --measure --gameplay-px 128
  201. # 3. Orthographic sheets only: world-registered IoU against a cleaned matte of the front view
  202. "$BLENDER" --background --python "$SKILL/scripts/world_gate.py" -- \
  203. --blend CH_Knight/CH_Knight_master.blend --out CH_Knight/review/02_blockout \
  204. --matte ref/front_clean.png --az 0 --m-per-px 0.0029167 --axis-col 109 --ground-row 610 \
  205. --collections LOW --name front
  206. ```
  207. Read the sheet and the numbers, fix the constants in the phase script, rebuild, and repeat until
  208. every mismatch is inside the phase tolerance.
  209. ### Limits
  210. - The skill is instructions plus scripts. The agent still does the modelling, as bpy code, so
  211. results depend on the model running the skill, the quality of the references and your review
  212. at each gate.
  213. - Dimensions are measured from orthographic views. Perspective concept art and photos are used
  214. for silhouette and surface detail, not proportions.
  215. - A single image cannot show the back or the sides. Those parts are inferred and labelled as such.
  216. ## Repository layout
  217. ```text
  218. .
  219. |-- README.md
  220. |-- LICENSE
  221. |-- .gitignore
  222. `-- skills/
  223. `-- blender-image-to-3d/ # one folder per skill; this folder is what gets installed
  224. |-- SKILL.md # instructions, phases and gates
  225. |-- scripts/ # the scripts above
  226. |-- references/ # categories, delivery and acceptance, rigging and
  227. | # animation, Blender 5 notes
  228. |-- assets/build_template.py # template for the per-phase build scripts
  229. `-- evals/evals.json # test prompts for evaluating the skill
  230. ```
  231. ### Adding a skill
  232. - Create `skills/<skill-name>/SKILL.md` with `name` and `description` frontmatter. The folder name
  233. must match `name`: lowercase letters, digits and hyphens, at most 64 characters. Keep
  234. `description` within 1024 characters.
  235. - Keep the skill self-contained: paths in `SKILL.md` are relative to its folder, and everything it
  236. needs (scripts, references, assets) lives inside it.
  237. - Add a row to the Skills table above, and check that `npx skills add . --list` finds every skill.
  238. ## Contributing
  239. Issues and pull requests are welcome. For larger changes, open an issue first.
  240. - Scripts run headless (`blender --background --python <script> -- <args>`), accept `--help`, and
  241. look up nodes by type, not by display name, because display names are translated in
  242. non-English Blender UIs.
  243. - Test on Blender 4.2 and a current 5.x release where you can, and record API differences in the
  244. skill's `references/blender-5-notes.md`.
  245. - Run `python3 -m py_compile` on every script. `compose_review.py` must keep working with only
  246. Pillow installed.
  247. - Keep each `SKILL.md` short (the Agent Skills specification recommends under 500 lines) and move
  248. detail into `references/`.
  249. - For changes to a skill's behaviour, run the prompts in its `evals/evals.json` before and after,
  250. for example with Anthropic's skill-creator skill.
  251. To try a working copy in Claude Code, link it into your skills folder after removing any installed
  252. copy: `ln -s "$PWD/skills/blender-image-to-3d" ~/.claude/skills/blender-image-to-3d`.
  253. ## License
  254. [MIT](LICENSE) © 2026 Majid Manzarpour.

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.