# meshy-3d-generation

Adopt this skill: https://proskills.md/skills/other/meshy-dev-meshy-3d-agent-skills-meshy-3d-generation

Page: https://proskills.md/skills/other/meshy-dev-meshy-3d-agent-skills-meshy-3d-generation
This document is the public skill bundle for that page. It contains SKILL.md and every helper file the catalog carries. No login is required.

## File: skills/meshy-3d-generation/SKILL.md
size: 3132
upstream: https://github.com/meshy-dev/meshy-3d-agent/blob/main/skills/meshy-3d-generation/SKILL.md

```text
---
name: meshy-3d-generation
description: "Create or edit digital 3D assets with Meshy: models, textures, rigging, animation, and reference images. For physical printing, use meshy-3d-printing."
license: MIT
---

# Meshy 3D Generation

Use Meshy CLI **0.4.0** to turn the user's request into a delivered asset. Completion means
saving the requested files in the requested location, inspecting an available preview, and
finishing any project integration the user requested. 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](references/setup.md) |
| Generation, texturing, rigging, animation, or conversion | [Pipelines](references/pipelines.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 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

Resolve the runner automatically: use compatible `meshy`, otherwise
`npm exec --yes --package=meshy-cli@0.4.0 -- meshy …`. Reuse a verified session. If login is
needed, follow Setup and run `auth login --device` in a persistent tool session. Show its
verification URL and user code in **commentary/progress, not a final answer**. Await that same
session in this turn until it exits, verify `auth status`, then continue the original request.
A background process cannot resume a finished turn; do not require a "done" chat message.
Browser approval stays with the user; credentials never belong in chat.

## Execution boundaries

- Run API, upload, download and mesh operations through the CLI. Local inputs have a 50 MiB
  limit; use the supported URL input route where appropriate.
- Use `--output-schema v1 --format json --no-update-check` for business commands; auth has
  its own JSON shape. Resolve `WORKSPACE` from the user's output path and pass it to writes.
- Submit once with `create --async`, retain the owning resource and ID, then `wait` on 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.
- 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, actual charges, and existing-project integration. Report the result and any concrete
limitation; a rendered image does not establish topology quality or provide a 3D viewer.
```

## File: README.md
upstream: https://github.com/meshy-dev/meshy-3d-agent/blob/main/README.md

````text
# Meshy 3D Agent

Meshy skills for creating digital assets and preparing 3D prints. All three skills drive
**Meshy CLI 0.8** (0.8.5 or later, `meshy`) on **Node.js 22.12+**. They are instructions and references only —
no bundled runtime scripts. Current release: **0.9.6**.

**Requires a paid Meshy plan (Pro or above),** and generation spends Meshy credits. Sign in with
your Meshy account; no API key needed. A Free account can sign in, but creating tasks is refused
(HTTP 402 `plan_upgrade_required`, CLI exit 9). Plans and prices: <https://www.meshy.ai/pricing>.

## Let your agent install it

Paste this into Claude Code, Codex, Cursor, OpenClaw, Hermes Agent, Meta Muse or another agent:

> Help me install Meshy CLI and the meshy-3d-agent skills:
> https://raw.githubusercontent.com/meshy-dev/meshy-3d-agent/main/INSTALL.md

[INSTALL.md](INSTALL.md) walks the agent through the CLI, the skills for its host and one
browser sign-in.

## Start by asking for what you want

Once installed, say the thing, in your own words:

> Turn this photo into a textured GLB and save it to `./assets/chest.glb`. Set it up if it
> isn't yet.

The agent resolves the CLI, checks whether a session already exists and, if not, starts one
browser login and shows you a link and a code. You approve in the browser; nothing is pasted
into the chat, no API key is copied, and the agent then continues the request you actually
made. The file lands at the path you named — `./meshy_output` is only the fallback when you
name none — with a rendered preview alongside it and the task IDs for whatever you ask next
("make a 1500-face LOD", "now as FBX", "scale it to 150 mm").

Two more things worth knowing:

- **The agent installs the CLI.** With Node 22.12+ and no `meshy` (or an older one), it runs
  `npm install -g meshy-cli@0.8`. Where a global install is not allowed, or a newer CLI is
  already installed, it runs the pinned package temporarily instead
  (`npm exec --yes --package=meshy-cli@0.8.5 -- meshy …`).
- **Local print work needs no account.** Rescaling an OBJ or opening a 3MF in a slicer runs
  entirely on your machine — no login, no balance check, no credits.

### Doing it by hand instead

```bash
npm install -g meshy-cli@0.8
meshy --version
meshy auth login
meshy auth status --format json --no-update-check
```

Run `meshy auth login` from a desktop terminal and approve in your browser; in SSH, CI or
container sessions use `meshy auth login --device` and open the verification URL it prints.
Keep the login process alive until you have approved. The CLI stores and refreshes the session;
both skills reuse it under the same OS user and CLI configuration, in any directory. On the China
site add `--region cn` to the login; the CLI remembers the region for later commands.

