Update to Meshy 3D

{
  "description": "Generates and edits digital 3D assets with Meshy: text-to-3D and image-to-3D models, reference images, texturing, remeshing and LODs, UV unwrapping, format conversion (GLB, FBX, OBJ, USDZ, STL, 3MF, Blender), rigging, animation and motion clips from text. Uses Meshy's hosted tools first and the Meshy CLI for what they do not do. Use when the user asks to make, texture, rig, animate, convert, find or download a 3D model or game asset. For physical 3D printing use meshy-3d-printing.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 455
    },
    {
      "relative_path": "assets/meshy-composer-icon.svg",
      "size_in_bytes": 9376
    },
    {
      "relative_path": "references/animation.md",
      "size_in_bytes": 4438
    },
    {
      "relative_path": "references/delivery.md",
      "size_in_bytes": 8851
    },
    {
      "relative_path": "references/pipelines.md",
      "size_in_bytes": 20934
    },
    {
      "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-generation",
  "skill_md_contents": "---\nname: meshy-3d-generation\ndescription: \"Generates and edits digital 3D assets with Meshy: text-to-3D and image-to-3D models, reference images, texturing, remeshing and LODs, UV unwrapping, format conversion (GLB, FBX, OBJ, USDZ, STL, 3MF, Blender), rigging, animation and motion clips from text. Uses Meshy's hosted tools first and the Meshy CLI for what they do not do. Use when the user asks to make, texture, rig, animate, convert, find or download a 3D model or game asset. For physical 3D printing use meshy-3d-printing.\"\nlicense: MIT\ncompatibility: \"Hosted tools: a host connected to Meshy's MCP server, nothing to install. CLI steps: 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).\"\n---\n\n# Meshy 3D Generation\n\nTurn the user's request into a delivered asset. Completion means the requested files in the\nrequested location, or their download links where the host has no file system, and an available\npreview inspected. Login or task submission alone is not completion. Choose the shortest\nsuitable pipeline and reuse existing assets for follow-ups.\n\n## How to run it\n\nMeshy is reached two ways: its hosted tools, and the Meshy CLI. **Use the hosted tools first;\nthe CLI is for what they do not do.** See which this session has before anything else.\n\n| This session has | Run |\n|---|---|\n| Meshy's hosted tools (`image_to_3d`, `text_to_3d_preview`, `get_task`, `download_model`, `get_balance`; a host may list them with a prefix, as in `meshy_3d_image_to_3d`) | Generation, reference pictures, texturing, lookups, downloads and the balance through the tools: [Tools](references/tools.md) |\n| The tools and a terminal | The same, plus the CLI for what the tools do not do: rigging, animation, motion, remeshing and LODs, UV unwrapping, multi-image-to-3d, conversion, resizing, and steps on a local model file. When the `meshy` command is missing, install it; that is the normal first run, not a reason to decline |\n| The tools and no terminal | The tools only. For a step they do not do, say that it is not available in this environment |\n| A terminal and no Meshy tools | Everything through the CLI: the CLI sections below and their references |\n\n**The tools not offering a step never means Meshy cannot do it.** With a terminal, a step the\ntools lack is a CLI step: run `meshy --version`, install the CLI when it is missing, and check\n`auth status`, all as *CLI: first use and authorization* says. Do this before telling the user\nthat 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 that the step is not available in this\nenvironment.\n\nChoose the path when you plan the job, and say in the plan which it is:\n\n- **The tools cover every step** (make, texture, find, show, download): the tools.\n- **The request already names a CLI step** (a character to rig, an LOD chain, several photos of\n  one object): set the CLI up first, then run the whole job on it. Its recipes set options at creation\n  that the tools do not have, such as the pose of a character to rig, and its steps chain by\n  task ID.\n- **A CLI step comes up later**, on a model the tools made: the CLI continues from that model's\n  task ID. Tools, *Continuing on the CLI*, says how, and how to check first that both are signed\n  in to the same account.\n\n## Read what this request needs\n\n| Need | Reference |\n|---|---|\n| The hosted tools: routes, credits and consent, progress, delivery, continuing on the CLI | [Tools](references/tools.md) |\n| CLI runner, credentials, or output location | [Setup](references/setup.md) |\n| CLI generation and the models to pair for a project, texturing, remeshing, conversion, scale, or 2D images | [Pipelines](references/pipelines.md) |\n| Rigging, animation, or generated motion (CLI) | [Animation](references/animation.md) |\n| CLI cost, waiting, preview, delivery, or finding a previous model | [Delivery](references/delivery.md) |\n| Failed or uncertain CLI operation | [Troubleshooting](references/troubleshooting.md) |\n\nRead the relevant section when needed; recipes are examples to adapt to the requested result,\nnot a requirement to execute every stage. An untextured model skips texture generation; an\nexisting GLB needs no extra format conversion. Use command help when parameters are uncertain.\n\n## Before any paid create\n\nThese hold on the tools and on the CLI alike.\n\n- Know what the model is for before the first paid create: a game asset, a character to rig, a\n  render, a 3D print. If the user hasn't said, ask once; the answer picks the route and the\n  models. A game asset or a face-count budget means smart topology, not a standard model\n  remeshed down.\n- Without a usable photo, recommend making a reference image first and building the model\n  from it; text-to-3d is the quicker alternative.\n- Continue work within the user's approved scope and budget. Propose additional paid stages\n  or reruns before spending.\n- Submit a create once and follow that task to its end. A timeout or an unknown submission does\n  not authorize another paid create.\n\n## CLI: first use and 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).\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\nReuse a verified session. If login is needed, run `auth login --device` (with `--region cn` for a\nuser in mainland China) as Setup, section 3 describes: show its URL and user code in\n**commentary/progress, not a final answer**, wait on that same command in this turn, verify\n`auth status`, then continue the original request. Browser approval stays with the user;\ncredentials never belong in chat, and only the CLI touches its config directory.\n\n## CLI: execution boundaries\n\n- Run API, upload, download and mesh operations through the CLI. Local inputs have a 50 MiB\n  limit, and a local model must be GLB or glTF (rigging, UV unwrap and multicolor: GLB); use the supported\n  URL input route for anything else.\n- Use `--format json --no-update-check` on every command: stdout is one `meshy.cli/v1` envelope,\n  auth included. Resolve `WORKSPACE` from the user's output\n  path and pass it to writes.\n- The route and the models for a purpose are in [Pipelines](references/pipelines.md), with\n  *Start from an image* for a request without a photo.\n- Submit once with `create --async`, retain the owning resource and ID, then `wait` on that\n  task. Keep the agent turn active while awaiting a running command. Follow Troubleshooting\n  on timeout or unknown submission.\n- Delivery specifies estimates and balance checks.\n\n## Deliver\n\nDownload only needed assets. Inspect and show a preview when available; a missing preview\nmust not prevent delivery or be described as inspected. On the CLI, Delivery covers\nearlier-stage preview lookup and actual charges. Report the result and any concrete\nlimitation; a rendered image does not establish topology quality or provide a 3D viewer.\n"
}