sculpt
Skill2 starsChanged 25 days agoMITView on GitHub
Use when an organic shape (skull, character, flowing form) must be built or made printable in Blender headless (watertight, minimum wall, remeshed, split only at natural boundaries). Runs the organic-modeler in a fresh context and writes STL, script and report to the named folder.
In this repository30 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- agent-reviewSkill
- ai-mesh-cleanSkill
- cad-buildSkill
- couponSkill
- curriculumSkill
- dfm-reviewSkill
- fileSkill
- gddSkill
- ip-checkSkill
- led-budgetSkill
- lesson-learnedSkill
- makerworld-publishSkill
- material-pickSkill
- mcp-new-toolSkill
- ortho-sheetSkill
- pi-power-budgetSkill
- preprint-checkSkill
- promo-planSkill
- qa-gateSkill
- render-criticSkill
- research-oneSkill
- research-topicSkill
- retopoSkill
- safety-sheetSkill
- slicer-questionSkill
- style-bibleSkill
- tech-packSkill
- unit-costSkill
- verifySkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 1 is distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 18
Verify with .venv\Scripts\python.exe and trimesh (is_watertight, is_volume, bounds).
- Distinctive: line 19
If no orientation prints clean, propose a split ONLY at natural part boundaries (separate characters, accessories, bases), with keyed …
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Overview
Input: $ARGUMENTS as <output folder> | <brief>. Output: <folder>\<name>.stl, the Blender script beside it, and report.md (watertight, bounds, min wall, overhang map, split proposal).
Blender comes from config\paths.yaml (blender_exe) through tools\mm_config.py. If it is empty, stop and say Blender is not configured.
When to use
Organic geometry. Not for hard-surface parts (/cad-build) and not for cleaning AI or scanned meshes (/ai-mesh-clean).
Steps
- Build in Blender headless (
<blender_exe> -b -P <script>); voxel remesh; make watertight; thicken to the minimum wall. - Verify with
.venv\Scripts\python.exeand trimesh (is_watertight,is_volume, bounds); estimate min wall by ray casting; overhang map per orientation against the overhang threshold inknowledge\02-bambu-studio\support-settings.md. - If no orientation prints clean, propose a split ONLY at natural part boundaries (separate characters, accessories, bases), with keyed joints (pins, sockets, pockets) and clearances from a printed coupon. Never a plane cut through a sculpture, a face, hair or the main body.
- Save the script beside the STL; write
report.md; return the path and numbers.
Common rationalizations
| Rationalization | Reality |
| "It looks closed in the viewport." | Only is_watertight and is_volume count. |
| "1.2 mm is the usual minimum." | Minimum wall depends on material and nozzle; label it ASSUMED until a coupon measures it. |
| "A flat cut through the middle avoids all support." | Plane cuts through the sculpture are rejected. Split at natural boundaries or reorient. |
Red flags
- Min wall stated without a method.
- Blender GUI steps instead of a saved script.
- A proposed split plane crossing the main body, a face or hair.
Verification
- STL watertight and
is_volume; height within 0.1 mm of spec. - Min wall and overhang table in
report.md. - Any split is at a natural boundary with keyed joints.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