An existing `MESHY_API_KEY` overrides the stored browser session — keep it if that is
intentional; `auth status` reports the effective source. Explicit key files need
`--api-key-file`; the CLI never searches `.env`. Never paste a key into a chat. The
self-contained [setup reference](skills/meshy-3d-generation/references/setup.md) has the
version, path and error handling in full.

## Skills

| Skill | Workflow |
|---|---|
| [meshy-3d-generation](skills/meshy-3d-generation/SKILL.md) | Text/image/2D/motion, textures, remesh, conversion, sizing, UV, rigging and animation |
| [meshy-3d-printing](skills/meshy-3d-printing/SKILL.md) | White models, multi-color 3MF, analysis/repair, Creative Lab products and slicers |

Printing installs independently and controls its generation parameters from the start.
Requested formats and already-approved budgets are preserved. Cost estimates come from
`meshy make --dry-run` or the published price list, never from your balance; the real charge is
the task's own `consumed_credits`. No live spending happens during install.

Install these directories with your host's skills installer, or copy each **whole directory**:

- Claude Code: `.claude/skills/` (the repository also retains its Claude plugin manifest).
- Cursor: `.cursor/skills/`, or the whole repository as a plugin (see [Cursor plugin](#cursor-plugin)).
- Codex: `.agents/skills/`.

Replace a prior managed skill directory rather than merging files, so old `scripts/` files are
removed. Back up personal edits before replacement. Do not remove model projects or CLI state.
Host discovery and browser interaction require a real host smoke test; local contract tests
alone do not certify a host or operating system.

### Cursor plugin

The repository is also a Cursor plugin. [`.cursor-plugin/plugin.json`](.cursor-plugin/plugin.json)
loads `meshy-3d-generation` and `meshy-3d-printing`. To load it from a clone instead of the
marketplace:

```bash
git clone https://github.com/meshy-dev/meshy-3d-agent.git ~/.cursor/plugins/local/meshy-3d-agent
```

Restart Cursor or run **Developer: Reload Window**, then check under **Customize** that both
skills are listed. Clone into that folder rather than symlinking to it: Cursor skips a symlink
that points outside `~/.cursor/plugins/local`. On Enterprise plans an admin has to allow local
plugin imports first.

You need Node.js 22.12+ and the paid Meshy plan described at the top of this page. The skills
quote an estimate in credits and stay within the budget you approve before starting a paid task.

Cursor's agent runs terminal commands in a sandbox that blocks most network access, so the first
sign-in or task asks to run outside it. To let the Meshy CLI through, add Meshy's domains to
`.cursor/sandbox.json` in your project (or `~/.cursor/sandbox.json` for every project):

```json
{
  "networkPolicy": {
    "allow": ["api.meshy.ai", "www.meshy.ai", "assets.meshy.ai"]
  }
}
```

On the China site, use `api.meshy.cn`, `meshy.cn` and `assets.meshy.cn` instead. A team admin can set the same
allowlist for everyone in Cursor's dashboard. See
[Cursor's sandbox reference](https://cursor.com/docs/reference/sandbox).

### OpenClaw and Hermes Agent

OpenClaw installs one skill per listing, so it gets both workflows in a single skill that lives in
[meshy-openclaw](https://github.com/meshy-dev/meshy-openclaw) and carries this repository's
references. It is published on ClawHub as
[Meshy 3D Agent](https://clawhub.ai/arlieeee/skills/meshy-3d-agent):
`openclaw skills install @arlieeee/meshy-3d-agent`.

Hermes Agent reads the same skills from skills.sh, ClawHub or GitHub:
`hermes skills install meshy-dev/meshy-3d-agent/skills/meshy-3d-generation`, or
`npx skills add … -a hermes-agent` as in [INSTALL.md](INSTALL.md).

Until the 0.6.0 skills release the OpenClaw skill was a separate Python client that called the
REST API with an API key. It is gone; its task IDs remain usable from the CLI.

## Data and local effects

The CLI sends prompts, media and task requests to the resolved Meshy API origins (normally
`api.meshy.ai`, or `api.meshy.cn` on the China site); OAuth opens Meshy's browser page. Asset downloads and input URL preflights
contact their media hosts without the API credential. npm is contacted when the CLI is installed
or run as a temporary package; workflow commands disable the update notifier. An unexpected
custom API or login origin must be resolved before credentials are sent.

CLI profiles normally live in `~/.config/meshy/credentials.v2.json` with mode 0600, their keys
and tokens encrypted under a key the OS keeps (Keychain, DPAPI or the Secret Service).
`MESHY_CONFIG_DIR` moves the config root, including operation and device-flow state;
`MESHY_CREDENTIALS_PATH` overrides only the credential file. The skills never read or copy tokens,
and never print a token, device code or signed URL.
`auth use` changes the shared active profile, so concurrent tasks should not switch accounts
independently. Profile sharing is local, not automatic across machines or containers.

Models, previews and the small `_meta.json` sidecar that records each delivered task are written
inside one workspace per job: the directory you named, or `./mes
````
