/meshy-openclaw

name: meshy-openclaw
description: "Generates 3D models, textures, format conversions, reference images, rigging, animation and motion clips with the Meshy CLI, and prepares them for physical 3D printing: white or multicolor prints, printability repair, Creative Lab products, sizing and slicer handoff (Bambu Studio, OrcaSlicer, PrusaSlicer, Cura). Use when the user asks to make, texture, rig, animate or convert a 3D model, or wants something 3D-printed. Signs in through the browser; no API key required."
license: MIT-0
compatibility: "Needs Node.js 22.12+ and the Meshy CLI 0.8.x, 0.8.5 or later (npm install -g meshy-cli@0.8); network access to the Meshy API."
metadata:
  openclaw:
    emoji: "🧊"
    homepage: https://github.com/meshy-dev/meshy-3d-agent
    primaryEnv: MESHY_API_KEY
    requires:
      anyBins:
        - meshy
        - npm
    install:
      - id: node
        kind: node
        package: meshy-cli@0.8
        bins:
          - meshy
        label: Install Meshy CLI (npm)

Meshy 3D — Generation + Printing

Use Meshy CLI **0.8** (0.8.5 or later) to turn the user's request into a delivered asset: the requested files in the requested location, an inspected preview when one exists, and — for prints — the intended size, analysis/repair results and a slicer handoff when asked. Login or task submission alone is not completion. Choose the shortest suitable pipeline and reuse existing assets for follow-ups.

SECURITY MANIFEST

**Executables:** the Meshy CLI — `meshy`, or the pinned temporary package `npm exec --yes --package=meshy-cli@0.8.5 -- meshy` — plus `npm` to install it, `node --version` to check the runtime, and the file manager when the user asks to see a delivered file. No Python, no `curl`, no bundled scripts.

**Credentials:** the CLI's own browser sign-in (OAuth device flow) stores and refreshes a session in `~/.config/meshy/credentials.v2.json` (mode 0600), encrypted under a key the OS keeps. An existing `MESHY_API_KEY`, or an explicit `--api-key-file`, is honoured and takes precedence. The skill never reads, prints or copies a token, device code or key, and never asks for one in chat. `MESHY_API_KEY` is optional.

**Network:** the Meshy API (`api.meshy.ai`) and its sign-in page (`www.meshy.ai`), or `api.meshy.cn` and `meshy.cn` on the China site; the media hosts of assets being downloaded or input URLs being checked, without the credential; the npm registry when the CLI is installed or run as a temporary package.

**Files:** writes only inside one workspace per job — the directory the user named, or `./meshy_output` — and the CLI refuses paths that escape it, including through symlinks. Existing files are not overwritten unless the user asked for it. Reads the input files the user pointed at and its own outputs in the workspace (previews, sidecars). Slicer handoff launches an already-installed slicer application.

**Data leaving this machine:** prompts, input images/models and task requests sent to Meshy.

Read what this request needs

| Need | Reference | |---|---| | CLI runner, sign-in, or output location | [Setup](references/setup.md) | | Digital assets: generation and the models to pair for a project, texturing, remeshing, conversion, images | [Pipelines](references/pipelines.md) | | Rigging, animation, or generated motion | [Animation](references/animation.md) | | Physical prints: local preparation, print generation, analysis/repair, slicers | [Printing recipes](references/printing.md) | | Creative Lab products (figures, lamps, keychains, magnets, keycaps, fidgets) | [Creative Lab](references/creative-lab.md) | | Cost, waiting, preview, delivery, or finding a previous model | [Delivery](references/delivery.md) | | Failed or uncertain operation | [Troubleshooting](references/troubleshooting.md) |

Read the relevant section when needed; recipes are examples to adapt, not stages to run in full. An untextured model skips texturing; an existing GLB needs no conversion. Use command `--help` when parameters are uncertain.

Digital asset or physical print

Anything meant to be printed — a print, slicer, 3MF, STL, Bambu/Orca/Prusa/Cura, multicolor, a desk toy or a physical figure — follows [Printing recipes](references/printing.md) **from the first command**, so generation parameters fit the print. Everything else follows [Pipelines](references/pipelines.md).

| Print request | Route | |---|---| | Scale, orient or ground an existing OBJ | Local `mesh prepare-print`; no sign-in or balance | | Open an existing STL or 3MF | Local `slicer detect` and `slicer open`; no sign-in or balance | | White model from text or photo | 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 alone does not imply Creative Lab. Ask about size, color or style only when the missing choice materially changes the result.

First use and sign-in on OpenClaw

Before the first command run `meshy --version`; no need to ask. When `meshy` is missing or older tha