Next AI Draw.io
draw.io diagrams your AI agent draws on a live browser canvas that you can also edit by hand
Claude Code plugin: describe an object or show a photo, and Claude builds a clean 3D model in Blender, for games, the web, AR or 3D printing. It animates characters too. New in 3.0: Kiln Studio, a local page to view, check and fix your models with Claude.
If you made this, paste this code into your README. The badge links back to this page.
[](https://mcp.popnx.com/en/skills/elithril-blender-kiln)MCP servers that connect the AI to services for the same work
draw.io diagrams your AI agent draws on a live browser canvas that you can also edit by hand
Create, inspect, validate, and save editable 3D building scenes with Pascal's MCP server.
Verified React chart generation: select, validate, repair, render, and inspect charts through MCP.
Same kind of work, ordered like the Skills list
| This one blender-kiln | impeccable | diagram-design | frontend-slides | guizang-ppt-skill | |
|---|---|---|---|---|---|
| Maker | elithril | pbakaus | cathrynlavery | zarazhangrui | op7418 |
| Skills | 1 | 1 | 1 | 1 | 1 |
| GitHub stars | 226 | 113,042 | 68,296 | 32,579 | 30,091 |
| Last code change | Nov 16, 2026 | Nov 19, 2026 | Nov 19, 2026 | Jun 24, 2026 | Oct 30, 2026 |
| License | MIT | Apache-2.0 | MIT | MIT | AGPL-3.0 |
1 skills (instruction sets) by elithril that an AI reads and follows · not an MCP server
MCP = the hands
Connects the AI to an outside service or data, such as reading Notion or creating an invoice. A program or server has to be running.
Skill = the manual
A text file that teaches the AI how to do a task. It connects to nothing.
Some overlap: a few Skills run scripts that call tools, and a few MCP servers only send knowledge. Start from the task you want done.
Claude Code
From the maker’s README and the folders in the repo
GitHub account elithril (person), 10 years old
★ 226 stars, few users so far · code last changed Nov 16, 2026
58 scripts that can run on a computer: tools/test_verify_docs.py, tools/verify_blender.py, tools/verify_docs.py, studio/approval_hook.py and 54 more
Scripts that go online: studio/estimate.py
No hooks or writes to machine settings found
Checked automatically from the repo files at commit 2aec3ec (read only, nothing was run). Not a safety guarantee: read it and decide for yourself
First: which AI do you use?
Pick your app and this page shows only how to install it there
Uploading to claude.ai would fail: the description is over 200 characters (875). Use "Let the AI install it" instead
Copy this sentence and paste it into a Claude Code chat
For one project, paste it into a chat that is open in that project’s folder · The AI always shows you the path before installing
The AI tells you what it will do first and asks your permission at every step
Restart Claude Code, then type /plugin or ask for a matching task and Claude picks it up
Checked against official docs Nov 12, 2026 · Source: code.claude.com
A Skill is instructions the AI will follow. Read the files before installing, and install only from makers you trust.
Checking the commands · copy buttons appear once they pass
Copied from the maker’s README; it downloads and runs the maker’s code
Mac: press Command+Space and type Terminal · Windows: the command below does not work in PowerShell; use “Let AI install it” above instead
This downloads the repo to a temporary folder and copies only the folders that contain a SKILL.md
Checking the commands · copy buttons appear once they pass
The ChatGPT desktop app has Codex built in, and Codex reads skills from ~/.agents/skills
Open Codex in the ChatGPT desktop app and paste this sentence into the chat
The AI always shows you the path before installing
The AI tells you what it will do first and asks your permission at every step
Put the kiln folder at ~/.agents/skills/kiln
~ is your home folder ($HOME)
A Skill is instructions the AI will follow. Read the files before installing, and install only from makers you trust.
Mac: press Command+Space and type Terminal · Windows: the command below does not work in PowerShell; use “Let AI install it” above instead
This downloads the repo to a temporary folder and copies only the folders that contain a SKILL.md
Checking the commands · copy buttons appear once they pass
Checked against official docs Nov 15, 2026 · Source: learn.chatgpt.com
Skills you install yourself do not work here; only skills that come with a plugin from the directory
To use this skill with ChatGPT, use the ChatGPT desktop app as above
Checked against official docs Nov 15, 2026 · Source: learn.chatgpt.com
Copy this sentence and paste it into a Codex chat · Works in Codex inside the ChatGPT desktop app, Codex CLI and the IDE extension
For one project, paste it into a chat that is open in that project’s folder · The AI always shows you the path before installing
The AI tells you what it will do first and asks your permission at every step
Codex picks up newly installed skills by itself; if one does not show up, restart Codex · To use it: in ChatGPT type @ and pick the skill · in Codex CLI or the IDE extension run /skills or type $ and the skill name
Checked against official docs Nov 15, 2026 · Source: learn.chatgpt.com
A Skill is instructions the AI will follow. Read the files before installing, and install only from makers you trust.
Mac: press Command+Space and type Terminal · Windows: the command below does not work in PowerShell; use “Let AI install it” above instead
This downloads the repo to a temporary folder and copies only the folders that contain a SKILL.md
Checking the commands · copy buttons appear once they pass
Copy this sentence and paste it into a Cursor chat
For one project, paste it into a chat that is open in that project’s folder · The AI always shows you the path before installing
The AI tells you what it will do first and asks your permission at every step
In Cursor’s Agent chat, type / and pick plugin
Checked against official docs Nov 12, 2026 · Source: cursor.com
A Skill is instructions the AI will follow. Read the files before installing, and install only from makers you trust.
Mac: press Command+Space and type Terminal · Windows: the command below does not work in PowerShell; use “Let AI install it” above instead
This downloads the repo to a temporary folder and copies only the folders that contain a SKILL.md
Checking the commands · copy buttons appear once they pass
For other apps that read skills. The sentence gives the paths for Claude Code, Codex and Cursor so the AI picks the one for your app · Copy this sentence into the app’s chat
For one project, paste it into a chat that is open in that project’s folder · The AI always shows you the path before installing
The AI tells you what it will do first and asks your permission at every step
Checked against official docs Nov 12, 2026 · Source: code.claude.com, learn.chatgpt.com, cursor.com
Other apps that support Agent Skills (such as Gemini CLI or GitHub Copilot) use different folders. Check that app’s guide, then copy the folder with the SKILL.md there.
Skill folders checked against the official Claude Code, Codex and Cursor guides on Nov 11, 2026
The text below comes from the maker’s repo, not from PopNx MCP
Showing the first 8,000 characters · Open the full file on GitHub
---
name: kiln
description: "Makes and fixes 3D assets in Blender, for games, the web and AR. Use when the user wants a 3D model, prop, character or GLB/glTF/FBX/USDZ file made — from a text brief, a reference image, a free marketplace (PolyHaven, Sketchfab) or AI generation — AND when they bring an existing 3D file to fix: too heavy or too many polygons (optimize, compress, LODs), broken normals, scale or origin, materials lost on glTF export, conversion between GLB, FBX and USDZ, texturing, rigging for animation, animating it (walk and idle cycles, text-to-motion, looping clips, articulated props), or inspection. Drives Blender through a Blender MCP server (ahujasid's or the official Blender Lab one). Batch mode produces many consistent assets unattended. Kiln Studio (`/kiln studio`) opens the project's models in the browser, where the user reviews them and pins notes for Claude to act on."
allowed-tools: Bash, Read, Edit, Write, Grep, Glob, WebFetch, WebSearch, mcp__blender__*, mcp__nano-banana__*, mcp__plugin_blender-kiln_kiln-studio__get_selection, mcp__plugin_blender-kiln_kiln-studio__get_notes, mcp__plugin_blender-kiln_kiln-studio__reply_to_note, mcp__plugin_blender-kiln_kiln-studio__set_camera, mcp__plugin_blender-kiln_kiln-studio__get_view_image, mcp__plugin_blender-kiln_kiln-studio__list_models, mcp__plugin_blender-kiln_kiln-studio__add_note, mcp__plugin_blender-kiln_kiln-studio__make_variations, mcp__plugin_blender-kiln_kiln-studio__add_finishes, mcp__plugin_blender-kiln_kiln-studio__open_model, mcp__plugin_blender-kiln_kiln-studio__set_view, mcp__plugin_blender-kiln_kiln-studio__compare, mcp__plugin_blender-kiln_kiln-studio__play_clip, mcp__plugin_blender-kiln_kiln-studio__present
---
# blender-kiln — The 3D Asset Forge
You are a 3D asset production expert. You pilot Blender via MCP to produce clean, optimized assets from brief to export.
Keep every working file — scripts, crops, renders, bakes — inside the asset's output
folder. Never write to `/tmp` or any shared path under a generic name: a bench session
wrote `/tmp/top.png` and could not tell whether it had overwritten someone's file.
Reply in the language the user wrote the request in — not the language of the machine, its paths or its locale. Measured: two bench sessions answered in French to an English brief.
---
## Commands
| Command | Action |
|---|---|
| `/kiln` | Full pipeline (CONFIG → EXPORT) |
| `/kiln batch` | Batch wizard → manifest → autonomous multi-asset production |
| `/kiln batch run` | Execute/resume a batch manifest (options: `--all`, `--asset <name>`) |
| `/kiln setup` | Environment detection + guided setup (models, dependencies, GPU) |
| `/kiln models` | List the optional AI backends (TRELLIS.2 first, Hunyuan3D with its licence limit), switch the active one |
| `/kiln status` | Show current pipeline state, next steps, prompts |
| `/kiln search` | Search PolyHaven/Sketchfab marketplaces |
| `/kiln inspect` | Inspect a 3D file (stats, poly count, materials, bbox) |
| `/kiln cleanup` | Cleanup a mesh in Blender (standalone) |
| `/kiln texture` | Texture an untextured mesh (standalone) |
| `/kiln animate` | Animate a rigged asset, routed by subject: idle/walk cycles, text-to-motion, keyed props (standalone) |
| `/kiln optimize` | Optimize a GLB with gltf-transform/gltfpack (standalone) |
| `/kiln convert` | Convert between formats (GLB→USDZ, GLB→FBX, etc.) |
| `/kiln studio` | Open Kiln Studio, the browser viewer where the user pins notes on models; with notes waiting, act on them (`/kiln studio <asset>`) |
| `/kiln help` | List all commands and usage |
### Argument routing
There is no `commands/` directory: `kiln` is a single skill, so every entry point
above arrives as the skill's arguments. Route on the FIRST word:
| First argument | Entry point |
|---|---|
| *(none)* | Full pipeline, starting at CONFIG |
| `batch` | Batch wizard (see `references/batch-mode.md`) |
| `batch run` | Batch runner — accepts `--all`, `--asset <name>` |
| `setup` | Environment detection + guided install |
| `models` | Model listing / switching |
| `status` | Pipeline state report |
| `search`, `inspect`, `cleanup`, `texture`, `optimize`, `convert` | Standalone tools |
| `studio` | Kiln Studio — accepts an asset id or name; load `references/studio.md` |
| `help` | Print the command table above and stop |
Anything the first word does not match is treated as an asset brief, so
`/kiln a low-poly wooden chair` starts the full pipeline with that brief already
captured — skip the CONFIG question it answers.
NEVER tell the user to type `/kiln:setup` or any other colon form. A colon
addresses a plugin's skill (`blender-kiln:kiln`), so `/kiln:setup` resolves to
nothing and the user gets no response.
---
## Iron Rules
```
1. ALWAYS get_scene_info() before each PHASE of the pipeline. Headless (no
Blender connected, rule 2): the build script prints the scene's objects
instead, and the log carries that line.
2. ALWAYS look at the model after each significant modification — `look()`
(older servers: get_viewport_screenshot(); `references/blender-mcp.md`) — at
minimum once at the end of every phase that changed geometry or materials
(SOURCE/IMPORT, CLEANUP, TEXTURING, OPTIMIZE if it re-imports), framed per
rule 22, and from TWO opposite angles after TEXTURING. A numeric check does
not replace it: a UV defect on one corner passed every count. When the MCP
does not answer (Blender closed), open it without asking: `python3
<skill>/tools/open_blender.py` — the user's own Blender, behind their windows,
its MCP add-on serving on 9876, exit 0 once it answers — and say so in one line.
(Inside Kiln Studio the worker's Blender is always open: never run it there.)
A Blender open without its server: it opens nothing (exit 1).
When it fails (exit 1), stop and ask: tell the user what it said and offer to
build headless. Headless, or when the open Blender is the user's (rule 16):
say so in the report — never "in your Blender" —, and render the same views
headless — never skip the look:
`tools/review_renders.py MODEL... --out DIR` (Workbench, matcap and colour,
two opposite three-quarters, top and under, framed on the vertices;
`--close-from` the check's thin spots). Every print session of 2026-10-13
wrote its own script; one framed on bound_box and misread a height by 15 mm.
3. ONE asset at a time — never an entire scene at once.
4. NEVER hard-cap poly count — alert if out of range, never block.
5. NEVER spend money — no paid services, no credits consumed. A free service
that answers HTTP 402 has stopped being free: switch source, never pay.
NEVER remove or paint over a watermark or attribution on a generated image.
6. NEVER silently destroy — decimate, simplify, delete = always propose,
show before/after, wait for user choice. Even in auto mode. The one
exception is Blender's untouched factory scene (Cube, Camera, Light, nothing
else, no .blend loaded): remove the Cube before building and log it. Any
other pre-existing object is the user's — hide it, never delete it.
A headless script started with `--factory-startup` gets that Cube too: begin
it with `bpy.ops.wm.read_factory_settings(use_empty=True)` — a 2 m Cube saved
into a print's parts .blend made `--reference` fail by 40 %. Only there: through
the MCP it resets the live Blender and turns its MCP add-on off.
Print's remesh-then-decimate (`references/print.md` rule 3) is the build
method, not a destruction of the user's mesh: logged, not proposed. Same for
a reduction the brief itself asks for, on a mesh the session built.
7. ALWAYS keep the .blend file (contains full history). In compact mode,
only keep original + final + .blend + log. In full mode, keep all
intermediate GLBs. ALWAYS save the .blend — it's the recovery point.
AND A PHASE IS NOT DONE UNTIL `{name}_log.md` SAYS SO: before starting the
Ask, share a tip or report that it does not work. Sorted by what people marked helpful.
No posts yet. Be the first to ask or share.
Posts here are written by users, not the PopNx team.