blenderBLOCK
DeepSeek Harness plugin for complete Blender 3D modeling, reconstruction, rendering, validation, and export workflows
Overview
From the repository's own README, as read at the audited commit. Badges and raw HTML are left out.
简体中文
[](https://github.com/awesome-dsh-plugin/awesome-dsh-plugin)
An installable DeepSeek Harness plugin that gives dsh a complete Blender-backed 3D production workflow. It registers one orchestrator plus 29 directly loadable domain skills, all 26 upstream analysis/validation helpers, and 13 workspace-scoped Blender tools.
Example output
Camera-free preview generated during a real dsh-blender installation smoke test.
Tools
blender_statuschecks Blender, analysis Python, skills, helpers, and the active workspace.blender_scene_infoandblender_object_infoinspect scenes and object-level geometry, materials, UVs, constraints, shape keys, and animation.blender_importconverts supported portable assets into versioned.blendsources.blender_pythonruns a small reviewedbpy/bmeshchunk and saves a versioned.blend.blender_preview,blender_render, andblender_render_framescreate blockout, look-dev, and animation evidence forread_imageQA.blender_exportexports GLB/glTF, FBX, OBJ, STL, USD, or PLY.blender_validate_sceneandblender_validate_exportperform target-aware audits and clean-process re-import checks.blender_helper_catalogandblender_helper_runexpose all 26 deterministic reference, wireframe, contour, multiview, UV, texture, look, repair, and animation-QA helpers.- The bundled 30-skill stack coordinates blockout, refinement, materials, lighting, cameras, animation, reconstruction, validation, and artifact handoff.
No Blender add-on or control port is required: each operation launches a local Blender background process.
Requirements
- DeepSeek Harness
0.2.0-rc.2,0.2.1-alpha.1, or0.2.1-alpha.2 - Node.js 22.12+
- Blender 4.3+ available as `bl
bb31944adda5OBSERVED · 2026-10-12Install
Commands as the repository documents them. They are shown, not run.
npm install --prefix "$host_dir" --registry=https://registry.npmjs.org \
UV unwrap + checker test for texel density → bake (normal, AO, ORM) →
UV fitting may analyze atlas regions before geometry locks, but final UV writes wait for stable mesh topology or stable pro
uv = mesh.uv_layers.get(uv_name) or mesh.uv_layers.new(name=uv_name)
uv = mesh.uv_layers.new(name='UV')
Host compatibility
What the documentation claims. We have not run a compatibility test.
| Host | Status | Notes |
|---|---|---|
| claude-code | mentioned | |
| codex | mentioned |
What it tells the agent
The instruction file, verbatim from the audited commit — this is the text the model reads, and the surface the audit's instruction layer examines. Quoted here so you can judge it without cloning anything.
--- name: create-3d-model description: Create and refine portable 3D models from text prompts, one or more reference images, wireframes, orthographic views, templates, texture atlases, or existing 3D assets. Use whenever the dsh agent must model or reconstruct geometry, match visual references, create materials and UVs, rig or animate a model, validate shape or multiview fidelity, repair a subpar asset, edit an existing Blender scene, or export GLB, glTF, FBX, OBJ, USD, STL, or another requested 3D format. Uses the dsh-blender tools and Blender as the production backend while treating the transferable 3D model as the normal deliverable. --- # Create 3D Model Turn text, images, wireframes, multiview references, or existing assets into validated 3D models. Use Blender as the production backend and editable source environment, not as the definition of the product. Inspect the inputs and open scene, route the request to the smallest relevant module set, execute controlled `bpy` changes, inspect visual evidence, iterate, export the model, and preserve the engineering source. This DeepSeek Harness plugin registers the complete 30-part capability stack: this top-level orchestrator plus 29 independently loadable domain skills. Load only the domain skills required by the request. ## Start here 1. Read [references/dsh-integration.md](references/dsh-integration.md) before the first Blender tool call in a task. 2. Read [references/capability-map.md](references/capability-map.md) and select only the skills needed for the request. 3. Load a selected module with the DSH `skill` tool using its kebab-case name, such as `blender-modeling`, `reference-to-3d`, or `wireframe-to-3d`. Resolve its resources from the directory reported by the skill loader. 4. Treat this file and `dsh-integration.md` as higher priority than a vendored module when tool naming, scene safety, output paths, or runtime guidance differs. Do not read every module preemptively. Load the orchestrator or domain module first, then follow a dependency only when its gate is reached. ## Discover Blender capabilities - Call `blender_status` before the first modeling operation. It reports Blender, the analysis runtime, registered skills, helpers, and workspace. - Use `blender_scene_info` and `blender_object_info` for structural inspection. Use `blender_import` before editing a non-Blend asset. - Use `blender_python` for controlled `bpy` changes, `blender_preview` for camera-free blockout evidence, `blender_render` or `blender_render_frames` for presentation/animation evidence, and `blender_export` for portable deliverables. - Run `blender_validate_scene` before export and `blender_validate_export` after export. For reference, wireframe, contour, multiview, UV, texture, look, repair, or animation QA, discover and run deterministic helpers through `blender_helper_catalog` and `blender_helper_run`. - If `blender_status.available` is false, stop and report the executable/configuration error. Do not claim Blender work completed while the backend is unavailable. - Every file path must stay inside the current dsh workspace unless the plugin was explicitly configured otherwise. Keep Poly Haven, Sketchfab, Hyper3D, Hunyuan3D, and other network asset or generation features disabled unless the user explicitly requests them. ## Follow the production workflow ### 1. Establish the target - Classify the input as text-only, single-image, multiview or orthographic, wireframe or technical drawing, texture or template pack, or an existing 3D asset. Combine modalities when the user supplies more than one. - Extract the subject, intended use, style, dimensions, reference priority, primary delivery format, target runtime, animation requirements, and quality bar. - Inspect every provided image before modeling. Record views, landmarks, silhouettes, part counts, material regions, uncertainties, and contradictions. - For a single image, state depth, scale, occlusion, and unseen-surface assumptions. For multiple images, register their view relationship before adding depth. - Use reversible defaults when missing information does not materially change the result. Ask one focused question only when a choice changes geometry, topology, animation, source-of-truth policy, or delivery. - Read [references/core/common-object-dimensions.md](references/core/common-object-dimensions.md) for common subjects; prefer user-provided or authoritative dimensions. ### 2. Inspect before mutating - Inspect the scene before the first write. Inspect each object in scope with `blender_object_info` and obtain a camera-free `blender_preview` when image capture is needed. - If the input is GLB/glTF, FBX, OBJ, STL, USD, PLY, or DAE, call `blender_import` and continue from its versioned `.blend` output. - Treat existing objects, collections, materials, lights, cameras, worlds, actions, and files as user-owned. - Do not clear the scene, reset the world, delete the default cube, or replace the camera merely because a recipe starts from a blank scene. - Delete startup content only when the user requested a fresh scene and inspection proves it is unchanged startup content. Otherwise create a task-specific collection and leave unrelated data alone. - Save a versioned checkpoint before broad or destructive work. Never overwrite the user's original `.blend` without explicit authorization. ### 3. Route and plan - For a complete scene or multi-stage asset, load `blender-pro-workflow` first, then the required domain modules. - For multi-module or source-locked work, load `blender-skill-harmonizer` so one module owns each decision and handoff. - For exact reference work, establish a source manifest and validation gates before creating geometry. Do not mix plausible freeform modeling with 1:1 reconstruction after fitting begins. - Define units, origin, up axis, long/broad/thin axes, object boundaries, stable names, collection ownership, modifier strategy, output paths, and validation views before e
Trust audit
BLOCKgrade D · trust 69/100 Do not install this without reading the findings. The audit found something that could harm you or your machine.
| Layer | What it checks | Result |
|---|---|---|
| L0 | Provenance & inventory | PASS |
| L1 | Static analysis of the code | FAIL |
| L2 | Instruction surface (what it tells the agent) | PASS |
| L3 | Class-specific surface | PASS |
| L4 | Behavioural (sandbox) | SKIPPED |
What the source does
- Filesystem
- none-observed
- Network
- none-observed
- Shell
- declared (1 observation(s))
- Dependencies
- pinned
- Secrets in source
- none-found
Findings (3)
exec(code, namespace, namespace)
Open [http://127.0.0.1:3080](http://127.0.0.1:3080), create a session whose workspace is the modeling directory, and ask dsh to use `create-3d-model`.
打开 [http://127.0.0.1:3080](http://127.0.0.1:3080)。新建以本仓库或你的建模目录为 workspace 的会话,然后输入:
Gates applied: no_behavioural_pass.
bb31944adda5full audit observations/trust-audit/skill/cheshirejcat__blender.json · Report an issue / request a re-scanAudit history
Every audit this skill has had.
| Date | Source | Verdict | Grade | Score | Change |
|---|---|---|---|---|---|
| 2026-10-12 | bb31944adda5 | BLOCK | D | 69 | first audit |
Questions
What does the blender skill do?
DeepSeek Harness plugin for complete Blender 3D modeling, reconstruction, rendering, validation, and export workflows
Is blender safe to install?
No — not without reading the findings first. The audit graded it D (69/100) and found 1 critical or high issue in the source. Each one is listed on this page with the file and line it is on.
What can blender access on my machine?
The audit observed that it runs shell commands. Each of those is consistent with what it says it does. Secrets in the source: none found.
Which assistants does blender work with?
Its documentation mentions claude-code and codex. That is what the text claims, not a compatibility test we ran.
How current is this page?
The grade is for one exact copy of the source (bb31944adda5), read on 2026-10-12. The repository is watched, and a new audit runs when it changes — this is the first audit.