Skip to content
Back to search

meshy-3d-agent

Meshy AI 3D generation and 3D printing skills. Install the whole suite via the meshy-3d-agent plugin, or each skill individually. Version is pinned by .claude-plugin/plugin.json; entries intentionally carry no version field.

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked today

Check it deeper on your machine

It has changed since its scan on 12 Nov 2026.

As a Claude Code plugin, install it and then ask Claude Code:

/plugin marketplace add keithmackay/mackayi/plugin install scanskillsafety@mackayiDo a deep scan of https://github.com/meshy-dev/meshy-3d-agent with scanskillsafety

Or from a terminal, clone it and run it:

git clone https://github.com/keithmackay/scanskillsafety-skill ~/.claude/skills/scanskillsafetynode ~/.claude/skills/scanskillsafety/cli.cjs --deep 'https://github.com/meshy-dev/meshy-3d-agent'

It checks the exact commit: every file, its packages against OSV (api.osv.dev), how it compares with this page's scan (findsafeskills.com receives the repository's address), and, if you agree, Claude reading every file with your own Claude subscription. It never runs the code.

Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/meshy-dev--meshy-3d-agent/badge.svg)](/listings/meshy-dev--meshy-3d-agent)

HTML

<a href="/listings/meshy-dev--meshy-3d-agent"><img src="/api/listings/meshy-dev--meshy-3d-agent/badge.svg" alt="findsafeskills safety rating" /></a>

Install

i

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

.claude-plugin/marketplace.json · Manifest · 30 lines
  1. {
  2. "name": "meshy-3d-agent",
  3. "owner": {
  4. "name": "Meshy",
  5. "url": "https://github.com/meshy-dev"
  6. },
  7. "description": "Meshy AI 3D generation and 3D printing skills. Install the whole suite via the meshy-3d-agent plugin, or each skill individually. Version is pinned by .claude-plugin/plugin.json; entries intentionally carry no version field.",
  8. "plugins": [
  9. {
  10. "name": "meshy-3d-generation",
  11. "source": "./",
  12. "skills": ["./skills/meshy-3d-generation"],
  13. "description": "Generate 3D models, textures, and images; rig and animate characters via the Meshy AI API.",
  14. "author": {
  15. "name": "Meshy",
  16. "url": "https://github.com/meshy-dev"
  17. }
  18. },
  19. {
  20. "name": "meshy-3d-printing",
  21. "source": "./",
  22. "skills": ["./skills/meshy-3d-printing"],
  23. "description": "3D-print Meshy-generated models: slicer detection, white and multicolor printing, Creative Lab products.",
  24. "author": {
  25. "name": "Meshy",
  26. "url": "https://github.com/meshy-dev"
  27. }
  28. }
  29. ]
  30. }
