3d-printinglisted
Complete 3D pipeline for Bambu Lab printers; the only skill for 3D work. Use for any .stl or .3mf file, or to scale, resize, recolor, change filament colors, mirror, rotate, split, merge, repair, measure, or add/resize magnet holes - even if the format isn't named. Also designing printable parts (bins, organizers, brackets, mounts, gridfinity), build123d CAD, MakerWorld - browse models, find me a model - print prep and printing - slice, print, fit on one plate, multi-object plate, batch print night, check printer, what's printing, AMS - troubleshooting - stringing, warping, bed or layer adhesion, support removal, clogs, elephant foot, ringing, under-extrusion, this keeps happening - and the print log: log this print, what settings did I use, what worked for this filament, did I fix this before, filament usage. When scaling, holds hardware interfaces (Maker's Supply parts, MH011 movement, bearings, inserts) and magnet holes at original size while the body scales. Defaults to a Bambu Lab H2C with PETG.
TrillyD13/3d-printing-skill · ★ 3 · AI & Automation · score 71
Install: claude install-skill TrillyD13/3d-printing-skill
# 3D Printing
Edit, design, prepare and print 3D files the way a careful machinist would:
measure first, confirm intent, protect functional interfaces, verify after.
This skill is one entry point for the whole loop: editing and designing files,
preparing and running prints, and keeping the print log that makes the second
attempt at anything cheap. Deliberately one skill rather than four — the paths
share too much context to split. The one thing it hands off is **cad-khana**,
for multi-part mechanical assemblies; see Designing new parts.
**For mesh work the local Python stack is the primary path.** For printing, the
`Bambu_Printer` MCP is, when it is live — it slices with a real `h2c` profile and
drives the printer. Other externals (OrcaSlicer CLI, OpenSCAD MCP, render server)
are useful when present and frequently absent, and the failure is silent until
you are deep into a job. Preflight decides the local paths; `ListConnectors`
decides the MCP ones. See `references/external_tools.md`.
## Step 0 — preflight, every run, before promising anything
```bash
python scripts/preflight.py
```
It reports which capabilities are live and prints the fallback for each that is
not. Run it before you tell the user what you are going to do, not after you
have failed to do it. It costs a second and it is the difference between
"here's your file" and "actually, I can't."
Non-negotiables it enforces:
- **Never fabricate a machine profile to make a slicer run.** If no profile for
the us