Ai Animated Video Maker

Skip the learning curve of professional editing software. Describe what you want — turn my product description into a 30-second animated explainer video — an...

Security Scan

The skill's requirements and runtime instructions are coherent with an AI video-rendering service: it needs a NEMO_TOKEN (or will obtain an anonymous one), uploads user media to a remote render backend, and does not request unrelated credentials or install arbitrary software locally.

Purpose & Capability

Name/description (animated video generation) matches the declared primary credential (NEMO_TOKEN) and the runtime API endpoints. One minor metadata mismatch: the registry-level summary listed no required config paths, while the SKILL.md frontmatter includes a config path (~/.config/nemovideo/) — plausible but inconsistent and worth confirming.

Instruction Scope

SKILL.md focuses on the render workflow (session creation, SSE chat, upload, export and polling) which is within scope. It instructs the agent to read the skill's own frontmatter and inspect common install paths (e.g., ~/.clawhub/, ~/.cursor/skills/) to set an X-Skill-Platform header — functionally reasonable but a privacy/detail leak risk because it reads local path information and sends that platform attribution to the backend.

Install Mechanism

Instruction-only skill with no install spec or code files; nothing is written to disk by an installer. Lowest-risk install mechanism.

Credentials

Only requests a single service credential (NEMO_TOKEN) and documents how to obtain an anonymous token if missing. No unrelated secrets or multiple credentials are requested. It does declare a config path for its own use, which is proportionate to a client that may cache session state.

Persistence & Privilege

always:false and normal autonomous invocation are set. The skill does not request permanent system-wide privileges or attempt to modify other skills' configs.

Assessment

This skill will upload any images, video, or audio you provide to a third‑party backend (mega-api-prod.nemovideo.ai) for processing and requires a NEMO_TOKEN (or will request an anonymous token on your behalf). Before installing/using: (1) Confirm you are comfortable with your media and any transcript being sent to that external service; avoid uploading sensitive or confidential content. (2) Verify the backend domain is legitimate for the vendor you expect. (3) Be aware the skill reads its own SKILL.md frontmatter and inspects common install paths to set attribution headers — this can reveal which client/platform you use. (4) The registry metadata and SKILL.md disagree about config path requirements (minor); if you care where local state is stored, check ~/.config/nemovideo/ after first run. Overall the permissions are proportional to its purpose, but review the service's privacy/terms and avoid sending sensitive data.

Getting Started

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

Try saying:

• "create my text or images"
• "export 1080p MP4"
• "turn my product description into a"

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 Animated Video Maker — Create Animated Videos from Text

Drop your text or images in the chat and tell me what you need. I'll handle the AI animation generation on cloud GPUs — you don't need anything installed locally.

Here's a typical use: you send a a short text script or three character illustration images, ask for turn my product description into a 30-second animated explainer video, and about 1-2 minutes later you've got a MP4 file ready to download. The whole thing runs at 1080p by default.

One thing worth knowing — shorter scripts under 60 seconds produce tighter, more watchable animations.

Matching Input to Actions

User prompts referencing ai animated video 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-animated-video-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 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)

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

Common Workflows

Quick edit: Upload → "turn my product description into a 30-second animated explainer video" → 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.

Tips and Tricks

The backend processes faster when you're specific. Instead of "make it look better", try "turn my product description into a 30-second animated explainer video" — 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.