Ai Animations

Turn a product logo and brand colors into 1080p animated video clips just by typing what you need. Whether it's turning static images into animated video con...

Security Scan

The skill largely matches its stated purpose (cloud video rendering) but contains minor metadata mismatches and a few opaque instructions (auto-anonymous token flow, filesystem checks, and a directive to 'keep technical details out of the chat') that warrant caution before installing.

Purpose & Capability

Name/description describe cloud-based animation generation and the SKILL.md only asks for a single service token (NEMO_TOKEN) and network calls to a nemo video API — these are coherent with the stated purpose.

Instruction Scope

Runtime instructions describe API calls (session creation, SSE, upload, render polling) appropriate for a cloud render service. However the doc instructs generating an anonymous token automatically if NEMO_TOKEN is missing and to 'keep the technical details out of the chat' (a transparency concern). The skill also expects to perform filesystem checks (detect install path like ~/.clawhub/ or ~/.cursor/) and to upload files via multipart using local paths (files=@/path), which requires the agent to access local files — this is expected for an upload workflow but should be explicit to users.

Install Mechanism

Instruction-only skill with no install spec or external downloads — lowest install risk.

Credentials

Declared required credential is a single NEMO_TOKEN which is reasonable for a third‑party API. However the SKILL.md frontmatter includes configPaths (~/.config/nemovideo/) not reflected in the registry metadata, a mismatch worth questioning. The anonymous token flow (POST to the external API) is allowed but the skill will upload user images and any files supplied to the remote service — users should confirm they are comfortable sending their assets to that endpoint.

Persistence & Privilege

Does not request always:true, does not write other skills' config, and has no install-time persistence. It may create short-lived sessions on the remote service (normal for this type of tool).

What to consider before installing

This skill appears to do what it says (cloud-based animation rendering) but review a few items before installing: 1) The skill will upload images/files to an external domain (mega-api-prod.nemovideo.ai); confirm this is an expected third party and you are comfortable sharing those assets. 2) It uses a single token (NEMO_TOKEN) or will obtain an anonymous token automatically — if you don’t provide a token, the agent will make network calls to mint a token on your behalf. 3) The SKILL.md mentions reading install/config paths and using local file paths for uploads — verify the agent environment will only expose intended files. 4) There is a metadata mismatch: the frontmatter lists a config path (~/.config/nemovideo/) that the registry summary did not. Ask the skill author to confirm why that path is needed and to explain the anonymous-token flow and the “keep technical details out of the chat” recommendation. If you need higher assurance, request the skill author or publisher (or their homepage) and verify the API domain and privacy policy before use.

Getting Started

Share your images or text and I'll get started on AI animation generation. Or just tell me what you're thinking.

Try saying:

• "generate my images or text"
• "export 1080p MP4"
• "turn my static images into a"

Getting Connected

Before handling any user request, establish a connection to the backend API. Show a brief status like "Connecting...".

If NEMO_TOKEN is in the environment, use it directly and create a session. Otherwise, acquire a free starter token:

• Generate a UUID as client identifier
• POST to https://mega-api-prod.nemovideo.ai/api/auth/anonymous-token with the X-Client-Id header
• The response includes a token with 100 free credits valid for 7 days — use it as NEMO_TOKEN

Then create a session by POSTing to https://mega-api-prod.nemovideo.ai/api/tasks/me/with-session/nemo_agent with Bearer authorization and body {"task_name":"project","language":"en"}. The session_id in the response is needed for all following requests.

Tell the user you're ready. Keep the technical details out of the chat.

AI Animations — Turn Images Into Animated Videos

This tool takes your images or text and runs AI animation generation through a cloud rendering pipeline. You upload, describe what you want, and download the result.

Say you have a product logo and brand colors and want to turn my static images into a smooth animated video with motion effects — the backend processes it in about 1-2 minutes and hands you a 1080p MP4.

Tip: simpler images with clear subjects animate more cleanly than busy backgrounds.

Matching Input to Actions

User prompts referencing ai animations, 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.

Headers are derived from this file's YAML frontmatter. X-Skill-Source is ai-animations, 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).

All requests must include: Authorization: Bearer <NEMO_TOKEN>, X-Skill-Source, X-Skill-Version, X-Skill-Platform. Missing attribution headers will cause export to fail with 402.

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.

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.

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

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)

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

Tips and Tricks

The backend processes faster when you're specific. Instead of "make it look better", try "turn my static images into a smooth animated video with motion effects" — concrete instructions get better results.

Max file size is 200MB. Stick to PNG, JPG, MP4, GIF for the smoothest experience.

Export as MP4 for widest compatibility across social platforms and presentations.

Common Workflows

Quick edit: Upload → "turn my static images into a smooth animated video with motion effects" → Download MP4. Takes 1-2 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.