Verwendung
- Installationsbefehl kopieren und das Quellpaket vor der Installation in der eigenen Agentenumgebung prüfen.
- Benötigte Werkzeuge, Zugangsdaten und Hosts im Original prüfen.
- Eingabe und gewünschtes Ergebnis beschreiben und die Ausgabe mit den Quellen abgleichen.
npx skills add https://github.com/meshy-dev/meshy-3d-agent --skill meshy-3d-generationVor dem Start
- Die Installation umfasst weder Modellabo noch API-Kontingent oder Dateizugriffsrechte.
- Sterne und Installationen zeigen Aktivität, keine unabhängige Qualitäts- oder Sicherheitsprüfung.
Aus dem Quell-Repository gerendert; Überschriften, Beispiele, Code, Tabellen, Links und Bilder bleiben erhalten.
Meshy 3D Generation
Use Meshy CLI 0.8 (0.8.6 or later) to turn the user's request into a delivered asset. Completion means saving the requested files in the requested location and inspecting an available preview. Login or task submission alone is not completion. Choose the shortest suitable pipeline and reuse existing assets for follow-ups.
Read what this request needs
| Need | Reference |
|---|---|
| CLI runner, credentials, or output location | Setup |
| Generation and the models to pair for a project, texturing, remeshing, conversion, scale, or 2D images | Pipelines |
| Rigging, animation, or generated motion | Animation |
| 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 the relevant section when needed; recipes are examples to adapt to the requested result, not a requirement to execute every stage. An untextured model skips texture generation; an existing GLB needs no extra format conversion. Use command help when parameters are uncertain.
First use and 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).
Reuse 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, not a final answer, wait on that same command in this turn, verify auth status, then continue the original request. Browser approval stays with the user; credentials never belong in chat, and only the CLI touches its config directory.
Execution boundaries
- Run API, upload, download and mesh operations through the CLI. Local inputs have a 50 MiB
limit, and a local model must be GLB or glTF (rigging, UV unwrap and multicolor: GLB); use the supported URL input route for anything else.
- Use
--format json --no-update-checkon every command: stdout is onemeshy.cli/v1envelope,
auth included. Resolve WORKSPACE from the user's output path and pass it to writes.
- Know what the model is for before the first paid create: a game asset, a character to rig, a
render, a 3D print. If the user hasn't said, ask once; the answer picks the route and the models (Pipelines). A game asset or a face-count budget means smart topology, not a standard model remeshed down.
- Submit once with
create --async, retain the owning resource and ID, thenwaiton that
task. Keep the agent turn active while awaiting a running command. Follow Troubleshooting on timeout or unknown submission; these do not authorize another paid create.
- Without a usable photo, recommend making a reference image first and building the model
from it; text-to-3d is the quicker alternative (Pipelines, Start from an image).
- Continue work within the user's approved scope and budget. Propose additional paid stages
or reruns before spending; Delivery specifies estimates and balance checks.
Deliver
Download only needed assets. Inspect and show a preview when available; a missing preview must not prevent delivery or be described as inspected. Delivery covers earlier-stage preview lookup and actual charges. Report the result and any concrete limitation; a rendered image does not establish topology quality or provide a 3D viewer. Where your chat shows images or web pages, Visual hosts covers showing the preview and the model there.