What problem does it solve? Sending a sliced G-code file to a Bambu Lab printer over the local network involves undocumented FTPS and MQTT handoffs, and a wrong payload can silently fail or start an unsafe print. This Skill provides a dry-run-first workflow that validates G-code, inspects printer status, uploads files, and cautiously initiates or controls print jobs on local Bambu printers. ## Core Features & Use Cases - Dry-run-first handoffs: Every send, pause, cancel, and clear-error command defaults to a non-networked dry-run plan; live printer traffic requires explicit --execute and confirmation flags. - Multiple handoff modes: Supports template-project (validated on A1 Mini), plain G-code upload, and bambox-project packaging for enabled printer profiles like P1S. - Printer onboarding and status: Guides users through enabling LAN Only and Developer Mode, stores credentials in a local bambu-printers.json, fetches the serial from the printer TLS certificate, and reads live printer status via MQTT. - Use Case: After slicing a model to plain G-code with OrcaSlicer, dry-run the upload-start plan for an A1 Mini, verify the payload, upload the project to the FTPS root, then start the print and monitor the first layer. ## Quick Start Ask the agent to dry-run a Bambu Lab handoff for your validated G-code file, for example: "Use the bambu-labs skill to dry-run uploading and starting /tmp/job.gcode on my configured a1-mini printer."
