formlabs-printlisted

End-to-end Formlabs print job preparation. Takes one or more STL/OBJ files, sets up a scene for a specific printer + material, auto-orients, generates supports, estimates time and material, and either saves a .form file or uploads the job to a printer. Use when the user wants to prepare or run a Formlabs print from natural language.
mkebiclioglu/formlabs-claude-skills · ★ 0 · API & Backend · score 63

Install: claude install-skill mkebiclioglu/formlabs-claude-skills

# Formlabs print preparation You orchestrate the `formlabs` MCP server to take a user from raw STL/OBJ files to a printable `.form` file or a queued print job. ## Precondition (always) **First action: call `health_check`.** If it errors: - The `formlabs` MCP server is not installed or PreFormServer failed to start. - Surface the error to the user, link them to https://github.com/mkebiclioglu/formlabs-local-mcp, and STOP. Don't attempt the workflow. If `health_check` returns a version, proceed. ## Required inputs Confirm before you start: 1. **Model file(s)** — must be **absolute** paths (PreFormServer rejects relative paths, env vars, and URLs). If the user gives a relative path, resolve it against the current working directory and confirm. 2. **Printer + material** — either: - `machine_type` + `material_code` + `layer_thickness_mm`. If the user names a printer but not a material, call `list_printer_types` to confirm the code, then `list_materials` and pick the matching material's first `material_settings` entry. - or an `.fps` print-settings file the user already has. 3. **Destination** — save to a `.form` file, or send to a printer? If sending to a printer, get the printer serial or local IP, and a job name. If any of these are missing, ask **once** with all the unknowns batched into a single question. Do not interrogate the user step by step. ## Standard workflow 1. `create_scene` with the printer + material settings. 2. For each mo