← ClaudeAtlas

bambu-labslisted

Dry-run, upload, and cautiously initiate local Bambu Lab print jobs from validated plain `.gcode`, using Bambu LAN FTPS/MQTT handoffs.
baibai2013/build123d-cad · ★ 2 · AI & Automation · score 65
Install: claude install-skill baibai2013/build123d-cad
# Bambu Labs Provenance: maintained in [earthtojake/text-to-cad](https://github.com/earthtojake/text-to-cad). Use the installed local skill files as the runtime source of truth; the repository link is only for provenance and release review. Use this skill for local-network Bambu Lab print handoffs after a plain `.gcode` file already exists and has been validated. This skill does not slice models. ## Safety Rules - Default to dry-run plans. Real printer traffic requires `--execute`. - Never start a print without `--execute --confirm-start-print`. - Pause and cancel controls are live printer requests; default to dry-run plans. Canceling a print requires `--execute --confirm-cancel-print`. - Treat an explicit user request to print or start a specific job as live-start authorization; do not pause for a second confirmation solely for physical checks. Still validate the G-code, inspect the dry-run payload, read printer status, prefer upload-only before upload-start, state the physical checks, and stop if validation/status/intent is unsafe or ambiguous. - Do not ask for the printer serial by default; fetch it from the printer TLS certificate with `serial` or let `send` cache it. - Prefer workspace-root `bambu-printers.json` over repeating access codes in commands. The file is local config and should be ignored by Git. - Before a live start, state the physical checks: clear build plate, correct plate/filament/nozzle, safe surroundings, and operator nearby. - Publishing