meshy-3d-generation
Generate 3D models, textures, images, rig characters, and animate them using the Meshy AI API. Handles API key detection, setup, and all generation workflows via direct HTTP calls. Use when the user asks to create 3D models, convert text/images to 3D, texture models, rig or animate characters, or interact with the Meshy API. For 3D printing requests, use the meshy-3d-printing skill instead.
meshy-dev · 已有 AI 审核记录
安装与使用
运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。
npx skills add meshy-dev/meshy-3d-agent --skill meshy-3d-generation技能说明
name: meshy-3d-generation description: Generate 3D models, textures, images, rig characters, and animate them using the Meshy AI API. Handles API key detection, setup, and all generation workflows via direct HTTP calls. Use when the user asks to create 3D models, convert text/images to 3D, texture models, rig or animate characters, or interact with the Meshy API. For 3D printing requests, use the meshy-3d-printing skill instead. license: MIT compatibility: Requires Python 3 with requests package. Works with Claude Code, Cursor, and all Agent Skills compatible tools. metadata: author: meshy-dev version: "0.4.1" homepage: https://github.com/meshy-dev/meshy-3d-agent allowed-tools: Bash, Read, Write, Glob, Grep
Meshy 3D Generation
Directly communicate with the Meshy AI API to generate 3D assets. This skill handles the complete lifecycle: environment setup, API key detection, task creation, polling, downloading, and chaining multi-step pipelines.
All paths below are relative to this skill's own directory (the directory containing this SKILL.md). Resolve them before running.
| Resource | When to use |
|---|---|
scripts/meshy_task.py | Bundled CLI for every API call and file operation (Step 2) |
| reference.md | Full API reference: every parameter, response schema, error code |
| references/setup.md | API key setup — read when Step 0 finds no key |
| references/pipelines.md | Per-endpoint recipes: exact payloads + script calls for each workflow |
| references/troubleshooting.md | Error recovery trees and task failure messages |
Security & Data Handling
- API key (
MESHY_API_KEY) — sent only in the HTTPAuthorization: Bearerheader tohttps://api.meshy.ai. Never logged in full (only akey[:8]...prefix is ever printed). The bundled script never persists it; it is written to.envin the current working directory only when the user explicitly asks, and never to shell profiles, Windows user variables, or any path outside the working directory (see references/setup.md). - Key sources read — the current session environment, then
.env/.env.localin the current working directory. Home directories and shell profiles are never scanned. - Network — the only external endpoint is
https://api.meshy.ai. System proxies are bypassed (trust_env = False) so the key is never handed to an environment-configured proxy. - Filesystem writes —
.envin the working directory (on explicit request only) and./meshy_output/for downloaded models, thumbnails, and metadata. Input files (e.g. local images for image-to-3D) are read only at the exact path the user provides. - Data leaving the machine — the API key, user-provided text prompts, and image URLs/data go to
api.meshy.aionly. No other local data is transmitted; downloaded assets are saved locally.
IMPORTANT: 3D Printing → Use meshy-3d-printing Skill
If the user's request involves 3D printing (keywords: print, 3d print, slicer, slice, bambu, orca, prusa, cura, multicolor, 3mf, figurine, miniature, statue, physical model), use the meshy-3d-printing skill instead of this one for the entire workflow. The printing skill handles generation with correct print-optimized parameters (e.g. target_formats with "3mf" for multicolor), slicer detection, coordinate conversion, and slicer launch — all in one pipeline.
This skill's scripts/meshy_task.py is reused by the printing skill, but the workflow orchestration (what to generate, which formats, what to do after) must come from the printing skill when printing is involved.
Do NOT generate a model with this skill and then hand off to the printing skill — the printing skill needs to control parameters from the start (e.g. target_formats, should_texture).
IMPORTANT: First-Use Session Notice
When this skill is first activated in a session, inform the user:
All generated files will be saved to
meshy_output/in the current working directory. Each project gets its own folder ({YYYYMMDD_HHmmss}_{prompt}_{id}/) with model files, textures, thumbnails, and metadata. History is tracked inmeshy_output/history.json.
This only needs to be said once per session, at the beginning.
IMPORTANT: File Organization
All downloaded files MUST go into a structured meshy_output/ directory in the current working directory. Do NOT scatter files randomly.
- Each project gets its own folder:
meshy_output/{YYYYMMDD_HHmmss}_{prompt_slug}_{task_id_prefix}/ - For chained tasks (preview → refine → rig), reuse the same
project_dir - Track tasks in
metadata.jsonper project, and globalhistory.json - Auto-download thumbnails alongside models
The bundled CLI implements this: project-dir, record, and thumbnail subcommands.
IMPORTANT: Shell Command Rules
Use only standard POSIX tools in shell commands. Do NOT use rg (ripgrep), fd, or other non-standard CLI tools — they may not be installed. Use these standard alternatives instead:
| Do NOT use | Use instead |
|---|---|
rg | grep |
fd | find |
bat | cat |
exa / eza | ls |
IMPORTANT: Run Long Tasks Properly
Meshy generation tasks take 1–5 minutes. When polling for completion:
- The bundled CLI prints unbuffered progress in real time — run each
pollas a single Bash call and let it finish. - Be patient with long-running polls — do NOT interrupt or kill them prematurely. Tasks at 99% for 30–120s is normal finalization, not a failure.
- Pass a larger
--timeout(e.g.--timeout 600) for heavy tasks instead of retrying a timed-out poll.
IMPORTANT: Never Rebuild Bundled Scripts
scripts/meshy_task.py is the single source of truth for create_task / poll_task / download / get_project_dir / record_task / save_thumbnail. **Never retype, paraphrase, or "rec