README.md · README · 212 lines
  1. # Meshy 3D Agent
  2. Meshy skills for creating digital assets and preparing 3D prints. All three skills drive
  3. **Meshy CLI 0.8** (0.8.5 or later, `meshy`) on **Node.js 22.12+**. They are instructions and references only —
  4. no bundled runtime scripts. Current release: **0.9.6**.
  5. **Requires a paid Meshy plan (Pro or above),** and generation spends Meshy credits. Sign in with
  6. your Meshy account; no API key needed. A Free account can sign in, but creating tasks is refused
  7. (HTTP 402 `plan_upgrade_required`, CLI exit 9). Plans and prices: <https://www.meshy.ai/pricing>.
  8. ## Let your agent install it
  9. Paste this into Claude Code, Codex, Cursor, OpenClaw, Hermes Agent, Meta Muse or another agent:
  10. > Help me install Meshy CLI and the meshy-3d-agent skills:
  11. > https://raw.githubusercontent.com/meshy-dev/meshy-3d-agent/main/INSTALL.md
  12. [INSTALL.md](INSTALL.md) walks the agent through the CLI, the skills for its host and one
  13. browser sign-in.
  14. ## Start by asking for what you want
  15. Once installed, say the thing, in your own words:
  16. > Turn this photo into a textured GLB and save it to `./assets/chest.glb`. Set it up if it
  17. > isn't yet.
  18. The agent resolves the CLI, checks whether a session already exists and, if not, starts one
  19. browser login and shows you a link and a code. You approve in the browser; nothing is pasted
  20. into the chat, no API key is copied, and the agent then continues the request you actually
  21. made. The file lands at the path you named — `./meshy_output` is only the fallback when you
  22. name none — with a rendered preview alongside it and the task IDs for whatever you ask next
  23. ("make a 1500-face LOD", "now as FBX", "scale it to 150 mm").
  24. Two more things worth knowing:
  25. - **The agent installs the CLI.** With Node 22.12+ and no `meshy` (or an older one), it runs
  26. `npm install -g meshy-cli@0.8`. Where a global install is not allowed, or a newer CLI is
  27. already installed, it runs the pinned package temporarily instead
  28. (`npm exec --yes --package=meshy-cli@0.8.5 -- meshy …`).
  29. - **Local print work needs no account.** Rescaling an OBJ or opening a 3MF in a slicer runs
  30. entirely on your machine — no login, no balance check, no credits.
  31. ### Doing it by hand instead
  32. ```bash
  33. npm install -g meshy-cli@0.8
  34. meshy --version
  35. meshy auth login
  36. meshy auth status --format json --no-update-check
  37. ```
  38. Run `meshy auth login` from a desktop terminal and approve in your browser; in SSH, CI or
  39. container sessions use `meshy auth login --device` and open the verification URL it prints.
  40. Keep the login process alive until you have approved. The CLI stores and refreshes the session;
  41. both skills reuse it under the same OS user and CLI configuration, in any directory. On the China
  42. site add `--region cn` to the login; the CLI remembers the region for later commands.
  43. An existing `MESHY_API_KEY` overrides the stored browser session — keep it if that is
  44. intentional; `auth status` reports the effective source. Explicit key files need
  45. `--api-key-file`; the CLI never searches `.env`. Never paste a key into a chat. The
  46. self-contained [setup reference](skills/meshy-3d-generation/references/setup.md) has the
  47. version, path and error handling in full.
  48. ## Skills
  49. | Skill | Workflow |
  50. |---|---|
  51. | [meshy-3d-generation](skills/meshy-3d-generation/SKILL.md) | Text/image/2D/motion, textures, remesh, conversion, sizing, UV, rigging and animation |
  52. | [meshy-3d-printing](skills/meshy-3d-printing/SKILL.md) | White models, multi-color 3MF, analysis/repair, Creative Lab products and slicers |
  53. Printing installs independently and controls its generation parameters from the start.
  54. Requested formats and already-approved budgets are preserved. Cost estimates come from
  55. `meshy make --dry-run` or the published price list, never from your balance; the real charge is
  56. the task's own `consumed_credits`. No live spending happens during install.
  57. Install these directories with your host's skills installer, or copy each **whole directory**:
  58. - Claude Code: `.claude/skills/` (the repository also retains its Claude plugin manifest).
  59. - Cursor: `.cursor/skills/`, or the whole repository as a plugin (see [Cursor plugin](#cursor-plugin)).
  60. - Codex: `.agents/skills/`.
  61. Replace a prior managed skill directory rather than merging files, so old `scripts/` files are
  62. removed. Back up personal edits before replacement. Do not remove model projects or CLI state.
  63. Host discovery and browser interaction require a real host smoke test; local contract tests
  64. alone do not certify a host or operating system.
  65. ### Cursor plugin
  66. The repository is also a Cursor plugin. [`.cursor-plugin/plugin.json`](.cursor-plugin/plugin.json)
  67. loads `meshy-3d-generation` and `meshy-3d-printing`. To load it from a clone instead of the
  68. marketplace:
  69. ```bash
  70. git clone https://github.com/meshy-dev/meshy-3d-agent.git ~/.cursor/plugins/local/meshy-3d-agent
  71. ```
  72. Restart Cursor or run **Developer: Reload Window**, then check under **Customize** that both
  73. skills are listed. Clone into that folder rather than symlinking to it: Cursor skips a symlink
  74. that points outside `~/.cursor/plugins/local`. On Enterprise plans an admin has to allow local
  75. plugin imports first.
  76. You need Node.js 22.12+ and the paid Meshy plan described at the top of this page. The skills
  77. quote an estimate in credits and stay within the budget you approve before starting a paid task.
  78. Cursor's agent runs terminal commands in a sandbox that blocks most network access, so the first
  79. sign-in or task asks to run outside it. To let the Meshy CLI through, add Meshy's domains to
  80. `.cursor/sandbox.json` in your project (or `~/.cursor/sandbox.json` for every project):
  81. ```json
  82. {
  83. "networkPolicy": {
  84. "allow": ["api.meshy.ai", "www.meshy.ai", "assets.meshy.ai"]
  85. }
  86. }
  87. ```
  88. On the China site, use `api.meshy.cn`, `meshy.cn` and `assets.meshy.cn` instead. A team admin can set the same
  89. allowlist for everyone in Cursor's dashboard. See
  90. [Cursor's sandbox reference](https://cursor.com/docs/reference/sandbox).
  91. ### OpenClaw and Hermes Agent
  92. OpenClaw installs one skill per listing, so it gets both workflows in a single skill that lives in
  93. [meshy-openclaw](https://github.com/meshy-dev/meshy-openclaw) and carries this repository's
  94. references. It is published on ClawHub as
  95. [Meshy 3D Agent](https://clawhub.ai/arlieeee/skills/meshy-3d-agent):
  96. `openclaw skills install @arlieeee/meshy-3d-agent`.
  97. Hermes Agent reads the same skills from skills.sh, ClawHub or GitHub:
  98. `hermes skills install meshy-dev/meshy-3d-agent/skills/meshy-3d-generation`, or
  99. `npx skills add … -a hermes-agent` as in [INSTALL.md](INSTALL.md).
  100. Until the 0.6.0 skills release the OpenClaw skill was a separate Python client that called the
  101. REST API with an API key. It is gone; its task IDs remain usable from the CLI.
  102. ## Data and local effects
  103. The CLI sends prompts, media and task requests to the resolved Meshy API origins (normally
  104. `api.meshy.ai`, or `api.meshy.cn` on the China site); OAuth opens Meshy's browser page. Asset downloads and input URL preflights
  105. contact their media hosts without the API credential. npm is contacted when the CLI is installed
  106. or run as a temporary package; workflow commands disable the update notifier. An unexpected
  107. custom API or login origin must be resolved before credentials are sent.
  108. CLI profiles normally live in `~/.config/meshy/credentials.v2.json` with mode 0600, their keys
  109. and tokens encrypted under a key the OS keeps (Keychain, DPAPI or the Secret Service).
  110. `MESHY_CONFIG_DIR` moves the config root, including operation and device-flow state;
  111. `MESHY_CREDENTIALS_PATH` overrides only the credential file. The skills never read or copy tokens,
  112. and never print a token, device code or signed URL.
  113. `auth use` changes the shared active profile, so concurrent tasks should not switch accounts
  114. independently. Profile sharing is local, not automatic across machines or containers.
  115. Models, previews and the small `_meta.json` sidecar that records each delivered task are written
  116. inside one workspace per job: the directory you named, or `./meshy_output` when you named none.
  117. Every writing command carries that boundary explicitly, so a path outside it — including through
  118. a symlink — is refused rather than written. Downloads are selected, not fetched in every format;
  119. existing files are not overwritten, and `download` replaces one only with `--overwrite`. OBJ preparation writes a new file. Slicer integration launches a detected
  120. installed application; a launch request is not proof the model was imported.
  121. ## Development and validation
  122. Only maintainers need Python 3.11+, PyYAML and jsonschema. None of these tools ships in the CLI
  123. skill folders.
  124. ```bash
  125. python3 scripts/build.py
  126. python3 scripts/build.py --check
  127. python3 scripts/validate_skills.py
  128. MESHY_CLI_BIN=/absolute/path/to/meshy node --test tests/*.test.mjs
  129. ```
  130. `build.py` copies the shared setup, delivery and troubleshooting references from generation to
  131. printing so each skill directory installs on its own; `--check` fails when a copy is stale.
  132. `validate_skills.py` checks frontmatter, link closure, the absence of bundled runtime files, the
  133. JSON envelope and resolved workspace placeholder on every documented CLI command, and the plugin
  134. manifests, for all three skills. It also checks the Cursor manifests against Cursor's plugin and
  135. marketplace schemas, downloaded from a pinned commit of cursor/plugins and checked by hash (set
  136. `CURSOR_SCHEMA_CACHE` to keep them in a folder of your choice), and requires the plugin manifest
  137. to list exactly the generation and printing skills.
  138. Tests use a loopback API, synthetic credentials and temporary config/workspace directories.
  139. `tests/runner-contract.test.mjs` additionally runs the documented `npm exec` entry point, so it
  140. populates an isolated npm cache from the registry on its first run and needs no `MESHY_CLI_BIN`.
  141. CI installs the pinned CLI into a temporary prefix; tests never contact production or spend
  142. credits. Without `MESHY_CLI_BIN`, the CLI contract tests skip explicitly — a skip is not a pass,
  143. so set it.
  144. ## Upgrade and rollback
  145. Old task IDs remain usable: `get` or `wait` on the original resource by its ID; never recreate a
  146. task just to migrate. CLI 0.7.0 removed the project store (`meshy project`, `--project` and `--stage`
  147. are gone), so a `metadata.json` or `history.json` left by an older version is not read: take the
  148. task IDs from it by hand. Returning to an old Python skill requires its old runtime and API-key
  149. setup; it cannot use the CLI OAuth store. Keep the CLI for inspecting in-flight tasks rather than
  150. submitting again.
  151. ## Terms, privacy and support
  152. Using Meshy through these skills is covered by Meshy's
  153. [Terms of Use](https://www.meshy.ai/terms-of-use) and
  154. [Privacy Policy](https://www.meshy.ai/privacy-policy).
  155. [Data and local effects](#data-and-local-effects) lists what the CLI sends and writes. For account
  156. or billing help, email support@meshy.ai. Report problems with the skills in
  157. [GitHub issues](https://github.com/meshy-dev/meshy-3d-agent/issues).
  158. ## License
  159. [MIT](LICENSE)
  160. This repository contains only skills and references; it does not include the Meshy CLI or any of
  161. its dependencies. Setup installs the [Meshy CLI](https://www.npmjs.com/package/meshy-cli) from npm
  162. as a separate tool, under its own MIT license.

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.