Update to Meshy 3D

{
  "description": "Generates and prepares models for physical 3D printing with Meshy: 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). Print preparation runs on the Meshy CLI; a host with only Meshy's hosted tools gets a model and its STL. Use when the user wants something 3D-printed or asks for print or slicer files.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 457
    },
    {
      "relative_path": "assets/meshy-composer-icon.svg",
      "size_in_bytes": 9376
    },
    {
      "relative_path": "references/creative-lab.md",
      "size_in_bytes": 7967
    },
    {
      "relative_path": "references/delivery.md",
      "size_in_bytes": 8851
    },
    {
      "relative_path": "references/printing.md",
      "size_in_bytes": 16992
    },
    {
      "relative_path": "references/setup.md",
      "size_in_bytes": 14209
    },
    {
      "relative_path": "references/tools.md",
      "size_in_bytes": 9630
    },
    {
      "relative_path": "references/troubleshooting.md",
      "size_in_bytes": 9834
    }
  ],
  "name": "meshy-3d-printing",
  "skill_md_contents": "---\nname: meshy-3d-printing\ndescription: \"Generates and prepares models for physical 3D printing with Meshy: 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). Print preparation runs on the Meshy CLI; a host with only Meshy's hosted tools gets a model and its STL. Use when the user wants something 3D-printed or asks for print or slicer files.\"\nlicense: MIT\ncompatibility: \"Print preparation: a terminal with network access, Node.js 22.12+ and the Meshy CLI 0.8.x, 0.8.5 or later (npm install -g meshy-cli@0.8.5). Without one: a host connected to Meshy's MCP server.\"\n---\n\n# Meshy 3D Printing\n\nDeliver the requested print files at the intended size, with analysis/repair results where\napplicable and a slicer handoff when requested. This skill is self-contained. Ordinary digital\nassets belong to meshy-3d-generation.\n\n## How to run it\n\nPrint work is CLI work: sizing, analysis and repair, splitting, multicolor files, Creative Lab\nand the slicer all need Meshy CLI **0.8** (0.8.5 or later). Meshy's hosted tools make and\ndownload models; they do not prepare a print.\n\n| This session has | Run |\n|---|---|\n| A terminal | A new print job runs on the CLI from its first step, as the sections below describe, whether or not Meshy's hosted tools are also listed: its recipes set output formats at creation that the tools do not have. When the `meshy` command is missing, install it; that is the normal first run, not a reason to decline. A model the tools already made continues on the CLI from its task ID, after the account check in [Tools](references/tools.md), *Continuing on the CLI* |\n| Meshy's hosted tools (`image_to_3d`, `get_task`, `download_model`; a host may list them with a prefix, as in `meshy_3d_image_to_3d`) and no terminal | The model only: an untextured model from the photo or a reference image, and its STL download as the handoff ([Tools](references/tools.md)). Say that sizing, analysis, repair, multicolor files and the slicer are not available in this environment, and never call the model printable |\n\n**The tools not offering a step never means Meshy cannot do it.** With a terminal, run\n`meshy --version`, install the CLI when it is missing, and check `auth status`, all as *Cloud\nauthorization* says, before telling the user that anything is unavailable.\n\nThe CLI counts as not working only after that was tried: the install was refused and the\ntemporary package failed too, or the terminal cannot reach Meshy (a sandbox without network\naccess, for one). Then say which of these happened, and treat the session as the second row.\n\n| Need | Reference |\n|---|---|\n| The hosted tools, and continuing on the CLI from a model they made | [Tools](references/tools.md) |\n| CLI runner, credentials, or output location | [Setup](references/setup.md) |\n| Local preparation, white or multicolor prints, analysis/repair, or splitting into parts | [Printing recipes](references/printing.md) |\n| Creative Lab products (figures, lamps, keychains, magnets, keycaps, fidgets) | [Creative Lab](references/creative-lab.md) |\n| Cost, waiting, preview, delivery, or finding a previous model | [Delivery](references/delivery.md) |\n| Failed or uncertain operation | [Troubleshooting](references/troubleshooting.md) |\n\nRead relevant sections as needed. Recipes illustrate valid commands; select only the stages\nneeded for the user's output.\n\n## Choose local or cloud work\n\n| Request | Route |\n|---|---|\n| Scale, orient or ground an existing OBJ | Local `mesh prepare-print`; no auth or balance |\n| Open an existing STL or 3MF | Local `slicer detect` and `slicer open`; no auth or balance |\n| 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 |\n| Multicolor model | Generate/reuse geometry; analyze/repair as needed; texture; multi-color-print |\n| Print in separate parts (build plate, colours per part, fewer supports) | Generate/reuse geometry; auto-split; slice the parts |\n| Check or fix an existing model (holes, thin walls), any format | Free analyze-printability by task ID or `--model-url`; repair only if needed |\n| Resize an existing STL, 3MF or GLB | Scale it in the slicer; only an OBJ is resized locally |\n| 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 |\n| Creative Lab collapsible fidget | One create from the photo → STL |\n\nColour routes differ: multicolor paints one object's surface for a multi-material printer; a\nsplit cuts it into parts, one filament each, and drops the texture (split before any repair;\nthe two do not chain); the pixel fidget board is a product of its own.\n\nA figurine does not by itself require Creative Lab. Infer the route from the intended product;\nask about size, color or style only when the missing choice materially changes the result.\nFor an existing model, distinguish local preparation from cloud printability analysis; a\nlocal dimension check cannot establish full printability.\n\n## Cloud authorization\n\nIn DeepSeek Harness with the Meshy plugin (`DSH_MESHY_CLI` is set) run every command as\n`\"$DSH_MESHY_NODE\" \"$DSH_MESHY_CLI\" …`, never a `meshy` on PATH, install nothing, and sign in with\nthe `meshy_sign_in` tool. Everywhere else run `meshy --version` before the first command, without\nasking; when it is missing or older than 0.8.5, install it with `npm install -g meshy-cli@0.8.5`\nand say so in one line ([Setup](references/setup.md), section 1). Local-only work stops there.\n\n**Keep the CLI current.** An older CLI lacks commands these references use. A version older than\n0.8.5 is upgraded before anything else, not worked around; say which version it replaced. Once\nper conversation, unless you installed it just now, also look for a newer 0.8 release\n(`npm view meshy-cli@0.8 version --json`; the last entry is the newest). When there is one,\nrecommend it to the user in one line with its command, `npm install -g meshy-cli@VERSION`, and\nrun that when they agree. Do not hold the job for the answer.\n\nCloud work reuses a verified session. If login is needed, run `auth login --device` (with\n`--region cn` for a user in mainland China) as Setup, section 3 describes: show its URL and user\ncode in **commentary/progress, never a final answer**, wait on that same command in this turn,\nverify `auth status`, then resume the print job. Never ask for credentials in chat; only the CLI\ntouches its config directory.\n\n## Printing-specific constraints\n\n- Repair changes geometry and drops textures. Use repaired geometry downstream and retexture\n  before multicolor output. Use analysis when functional parts, thin features or other\n  requirements make it relevant, with the printer type and print size when known so wall\n  thickness is checked too; its report does not establish material suitability.\n- Prepare a Y-up OBJ as a new Z-up file at the requested height, centered and grounded. Do not\n  repeat the transform or apply it to STL, 3MF, or relief product output. A multicolor 3MF\n  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\n  Printing recipes.\n- API, downloads and geometry operations use the CLI. Local inputs have a 50 MiB limit, and a\n  local model must be GLB or glTF (multicolor: GLB); an STL, OBJ or FBX goes to Meshy only as an\n  http(s) URL.\n  Every command uses `--format json --no-update-check` and prints one `meshy.cli/v1` envelope;\n  writes carry the resolved `--workspace WORKSPACE`. Read returned paths and IDs rather than\n  guessing.\n- Submit cloud tasks once with `create --async`, retain their resource and lineage, and `wait`\n  on the same task. Keep the turn active during waits. Unknown submission and interrupted\n  downloads are recovery cases, not permission to generate again.\n- Work within the approved scope and budget; propose additional paid stages before spending.\n  Delivery describes applicable estimates. Local preparation and printability analysis are free.\n\n## Finish the handoff\n\nShow an available rendered preview and deliver file paths, dimensions, analysis/repair status\nand reported charges. Launch a detected slicer only when requested or already authorized;\n`launch_requested` does not prove successful import or start a physical printer. If no suitable\nslicer is installed, still deliver the files. Explain relevant remaining checks, such as supports\nand wall thickness, without describing an untested model as guaranteed printable.\n"
}