What does this skill do, and when should you use it?
One of 13 skills bundled in the earthtojake/text-to-cad monorepo, this skill solves a narrow problem: how an agent hands a print job to a Bambu Lab printer. Because Bambu firmware accepts third-party print jobs only through the official Bambu Connect desktop app (or Bambu Studio), the skill teaches the agent to build a bambu-connect://import-file link for sliced files, or to open unsliced models in Bambu Studio. The user picks the printer and starts the print in the app; the agent never asks for access codes and never reports a print as started. Both Bambu Cloud and LAN printer connections are covered.
- Reads a user-supplied .gcode.3mf (sliced plate export) or plain .gcode, then builds and opens a bambu-connect://import-file link (path/name percent-encoded like encodeURIComponent, plus version=1.0.0), launching Bambu Connect with
openon macOS or Start-Process on Windows - For unsliced .3mf, .stl or .step models, opens Bambu Studio instead:
open -a BambuStudio <file>on macOS,bambu-studio <file>on Linux, file menu or Start-Process on Windows - Falls back to slicing in Bambu Studio when Bambu Connect refuses a plain .gcode
- Prompts the user, before pressing Print, to check printer, plate type, nozzle, filament and AMS mapping, a clear build plate, and someone nearby for the first layer
- Explicitly out of scope: starting/pausing/cancelling prints, reading printer status, or requesting access codes
- A desktop user with a .gcode.3mf sliced in OrcaSlicer or Bambu Studio who wants the agent to hand the file to Bambu Connect in one step
- An engineer holding only a .stl/.step model who wants it opened directly in Bambu Studio for slicing and sending
- Users whose printer runs in LAN mode and want to avoid the cloud — both connection modes are supported
- Linux users, where Bambu Connect is still in development; the skill explicitly routes them to Bambu Studio
- Security-conscious teams that don't want an agent holding printer access codes or starting prints on its own
- Anyone wanting the agent to start, pause or cancel prints or read printer status remotely — Bambu firmware only allows that via Bambu Connect or the LAN-only Developer Mode, which this skill lists as out of scope
- Environments without Bambu Connect (Windows 10+/macOS 13+) or Bambu Studio, or without a signed-in Bambu Lab account
- Workflows that need slicing itself — this skill does not slice; use the sibling $gcode skill or Bambu Studio
How do you install this skill?
- This is a static source review; no commands were executed and no apps opened, so the `bambu-connect://import-file` URL scheme's actual behavior is unverified.
- The skill requires Bambu Connect signed in to a Bambu Lab account; confirm account and network reachability (especially in mainland China) yourself, and prefer LAN mode where possible.
- The agent cannot see the printer or print status; never assume a print started before confirming in the official app.
- The publisher is not verified by the FollowSkills registry and identity is unknown; review the repository yourself before use.
- Shell / CLI
- Local filesystem
Bambu Connect (Windows 10+/macOS 13+) signed in to a Bambu Lab account, or Bambu Studio (incl. Linux)
This skill ships as part of the text-to-cad collection (skill file at skills/bambu-labs/SKILL.md). The source documents no command for installing this one skill alone; below are the collection-level install routes:
Claude Code
claude plugin marketplace add earthtojake/text-to-cad#latest
claude plugin install text-to-cad@earthtojakeCursor
git clone --depth 1 --branch latest https://github.com/earthtojake/text-to-cad ~/.cursor/plugins/local/text-to-cadGrok Build
grok plugin install earthtojake/text-to-cad@latest --trust
grok plugin enable text-to-cadGemini
gemini extensions install https://github.com/earthtojake/text-to-cad --ref latest --consent --auto-updateOther agents (Skills CLI)
npx skills add earthtojake/text-to-cad#latestCodex: install from Codex's plugin directory ("text-to-cad for Codex"), or manually via codex plugin marketplace add earthtojake/text-to-cad --ref latest then codex plugin add text-to-cad@earthtojake.
How do you use this skill?
Once installed, send your agent any of these to trigger it:
- Send /Users/me/prints/bracket.gcode.3mf to my Bambu printer
- I have a bracket.step model — open it in Bambu Studio and get it printing
- Hand this sliced plate.gcode.3mf off through Bambu Connect
- This model.stl isn't sliced yet, use the Bambu Studio path to print it
The skill picks a handoff path by file type (per the SKILL.md decision table):
- .gcode.3mf or a .gcode sliced with the printer's Bambu profile → build an import-file link for Bambu Connect:
bambu-connect://import-file?path=%2FUsers%2Fme%2Fprints%2Fbracket.gcode.3mf&name=bracket&version=1.0.0(path is the absolute file path; path and name are percent-encoded like JavaScript's encodeURIComponent or Python's urllib.parse.quote(value, safe=""))
- Open the link on macOS:
open "<link>"- Open the link on Windows:
Start-Process "<link>"- Hand an unsliced model to Bambu Studio:
open -a BambuStudio <file>bambu-studio <file>The user then picks the printer and starts the print in the app; the agent only opens the file and walks through the pre-print checklist, and never claims a print has started.
What are this skill's strengths and limitations?
- Uses Bambu's official third-party integration path (Bambu Connect) — no access codes, no firmware workarounds
- Covers both cloud and LAN printers, with a Bambu Studio fallback for Linux where Bambu Connect is unavailable
- Built-in decision table routes the correct app by file type (sliced vs unsliced; .gcode.3mf/.gcode/.3mf/.stl/.step)
- Thoughtful safety guardrails: a pre-print checklist and an explicit rule against falsely reporting print status
- The agent never sees the printer or print progress; the final actions depend entirely on the user in the app
- Bambu Connect is still in development on Linux, so Linux users are limited to the Bambu Studio path
- Bambu Connect may refuse plain .gcode files, forcing a re-slice in Bambu Studio
- The skill does not slice; slicing depends on the sibling $gcode skill (OrcaSlicer) or Bambu Studio
How does this skill compare with similar options?
Side by side with related skills; every score comes from the same FSRS standard.
| Skill | FS score | Stars | Last updated | License |
|---|---|---|---|---|
| Bambu Labs Print Handoff Skill this page | 60 · Recommended | ★ 19k | 1d ago | MIT |
| G-code Slicing Skill (text-to-cad) | 60 · Recommended | ★ 19k | 1d ago | MIT |
| neat-freak — Knowledge & Governance Closeout | 63 · Recommended | ★ 21k | 10d ago | MIT |
| Stripe Connect Integration Advisor | 57 · Use with care | ★ 1.9k | 3d ago | MIT |
| NeMo MBridge MoE VLM Training Guide ✓ NVIDIA · Official | 57 · Use with care | ★ 3.5k | 3d ago | Apache-2.0 |
The sibling G-code skill in the same repo handles slicing (producing printer-ready G-code with OrcaSlicer); this skill is its downstream step, handing the sliced file to a Bambu Lab printer. They complement each other — this skill does no slicing itself.
How did FollowSkills review this skill?
Least-privilege design: the agent only opens files via a `bambu-connect://` URL or `open`/`Start-Process`; it never touches printers, never asks for access codes or credentials, and print start/confirmation stays with the user in Bambu Connect/Bambu Studio. The skill explicitly instructs the agent to tell the user what to check before printing and never to claim a print started. Deductions: SKILL.md does not discuss local-file read boundaries (absolute paths are passed into the URL) or behavior on abnormal input (missing files, non-Bambu gcode).
Instructions are self-consistent with explicit percent-encoding rules; a fallback is given when Bambu Connect refuses a plain `.gcode`; commands cover macOS, Windows and Linux. Deductions: the URL scheme depends on external app versions, there are no committed tests covering this skill's key path, and failure behavior for missing files or encoding errors is not described.
Frontmatter triggers are precise (printing a sliced `.gcode.3mf`, Bambu `.gcode`, or unsliced model over cloud or LAN), with an explicit 'Out of scope' section and a decision table mapping file types to handoffs. Deductions: cloud path requires a Bambu Lab account sign-in and mainland-China reachability of Bambu Cloud is not addressed; Linux boundary still relies on external docs.
Well-layered docs: frontmatter, requirements, decision table, platform commands, pre-print checklist and scope statement. MIT license and repository provenance are present. Deductions: no per-skill version, changelog or known-limitations list (e.g., Bambu Connect version compatibility); maintenance responsibility is only implied at the repository level.
The handoff delivers sliced files to the official app where the user starts the print; output is directly usable, and the skill honestly states the agent cannot see print progress. Marginal value lies in saving the user from discovering the URL scheme. Deductions: static review cannot verify the URL scheme works in the current Bambu Connect, and the task is only a file handoff with limited scope.
Bambu official wiki links corroborate the third-party integration mechanism, and the repo shows a CI test badge, but committed tests are CAD-generator fixtures that do not cover this skill's handoff path. Deductions: the key claim (URL scheme behavior) has a single source and no committed test evidence; static review cannot independently reproduce it.
Open a dimension to read why it scored that way
Evidence confidence：Low — Mostly static review, author material or a limited demo; useful for discovery, not high-risk decisions.
See the full review method →