Ai Animation Video

generate images or text into animated MP4 videos with this skill. Works with PNG, JPG, MP4, GIF files up to 200MB. content creators, marketers, educators use...

Security Scan

The skill's requested credential and runtime instructions line up with its stated purpose (calling a cloud video-rendering API using NEMO_TOKEN), but small metadata inconsistencies and the unknown source mean you should review before installing.

Purpose & Capability

The skill is an instruction-only wrapper for a cloud rendering API. Requiring a single API token (NEMO_TOKEN) is consistent with a service that renders videos on cloud GPUs.

Instruction Scope

SKILL.md instructs the agent to use NEMO_TOKEN (or obtain an anonymous token via POST to https://mega-api-prod.nemovideo.ai) and to call several documented endpoints (session, SSE chat, upload, export). It does not direct reading unrelated local files or other secrets, but it references deriving headers from the install path (detecting ~/.clawhub/ or ~/.cursor/skills/) which implies filesystem awareness; the guidance is ambiguous about whether the agent must probe those paths.

Install Mechanism

There is no install spec and no code files; this is instruction-only, so nothing is downloaded or written to disk by the skill itself.

Credentials

Only NEMO_TOKEN is required, which fits a cloud API. However the SKILL.md frontmatter includes a configPaths entry (~/.config/nemovideo/) while the registry metadata reported no required config paths—this mismatch should be clarified. No other unrelated secrets are requested.

Persistence & Privilege

The skill is not always-enabled and uses normal autonomous-invocation defaults. It asks to store session tokens for API interaction (expected) but does not request elevated or cross-skill configuration access.

Assessment

This skill appears to do what it says: talk to a third-party cloud video service using a single API token. Before installing, consider: (1) Source verification — the skill has no homepage or known source, so confirm you trust calls to https://mega-api-prod.nemovideo.ai. (2) Data privacy — uploads (images, audio) go to that third party; avoid sending sensitive content. (3) Token handling — the skill suggests generating/storing an anonymous token; verify how and where tokens/sessions will be stored and never disclose your tokens in chat. (4) Metadata mismatch — the frontmatter mentions a config path (~/.config/nemovideo/) even though registry metadata listed none; ask the publisher to clarify whether the skill will read that directory. If you are comfortable with the external service and these behaviors, the permission set is proportionate to the stated functionality.

Getting Started

Send me your images or text and I'll handle the AI animation generation. Or just describe what you're after.

Try saying:

• "generate a short story prompt or five character illustrations into a 1080p MP4"
• "turn these character images into a 30-second animated scene with motion and transitions"
• "creating animated videos from static images or text prompts for content creators, marketers, educators"

Automatic Setup

On first interaction, connect to the processing API before doing anything else. Show a brief status like "Setting things up...".

Token: If NEMO_TOKEN environment variable is already set, use it and skip to Session below.

Free token: Generate a UUID as client identifier, then POST to https://mega-api-prod.nemovideo.ai/api/auth/anonymous-token with header X-Client-Id: <uuid>. The response field data.token becomes your NEMO_TOKEN (100 credits, 7-day expiry).

Session: POST to https://mega-api-prod.nemovideo.ai/api/tasks/me/with-session/nemo_agent with Bearer auth and body {"task_name":"project"}. Save session_id from the response.

Confirm to the user you're connected and ready. Don't print tokens or raw JSON.

AI Animation Video — Generate Animated Videos from Images

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 short story prompt or five character illustrations and want to turn these character images into a 30-second animated scene with motion and transitions — the backend processes it in about 1-3 minutes and hands you a 1080p MP4.

Tip: simpler backgrounds animate more smoothly and reduce processing time.

Matching Input to Actions

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

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

Include Authorization: Bearer <NEMO_TOKEN> and all attribution headers on every request — omitting them triggers a 402 on export.

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)

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.

Error Handling

Code	Meaning	Action
0	Success	Continue
1001	Bad/expired token	Re-auth via anonymous-token (tokens expire after 7 days)
1002	Session not found	New session §3.0
2001	No credits	Anonymous: show registration URL with ?bind=<id> (get <id> from create-session or state response when needed). Registered: "Top up credits in your account"
4001	Unsupported file	Show supported formats
4002	File too large	Suggest compress/trim
400	Missing X-Client-Id	Generate Client-Id and retry (see §1)
402	Free plan export blocked	Subscription tier issue, NOT credits. "Register or upgrade your plan to unlock export."
429	Rate limit (1 token/client/7 days)	Retry in 30s once

Tips and Tricks

The backend processes faster when you're specific. Instead of "make it look better", try "turn these character images into a 30-second animated scene with motion and transitions" — 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 and web platforms.

Common Workflows

Quick edit: Upload → "turn these character images into a 30-second animated scene with motion and transitions" → 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.