meshy-3d-printing
meshy-dev/meshy-3d-agent
Generate and prepare 3D models for physical printing with Meshy CLI, supporting white/multicolor prints and slicer handoff.
What is meshy-3d-printing?
This skill uses Meshy CLI 0.4.0 to generate 3D models from text or images, prepare existing models for printing, and handle slicer integration. Use it when you need to create print-ready files at specified dimensions, analyze printability, repair geometry, or deliver files to slicing software.
- Generate white or multicolor 3D models from text descriptions or photos
- Prepare and transform existing OBJ, STL, or 3MF files for printing (scale, orient, ground)
- Analyze and repair geometry to improve printability
- Create Creative Lab products (lamps, keychains, magnets, figures) with templated workflows
- Detect and launch compatible slicers for direct handoff to printing software
How to install meshy-3d-printing
npx skills add https://github.com/meshy-dev/meshy-3d-agent --skill meshy-3d-printing- Meshy CLI 0.4.0 installed or accessible via npm
- Meshy account credentials for cloud-based generation and multicolor workflows
- Local file input limited to 50 MiB
How to use meshy-3d-printing
- 1.Determine whether your task requires local preparation (scale/orient) or cloud generation (new models, multicolor, Creative Lab)
- 2.For local work: use `mesh prepare-print` to transform OBJ files or `slicer detect`/`slicer open` to work with existing STL/3MF files
- 3.For cloud work: authenticate with `auth login --device` if needed, then submit generation or product tasks with `create --async`
- 4.Monitor cloud tasks with `wait` and retain resource IDs and lineage throughout the session
- 5.Review the rendered preview, verify dimensions and repair status, then deliver file paths and launch slicer if requested
Use cases
- Convert a text description into a print-ready multicolor 3D model with texture and repair
- Scale and reorient an existing OBJ file to specified dimensions and prepare it for slicing
- Generate a figurine from a photo, analyze its printability, and deliver to a slicer
- Create a Creative Lab lamp prototype, review it, build the final product, and export artifacts
- Analyze an existing STL for printability issues before sending to a 3D printer
- 3D printing enthusiasts and hobbyists
- Product designers preparing models for manufacturing
- Users wanting to generate custom figurines or decorative objects
- Anyone integrating 3D model generation into a larger workflow
meshy-3d-printing FAQ
No. Local preparation (scaling, orienting OBJ files) and opening existing STL/3MF files require no authentication or balance. Cloud work (generating new models, multicolor printing, Creative Lab products) requires a verified Meshy session.
Repair changes the geometry and removes textures. If you need multicolor output, retexture the repaired geometry before proceeding to multicolor printing.
No. Digital asset generation without printing intent belongs to the meshy-3d-generation skill. This skill is specifically for print preparation and delivery.
Input formats include OBJ, STL, and 3MF. Output is typically STL or 3MF for slicing, with product workflows delivering ZIP files containing artifacts.
Local preparation and printability analysis are free. Cloud generation and product workflows incur charges; the skill will propose additional paid stages and report costs before spending.
Full instructions (SKILL.md)
Source of truth, from meshy-dev/meshy-3d-agent.
name: meshy-3d-printing description: Generate or prepare models for physical 3D printing, including white or multicolor prints, Creative Lab products, sizing, and slicer handoff. license: MIT
Meshy 3D Printing
Use Meshy CLI 0.4.0 to deliver the requested print files at the intended size, with analysis/repair results where applicable and a slicer handoff when requested. This skill is self-contained. Ordinary digital assets belong to meshy-3d-generation.
| Need | Reference |
|---|---|
| CLI runner, credentials, or output location | Setup |
| Local preparation, cloud generation, or product workflow | Printing recipes |
| Cost, waiting, preview, delivery, or finding a previous model | Delivery |
| Failed or uncertain operation | Troubleshooting |
Read relevant sections as needed. Recipes illustrate valid commands; select only the stages needed for the user's output.
Choose local or cloud work
| Request | Route |
|---|---|
| Scale, orient or ground an existing OBJ | Local mesh prepare-print; no auth or balance |
| Open an existing STL or 3MF | Local slicer detect and slicer open; no auth or balance |
| White model from text or photo | Generate geometry without textures; analyze/repair as needed; prepare the file |
| Multicolor model | Generate/reuse geometry; analyze/repair as needed; texture; multi-color-print |
| Creative Lab lamp, keychain, fridge magnet or figure template | Prototype → review → build → select product artifacts |
A figurine does not by itself require Creative Lab. Infer the route from the intended product; ask about size, color or style only when the missing choice materially changes the result. For an existing model, distinguish local preparation from cloud printability analysis; a local dimension check cannot establish full printability.
Cloud authorization
Resolve the runner automatically using Setup (compatible meshy or
npm exec --yes --package=meshy-cli@0.4.0 -- meshy …). Local-only work stops at runner setup.
Cloud work reuses a verified session. If login is needed, keep auth login --device running,
show its URL and user code in commentary/progress, never a final answer, and await the
same tool session in this turn. After it exits, verify auth status and resume the print job.
Do not ask for a "done" message or credentials in chat; Setup has the host wait procedure.
Printing-specific constraints
- Repair changes geometry and drops textures. Use repaired geometry downstream and retexture before multicolor output. Use analysis when functional parts, thin features or other requirements make it relevant; its report does not establish material suitability.
- Prepare a Y-up OBJ as a new Z-up file at the requested height, centered and grounded. Do not repeat the transform or apply it to STL, 3MF, or relief product output. A multicolor 3MF requires no OBJ conversion. Product ZIPs and optional lamp bases have distinct handling in Printing recipes.
- API, downloads and geometry operations use the CLI. Local inputs have a 50 MiB limit.
Business commands use
--output-schema v1 --format json --no-update-check; writes carry the resolved--workspace WORKSPACE. Read returned paths and IDs rather than guessing. - Submit cloud tasks once with
create --async, retain their resource and lineage, andwaiton the same task. Keep the turn active during waits. Unknown submission and interrupted downloads are recovery cases, not permission to generate again. - Work within the approved scope and budget; propose additional paid stages before spending. Delivery describes applicable estimates. Local preparation and printability analysis are free.
Finish the handoff
Show an available rendered preview and deliver file paths, dimensions, analysis/repair status
and reported charges. Launch a detected slicer only when requested or already authorized;
launch_requested does not prove successful import or start a physical printer. If no suitable
slicer is installed, still deliver the files. Explain relevant remaining checks, such as supports
and wall thickness, without describing an untested model as guaranteed printable.
Related skills
More from meshy-dev/meshy-3d-agent and the wider catalog.
meshy-3d-generation
Generate and edit 3D models, textures, rigging, and animations using Meshy CLI.
add-malli-schemas
Add Malli schemas to Metabase API endpoints with proper validation patterns and error handling
analytics-events
Add Snowplow analytics events to track user interactions in Metabase frontend.
clojure-review
Review Clojure/ClojureScript code against Metabase style standards and quality guidelines.
clojure-write
Guide Clojure/ClojureScript development with REPL-driven workflow, conventions, and best practices.
docs-review
Review documentation changes against Metabase's writing style guide.