Formlabs print prep (save only)

A non-destructive version of the formlabs-print workflow: same preparation pipeline, but always saves a .form file at the end instead of sending to a printer. Use this when the user wants to inspect the job in PreForm first, or batch-prepare jobs to print later.

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, link the user to https://github.com/mkebiclioglu/formlabs-local-mcp, and STOP.

Required inputs

1. Model file(s) — absolute paths.
2. Printer + material — same as formlabs-print. If the user names a

printer but no material, call list_printer_types to confirm the code, then list_materials and surface the available materials for that printer so they can pick.

1. Output `.form` path — absolute path. If they don't specify, default to

the model's directory with the same basename and .form extension, and confirm.

Workflow

1. health_check (precondition).
2. create_scene.
3. import_model for each input file. The server defaults repair_behavior=REPAIR

and units=MILLIMETERS — leave them unless the user explicitly says otherwise.

1. auto_orient.
2. auto_support.
3. auto_layout (SLA, machine_type starts with FORM-) or auto_pack

(SLS, starts with FS).

1. get_print_validation — surface errors/warnings.
2. Auto drain holes (SLA only): call auto_add_drain_holes to place drain

holes for any cups reported by validation. Skip the user XYZ prompt — bbox sampling + PreForm's surface projection handle placement. If PreForm reports "no surface found" for a model, surface that to the user and offer add_drain_holes (hand-placed) as fallback.

1. estimate_print_time — report time and material usage.
2. save_form to the chosen path. Skip the confirmation if the path is new;

ask before overwriting an existing file.

1. Optionally save_screenshot to a .png next to the .form for preview.

When to use this vs formlabs-print

• User mentions "save", "prepare", "set up", "draft", "preview" → this skill.
• User mentions "print", "send to printer", "kick off the job" → use

formlabs-print.

• Ambiguous → ask once which they want.

Things to avoid

• Don't use TaskCreate for this flow. Short linear pipeline; overhead.
• Don't loop retries on IMPORT_PRODUCED_EMPTY_SCENE — that error means

the STL is genuinely malformed and the post-import verification caught it. Tell the user, stop, and let them open the file in PreForm to diagnose.

• Don't invent machine_type or material_code values. Use

list_printer_types / list_materials to get real values.