Animated Video

Skip the learning curve of professional editing software. Describe what you want — turn these images into an animated explainer video with motion and transit...

Security Scan

The skill's requirements and runtime instructions are coherent with a cloud-based video-rendering integration: it only needs a single service token and uses documented API endpoints to upload media, start jobs, and poll status.

Purpose & Capability

The skill claims to produce animated videos via a cloud backend. The only declared credential (NEMO_TOKEN) and the listed API endpoints (upload, render, state, credits) match that purpose. No unrelated credentials or binaries are requested.

Instruction Scope

SKILL.md contains concrete runtime instructions (create anonymous token if no NEMO_TOKEN, create session, upload, SSE handling, poll export). All instructions are scoped to interacting with the nemo-video backend and handling render jobs. The skill does not instruct the agent to read arbitrary local files or unrelated environment variables.

Install Mechanism

This is an instruction-only skill with no install spec and no code files, which minimizes installation risk. All network calls go to a single domain (mega-api-prod.nemovideo.ai).

Credentials

Only one credential is required (NEMO_TOKEN), which is proportional to a cloud-rendering service. The SKILL.md explains how to obtain an anonymous token if none is provided. Note: the frontmatter in SKILL.md lists a config path (~/.config/nemovideo/) while the registry metadata shows no required config paths — this mismatch should be clarified but is not itself critical.

Persistence & Privilege

The skill is not forced-always and uses normal autonomous invocation. It instructs storing a session_id for job state, and can obtain a short-lived anonymous NEMO_TOKEN (100 credits, 7 days). If the agent persists that token or writes config to ~/.config/nemovideo/, that would be expected for this service but users should be aware that tokens and uploaded media are sent to the external backend.

Assessment

This skill uploads your images/audio/text to an external rendering service (mega-api-prod.nemovideo.ai) and uses a NEMO_TOKEN to authorize requests. If you install it, expect uploads and temporary tokens to be sent to that backend; avoid sending highly sensitive data (private credentials, PII you wouldn't want stored externally). Consider providing your own NEMO_TOKEN from the service (instead of letting the skill generate an anonymous token) if you want more control. Also ask the skill author to clarify the mismatch between the registry-config paths and the SKILL.md frontmatter (~/.config/nemovideo/) so you know whether any files will be written to your config directory.

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 an animated"

First-Time Connection

When a user first opens this skill, connect to the processing backend automatically. Briefly let them know (e.g. "Setting up...").

Authentication: Check if NEMO_TOKEN is set in the environment. If it is, skip to step 2.

1. Obtain a free token: Generate a random UUID as client identifier. POST to https://mega-api-prod.nemovideo.ai/api/auth/anonymous-token with header X-Client-Id set to that UUID. The response data.token is your NEMO_TOKEN — 100 free credits, valid 7 days.
2. Create a session: POST to https://mega-api-prod.nemovideo.ai/api/tasks/me/with-session/nemo_agent with Authorization: Bearer <token>, Content-Type: application/json, and body {"task_name":"project","language":"<detected>"}. Store the returned session_id for all subsequent requests.

Keep setup communication brief. Don't display raw API responses or token values to the user.

Animated Video — Create Animated Videos from Images

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

Here's a typical use: you send a five product images and a script, ask for turn these images into an animated explainer video with motion and transitions, 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 — fewer scenes per video means faster render and smoother animation.

Matching Input to Actions

User prompts referencing animated 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.

Three attribution headers are required on every request and must match this file's frontmatter:

Header	Value
X-Skill-Source	animated-video
X-Skill-Version	frontmatter version
X-Skill-Platform	auto-detect: clawhub / cursor / unknown from install path

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)

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

SSE Event Handling

Event	Action
Text response	Apply GUI translation (§4), present to user
Tool call/result	Process internally, don't forward
heartbeat / empty data:	Keep waiting. Every 2 min: "⏳ Still working..."
Stream closes	Process final response

~30% of editing operations return no text in the SSE stream. When this happens: poll session state to verify the edit was applied, then summarize changes to the user.

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 images into an animated explainer video with motion and transitions" — concrete instructions get better results.

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

Export as MP4 for widest compatibility.

Common Workflows

Quick edit: Upload → "turn these images into an animated explainer video with motion and transitions" → 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.