Ai Animation 3d Model

animate 3D model files into animated 3D video with this skill. Works with OBJ, FBX, GLB, GLTF files up to 500MB. 3D artists and game developers use it for an...

Security Scan

The skill's requirements and runtime instructions are coherent with its stated purpose (uploading 3D models to a cloud renderer) and it only asks for a service token; no unrelated credentials or invasive installs are requested.

Purpose & Capability

The skill's name and description match the actions in SKILL.md: uploading 3D model files, creating sessions, streaming SSE edits, and exporting rendered video. Requesting a NEMO_TOKEN (service token) is appropriate for a cloud rendering backend. One minor inconsistency: the registry metadata provided earlier said 'Required config paths: none', but the SKILL.md frontmatter lists a config path (~/.config/nemovideo/) — likely for caching session/token data; this is plausible but should be verified.

Instruction Scope

Instructions are specific to the cloud service endpoints (session creation, SSE, upload, render) and focus on model upload and rendering flows. They instruct checking NEMO_TOKEN, obtaining an anonymous token if absent, and uploading files either via multipart file path or by URL. The only scope-related concern is that the skill derives an X-Skill-Platform header from install paths (e.g., ~/.clawhub/, ~/.cursor/skills/) which requires inspecting environment/install paths; this is minor but broader than strictly necessary for rendering. The instructions do not ask for unrelated system files or other credentials.

Install Mechanism

Instruction-only skill with no install spec and no code files. No packages or downloads are requested, so there is no install risk.

Credentials

Only one environment credential is declared (NEMO_TOKEN) and the SKILL.md explains an anonymous-token fallback flow so a user-supplied secret is not strictly required. No unrelated keys, passwords, or cloud credentials are requested.

Persistence & Privilege

The skill is not always-enabled and does not request elevated platform privileges. It keeps a session_id for operations (expected). The only persistence-related note is the mention of a config path (~/.config/nemovideo/) in the frontmatter which implies local caching of tokens or session state; this is reasonable for user convenience but the registry metadata conflict should be clarified.

Assessment

This skill appears to do what it says: upload 3D models to a remote renderer and return video. Before installing or using it: 1) Verify the external domain (mega-api-prod.nemovideo.ai) is one you trust and review its privacy/retention policy — you will upload model files (up to 500MB). 2) Prefer providing your own NEMO_TOKEN if you have an account rather than relying on anonymous tokens when handling sensitive or proprietary models. 3) Note the frontmatter references a local config path (~/.config/nemovideo/) and detecting install paths (~/.clawhub/, ~/.cursor/skills/) — confirm whether you are comfortable with the skill reading/writing that path. 4) If you need stricter control, ask the author for details on how long uploaded models and generated videos are retained and where tokens are stored. The metadata inconsistency about required config paths should be clarified with the publisher before broad deployment.

Getting Started

Share your 3D model files and I'll get started on AI animation generation. Or just tell me what you're thinking.

Try saying:

• "animate my 3D model files"
• "export 1080p MP4"
• "animate this 3D character walking and"

Quick Start Setup

This skill connects to a cloud processing backend. On first use, set up the connection automatically and let the user know ("Connecting...").

Token check: Look for NEMO_TOKEN in the environment. If found, skip to session creation. Otherwise:

• Generate a UUID as client identifier
• POST https://mega-api-prod.nemovideo.ai/api/auth/anonymous-token with X-Client-Id header
• Extract data.token from the response — this is your NEMO_TOKEN (100 free credits, 7-day expiry)

Session: POST https://mega-api-prod.nemovideo.ai/api/tasks/me/with-session/nemo_agent with Bearer auth and body {"task_name":"project"}. Keep the returned session_id for all operations.

Let the user know with a brief "Ready!" when setup is complete. Don't expose tokens or raw API output.

AI Animation 3D Model — Animate 3D Models into Video

Send me your 3D model files and describe the result you want. The AI animation generation runs on remote GPU nodes — nothing to install on your machine.

A quick example: upload a static OBJ or FBX character model, type "animate this 3D character walking and waving, then export as MP4", and you'll get a 1080p MP4 back in roughly 1-3 minutes. All rendering happens server-side.

Worth noting: simpler models with clean topology animate more accurately and faster.

Matching Input to Actions

User prompts referencing ai animation 3d model, aspect ratio, text overlays, or audio tracks get routed to the corresponding action via keyword and intent classification.

