Meshy 3D Agent

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

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 walks the agent through the CLI, the skills for its host and one browser sign-in.

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.7. 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.7.3 -- 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.

npm install -g meshy-cli@0.7
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 has the version, path and error handling in full.

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/ (Cursor plugin manifest retained).
• 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.

OpenClaw installs one skill per listing, so meshy-openclaw carries both workflows and the same references as the other two (kept byte-identical by scripts/build.py). It is published on ClawHub as Meshy 3D Agent: openclaw skills install @arlieeee/meshy-3d-agent. It is eligible whenever meshy or npm is on PATH and offers the npm install of the CLI; MESHY_API_KEY is optional, not a gate.

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.

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.

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.json with mode 0600. 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 ./meshy_output when you named none. Every writing command carries that boundary explicitly, so a path outside it — including through a symlink — is refused rather than written. Downloads are selected, not fetched in every format; existing files are not overwritten, and download replaces one only with --overwrite. OBJ preparation writes a new file. Slicer integration launches a detected installed application; a launch request is not proof the model was imported.

Only maintainers need Python 3.11+ and PyYAML. None of these tools ships in the CLI skill folders.

python3 scripts/build.py
python3 scripts/build.py --check
python3 scripts/validate_skills.py
MESHY_CLI_BIN=/absolute/path/to/meshy node --test tests/*.test.mjs

build.py copies the shared setup, delivery and troubleshooting references from generation to printing so each skill directory installs on its own; --check fails when a copy is stale. validate_skills.py checks frontmatter, link closure, the absence of bundled runtime files, the JSON envelope and resolved workspace placeholder on every documented CLI command, and the plugin manifests, for all three skills.

Tests use a loopback API, synthetic credentials and temporary config/workspace directories. tests/runner-contract.test.mjs additionally runs the documented npm exec entry point, so it populates an isolated npm cache from the registry on its first run and needs no MESHY_CLI_BIN. CI installs the pinned CLI into a temporary prefix; tests never contact production or spend credits. Without MESHY_CLI_BIN, the CLI contract tests skip explicitly — a skip is not a pass, so set it.

Old task IDs remain usable: get or wait on the original resource by its ID; never recreate a task just to migrate. CLI 0.7.0 removed the project store (meshy project, --project and --stage are gone), so a metadata.json or history.json left by an older version is not read: take the task IDs from it by hand. Returning to an old Python skill requires its old runtime and API-key setup; it cannot use the CLI OAuth store. Keep the CLI for inspecting in-flight tasks rather than submitting again.

MIT