meshy-dev/meshy-3d-agent / skills/meshy-3d-printing
meshy-3d-printing
VerifiedGenerates and prepares models for physical 3D printing with the Meshy CLI: white and multicolor prints (3MF, STL, OBJ), printability analysis and repair, splitting into parts, Creative Lab products such as figures, lamps and keychains, sizing, and slicer handoff (Bambu Studio, OrcaSlicer, PrusaSlicer, Cura). Use when the user wants something 3D-printed or asks for print or slicer files.
Meshy 3D Printing
Use Meshy CLI 0.8 (0.8.6 or later) 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, white or multicolor prints, analysis/repair, or splitting into parts | Printing recipes |
| Creative Lab products (figures, lamps, keychains, magnets, keycaps, fidgets) | Creative Lab |
| Cost, waiting, preview, delivery, or finding a previous model | Delivery |
| A chat that shows images or web pages (desktop or IDE agent apps), at delivery or when the user asks to see the model | Visual hosts |
| 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 a photo, a sketch or text | Photo: image-to-3d. Otherwise recommend a reference image first (multi-view when depth or sides matter), with text-to-3d as the quicker alternative; geometry without textures; analyze/repair as needed; prepare the file |
| Multicolor model | Generate/reuse geometry; analyze/repair as needed; texture; multi-color-print |
| Print in separate parts (build plate, colours per part, fewer supports) | Generate/reuse geometry; auto-split; slice the parts |
| Check or fix an existing model (holes, thin walls), any format | Free analyze-printability by task ID or --model-url; repair only if needed |
| Resize an existing STL, 3MF or GLB | Scale it in the slicer; only an OBJ is resized locally |
| Creative Lab figure (a stylized collectible from a photo), vinyl figure, brick figure, lamp, keychain, fridge magnet, keycap or pixel fidget board | Prototype → review → build → select product artifacts |
| Creative Lab collapsible fidget | One create from the photo → STL |
Colour routes differ: multicolor paints one object's surface for a multi-material printer; a split cuts it into parts, one filament each, and drops the texture (split before any repair; the two do not chain); the pixel fidget board is a product of its own.
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
In DeepSeek Harness with the Meshy plugin (DSH_MESHY_CLI is set) run every command as
"$DSH_MESHY_NODE" "$DSH_MESHY_CLI" …, never a meshy on PATH, install nothing, and sign in with
the meshy_sign_in tool. Everywhere else run meshy --version before the first command, without
asking; when it is missing or older than 0.8.6, install it with npm install -g meshy-cli@0.8
and say so in one line (Setup, section 1). Local-only work stops there.
Cloud work reuses a verified session. If login is needed, run auth login --device (with
--region cn for a user in mainland China) as Setup, section 3 describes: show its URL and user
code in commentary/progress, never a final answer, wait on that same command in this turn,
verify auth status, then resume the print job. Never ask for credentials in chat; only the CLI
touches its config directory.
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, with the printer type and print size when known so wall thickness is checked too; 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; cloud print files are scaled in the slicer (Printing recipes, Print size). 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, and a
local model must be GLB or glTF (multicolor: GLB); an STL, OBJ or FBX goes to Meshy only as an
http(s) URL.
Every command uses
--format json --no-update-checkand prints onemeshy.cli/v1envelope; 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.
- On the reference-image route, show the image and end your turn; make the model only once the user approves it. Picking the route is not approval of the image, and neither is your own look.
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. Where your chat
shows images or web pages, Visual hosts covers showing them there.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| slack-gif-creatoranthropics/skillsKnowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request animated GIFs for Slack like "make me a GIF of X doing Y for Slack." | Stars: 197k | Updated | Claude CodeCodex | Verified | Install |
| ponytailDietrichGebert/ponytailLazy senior dev mode for any coding task: the smallest change that fully solves it, and a reply a busy human understands in one read. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailHarvest every shortcut: comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailList every `shortcut:` comment (and older `ponytail:` ones) as a debt ledger. One-shot report, changes nothing. Use for "ponytail debt", "what did ponytail defer", "list the shortcuts", /ponytail-debt. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |