跳至正文
OpenAgentSkill
浏览已开放 · 目录记录日期 2026-11-21 · 自动更新和账户服务暂时关闭。
开发与测试

blender-asset-studio

Build or refine a high-quality editable 3D model in Blender via Blender MCP from a brief, references and clarifications: staged blockout→pilot→finish, strict visual self-review against a target, executable repairs, export checks.

new-experement · 已有静态检查记录

安装与使用

运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。

npx skills add new-experement/blender-asset-studio --skill blender-asset-studio

技能说明


name: "blender-asset-studio" description: "Build or refine a high-quality editable 3D model in Blender via Blender MCP from a brief, references and clarifications: staged blockout→pilot→finish, strict visual self-review against a target, executable repairs, export checks."

Blender Asset Studio

Produce an editable model that survives close comparison with its target at the intended viewing conditions. Own the work from brief to delivery, including the critical review the user would otherwise have to request again and again. The result is judged by how it looks, not by how the process is reported.

Applies to props, vehicles, buildings, characters and asset families. Not for: a concept image alone, a plain export of an approved model (just export and check it), or engine programming.

Non-negotiable rules

  • Preserve the user's scope, primary references and protected features. Explicit user/project rules override the fallback choices here.
  • Look at actual pixels: references, and fresh renders of the current model. A filename, a summary or your own description of what you built is not visual evidence.
  • Separate maker and reviewer. A script that ran, a low triangle count or a confident narrative never passes the visual gate.
  • Artistic quality is judged against the visual target. Export fidelity is judged against the source. A perfect export of a weak model is still a weak model.
  • Every criticism becomes an executable repair: object/region, observed evidence, measurable target, operation, what must not change, how it will be verified.
  • A repair counts only after fresh evidence of the changed model. Old screenshots never certify a new revision.
  • Keep the best checkpoint. Running out of budget means delivering as incomplete with named defects, never relabeling a visible major defect as minor.
  • Spend geometry only where it can be seen and changes what is seen; nothing floats, nothing has visible gaps (see Modeling discipline).
  • Nothing grows into anything it shouldn't: no part of the asset passes through another part or through the objects it is used with (a hand through a wall, a chair leg through a tabletop, a wheel through the body). Touching is checked separately from penetration: parts that intersect look "connected" to a contact check and are still a defect. Only designed embeds with a recorded pair and depth are allowed.
  • Do not expand scope to hide weak execution: more props, more random damage, more polygons are not improvements by themselves.

Tools in this environment

NeedTool / approach
Startget_addon_status once: Blender version, enabled asset libraries and generators.
Scene factsget_scene_info with fields such as size, ground (floating/below), topology (ngons, non-manifold, loose verts), materials, modifiers, settings. Use it for measurements; don't estimate sizes from pictures.
Seeinglook: mode="angles" with views (front/back/left/right/top/three_quarter or [x,y,z]), mode="camera" for a fixed review camera, shading solid / material / rendered / wireframe, distance for close-ups, max_size (small for quick checks, larger for fine detail), image= to show a saved render or reference file.
Building, measuring, rendering to files, saving checkpoints, writing the ledgerexecute_blender_code in small steps that print what you need.
Materials and lightingsearch_assets / import_asset: Poly Haven CC0 textures and HDRIs first (use previews before importing). Sketchfab/Poly Pizza models only as reference or with an explicit license check. A library texture is a starting point, not a finished material.
Generated base meshgenerate_3d costs the user money or quota: use only with explicit permission. Its output arrives at arbitrary scale/facing and is a base or reference, never a finished asset; it goes through the same gates.
ReferencesUser attachments first; web image search for missing real-world references (record source and role).
Independent reviewRender evidence to files, then a separate reviewer agent (Agent tool) gets only the brief, the references and the renders, not the maker's notes. If a reviewer agent is not available, run a distinct sequential review pass and don't call it independent.

There is no image generation here. If a painted concept would help, offer: user-supplied art (e.g. made in another tool), a reference board assembled from search, or a quick 3D blockout shown as the concept checkpoint.

If Blender MCP is not reachable, finish the brief/reference work and say the modeling stage is not executed. Never deliver an illustration as a 3D model.

1. Intake: the brief

Read what's already available: the user's message, attachments, earlier answers, existing files and assets in the scene. Then ask one compact batch of only the questions that are actually open (usually 2-5). Never ask what was already answered; never pad the count.

Topics the brief must resolve:

TopicMust resolve
Subject and functionWhat it is, how it's used, key dimensions, variants, moving parts/states.
ReferencesExplicitly ask for 1-3 examples and what to take from each: form, materials, condition, overall quality. "No examples" is a valid answer; record it.
Style and conditionStylized/realistic; new, maintained, aged, damaged; where and how much. A genre word does not define the amount of damage.
Viewing and useClosest camera distance and screen size; allowed camera range (can it ever be seen from below, from behind, from inside?); does it stand on ground, set into it or mount on something; can it move, open, tip over, be entered or destroyed. These answers decide what may be simplified or removed. Which other objects it touches or is used with (wall, table, terrain, a character), and which poses/states must work.
Direction modeShow a concept/blockout for approval first, or decide autonomously and deliver.
阅读完整来源 ↗