User says...	Action	Skip SSE?
"export" / "导出" / "download" / "send me the video"	→ §3.5 Export	✅
"credits" / "积分" / "balance" / "余额"	→ §3.3 Credits	✅
"status" / "状态" / "show tracks"	→ §3.4 State	✅
"upload" / "上传" / user sends file	→ §3.2 Upload	✅
Everything else (generate, edit, add BGM…)	→ §3.1 SSE	❌

Cloud Render Pipeline Details

Each export job queues on a cloud GPU node that composites video layers, applies platform-spec compression (H.264, up to 1080x1920), and returns a download URL within 30-90 seconds. The session token carries render job IDs, so closing the tab before completion orphans the job.

Every API call needs Authorization: Bearer <NEMO_TOKEN> plus the three attribution headers above. If any header is missing, exports return 402.

Headers are derived from this file's YAML frontmatter. X-Skill-Source is ai-animation-3d-model, X-Skill-Version comes from the version field, and X-Skill-Platform is detected from the install path (~/.clawhub/ = clawhub, ~/.cursor/skills/ = cursor, otherwise unknown).

API base: https://mega-api-prod.nemovideo.ai

Create session: POST /api/tasks/me/with-session/nemo_agent — body {"task_name":"project","language":"<lang>"} — returns task_id, session_id.

Send message (SSE): POST /run_sse — body {"app_name":"nemo_agent","user_id":"me","session_id":"<sid>","new_message":{"parts":[{"text":"<msg>"}]}} with Accept: text/event-stream. Max timeout: 15 minutes.

Upload: POST /api/upload-video/nemo_agent/me/<sid> — file: multipart -F "files=@/path", or URL: {"urls":["<url>"],"source_type":"url"}

Credits: GET /api/credits/balance/simple — returns available, frozen, total

Session state: GET /api/state/nemo_agent/me/<sid>/latest — key fields: data.state.draft, data.state.video_infos, data.state.generated_media

Export (free, no credits): POST /api/render/proxy/lambda — body {"id":"render_<ts>","sessionId":"<sid>","draft":<json>,"output":{"format":"mp4","quality":"high"}}. Poll GET /api/render/proxy/lambda/<id> every 30s until status = completed. Download URL at output.url.

Supported formats: mp4, mov, avi, webm, mkv, jpg, png, gif, webp, mp3, wav, m4a, aac.

Error Codes

• 0 — success, continue normally
• 1001 — token expired or invalid; re-acquire via /api/auth/anonymous-token
• 1002 — session not found; create a new one
• 2001 — out of credits; anonymous users get a registration link with ?bind=<id>, registered users top up
• 4001 — unsupported file type; show accepted formats
• 4002 — file too large; suggest compressing or trimming
• 400 — missing X-Client-Id; generate one and retry
• 402 — free plan export blocked; not a credit issue, subscription tier
• 429 — rate limited; wait 30s and retry once

Translating GUI Instructions

The backend responds as if there's a visual interface. Map its instructions to API calls:

• "click" or "点击" → execute the action via the relevant endpoint
• "open" or "打开" → query session state to get the data
• "drag/drop" or "拖拽" → send the edit command through SSE
• "preview in timeline" → show a text summary of current tracks
• "Export" or "导出" → run the export workflow

Reading the SSE Stream

Text events go straight to the user (after GUI translation). Tool calls stay internal. Heartbeats and empty data: lines mean the backend is still working — show "⏳ Still working..." every 2 minutes.

About 30% of edit operations close the stream without any text. When that happens, poll /api/state to confirm the timeline changed, then tell the user what was updated.

Draft field mapping: t=tracks, tt=track type (0=video, 1=audio, 7=text), sg=segments, d=duration(ms), m=metadata.

Timeline (3 tracks): 1. Video: city timelapse (0-10s) 2. BGM: Lo-fi (0-10s, 35%) 3. Title: "Urban Dreams" (0-3s)

Common Workflows

Quick edit: Upload → "animate this 3D character walking and waving, then export as MP4" → Download MP4. Takes 1-3 minutes for a 30-second clip.

Batch style: Upload multiple files in one session. Process them one by one with different instructions. Each gets its own render.

Iterative: Start with a rough cut, preview the result, then refine. The session keeps your timeline state so you can keep tweaking.

Tips and Tricks

The backend processes faster when you're specific. Instead of "make it look better", try "animate this 3D character walking and waving, then export as MP4" — concrete instructions get better results.

Max file size is 500MB. Stick to OBJ, FBX, GLB, GLTF for the smoothest experience.

Export your 3D model as GLB for the best compatibility and smallest file size.