Ai Animation Maker

Get animated MP4 videos ready to post, without touching a single slider. Upload your images or text (PNG, JPG, GIF, MP4, up to 200MB), say something like "tu...

Security Scan

The skill's requirements and runtime instructions align with a cloud-based video rendering service: it only requests a single service token (NEMO_TOKEN), makes API calls to nemovideo endpoints, and has no install actions or unrelated credential requests.

Purpose & Capability

The skill claims to render animations via a cloud backend and only requests a single NEMO_TOKEN and an optional config path (~/.config/nemovideo/) — both are coherent with a remote rendering service that needs a bearer token. No unrelated credentials or binaries are requested.

Instruction Scope

Instructions focus on session creation, SSE-based editing, uploads, and exports to a single hostname (mega-api-prod.nemovideo.ai). They also instruct reading the skill's YAML frontmatter and detecting an install path (~/.clawhub or ~/.cursor) to set X-Skill-Platform; this requires reading local paths which is reasonable for attribution but is slightly beyond pure API use. The skill instructs automatically obtaining an anonymous token if NEMO_TOKEN is not present (via POST to /api/auth/anonymous-token). No instructions ask for unrelated system files or other credentials.

Install Mechanism

There is no install spec and no code files — this is instruction-only. That minimizes disk writes and arbitrary code installation risk.

Credentials

Only NEMO_TOKEN is declared as required and is used as the bearer token for all API calls. The skill documents how to obtain an anonymous token if absent. The presence of a config path (~/.config/nemovideo/) is plausible for storing the token but is not excessive relative to the service's needs.

Persistence & Privilege

always is false, user-invocable and autonomous invocation are default platform behavior. The skill does not request to modify other skills or system-wide settings.

Assessment

This skill appears to do what it says: it sends uploads to a nemoVideo API and returns rendered videos. Before installing/using it, consider: (1) It will transmit any uploaded media to https://mega-api-prod.nemovideo.ai — don't upload sensitive content you wouldn't want sent to a third party. (2) If no NEMO_TOKEN is present the skill will request an anonymous token from the service automatically; decide whether you prefer to supply your own token. (3) The skill may read/write ~/.config/nemovideo/ and probe common install paths to set attribution headers — if you are uncomfortable with that local file access, don't enable the skill. (4) Confirm the domain is the official service for this tool; the skill will include X-Skill-* headers that may reveal which client/platform was used. If any of those behaviors are unacceptable, do not install or provide your token. Otherwise the skill is internally consistent with its stated purpose.

Getting Started

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

Try saying:

• "create my images or text"
• "export 1080p MP4"
• "turn these images into a 30-second"

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 Maker — Turn Images into Animated Videos

Send me your images or text and describe the result you want. The AI animation creation runs on remote GPU nodes — nothing to install on your machine.

A quick example: upload five product illustrations or a text prompt describing a scene, type "turn these images into a 30-second animated explainer video with motion effects", and you'll get a 1080p MP4 back in roughly 1-2 minutes. All rendering happens server-side.

Worth noting: simpler scenes with fewer elements animate more cleanly and process faster.

Matching Input to Actions

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

All calls go to https://mega-api-prod.nemovideo.ai. The main endpoints:

1. Session — POST /api/tasks/me/with-session/nemo_agent with {"task_name":"project","language":"<lang>"}. Gives you a session_id.
2. Chat (SSE) — POST /run_sse with session_id and your message in new_message.parts[0].text. Set Accept: text/event-stream. Up to 15 min.
3. Upload — POST /api/upload-video/nemo_agent/me/<sid> — multipart file or JSON with URLs.
4. Credits — GET /api/credits/balance/simple — returns available, frozen, total.
5. State — GET /api/state/nemo_agent/me/<sid>/latest — current draft and media info.
6. Export — POST /api/render/proxy/lambda with render ID and draft JSON. Poll GET /api/render/proxy/lambda/<id> every 30s for completed status and download URL.

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

Skill attribution — read from this file's YAML frontmatter at runtime:

• X-Skill-Source: ai-animation-maker
• X-Skill-Version: from frontmatter version
• X-Skill-Platform: detect from install path (~/.clawhub/ → clawhub, ~/.cursor/skills/ → cursor, else 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.

Draft JSON uses short keys: t for tracks, tt for track type (0=video, 1=audio, 7=text), sg for segments, d for duration in ms, m for metadata.

Example timeline summary:

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

Backend Response Translation

The backend assumes a GUI exists. Translate these into API actions:

Backend says	You do
"click [button]" / "点击"	Execute via API
"open [panel]" / "打开"	Query session state
"drag/drop" / "拖拽"	Send edit via SSE
"preview in timeline"	Show track summary
"Export button" / "导出"	Execute 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.

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 these images into a 30-second animated explainer video with motion effects" — concrete instructions get better results.

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

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

Common Workflows

Quick edit: Upload → "turn these images into a 30-second animated explainer 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.