Video Maker Free Animation

Turn five product images and a script into 1080p animated MP4 videos just by typing what you need. Whether it's creating free animated videos from images or...

Security Scan

The skill's behavior mostly matches a cloud video-rendering tool, but there are metadata inconsistencies and a few instruction details that warrant caution before installing or running it with real secrets or private images.

Purpose & Capability

The skill's name/description match the runtime instructions (upload images, create session, render/export MP4). Requesting a NEMO_TOKEN credential is coherent for a cloud-rendering API. However, the SKILL.md frontmatter declares a config path (~/.config/nemovideo/) that is not listed in the registry's top-level requirements — this mismatch could be an oversight or indicate undeclared filesystem access.

Instruction Scope

Instructions direct the agent to call external endpoints (mega-api-prod.nemovideo.ai), upload files (multipart or via URL), open SSE streams, poll state, and map GUI actions to API calls. Those are expected for this purpose, but the SKILL.md also instructs 'auto-detect' the install path for X-Skill-Platform (which implies probing install paths) and asks the agent to create/use session tokens and potentially write/read a config directory — these file-system operations and install-path probing broaden the skill's scope beyond mere API calls and were not consistently declared.

Install Mechanism

Instruction-only skill with no install spec and no code files; nothing is written to disk by an installer. This is the lowest install risk category.

Credentials

Only one required env var (NEMO_TOKEN) is declared, which is proportionate for a remote API. The skill will also auto-obtain an anonymous token if none is present by POSTing to the service — that behavior is plausible but means the agent will make outbound network calls and may store or reuse returned tokens. Verify that any existing NEMO_TOKEN in your environment is intended for this service and not a different secret.

Persistence & Privilege

always is false and the skill does not request elevated platform privileges. However, the frontmatter mentions a config path (~/.config/nemovideo/) which implies persistent storage of session or token data; the registry metadata did not declare this path. That discrepancy should be resolved to understand what will be written to disk.

What to consider before installing

This skill appears to be a legitimate cloud video-renderer, but take these precautions before enabling it: 1) Confirm the external domain (mega-api-prod.nemovideo.ai) is a trusted service you want to send images and data to; uploads will leave your device. 2) Check whether you already have an env var named NEMO_TOKEN—if so, ensure it is safe to use here (don't reuse unrelated secrets). 3) Ask the publisher (or inspect a code release) to clarify the declared config path (~/.config/nemovideo/) and what the skill will store there; if you don't want persistent tokens, run in a restricted/ephemeral environment. 4) If you need stronger assurance, request a code-backed skill or an official homepage/source; as-is the skill is instruction-only and the metadata mismatch (config path present in SKILL.md but not in registry) is the main red flag.

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"

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.

Video Maker Free Animation — Create Animated Videos from Images

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

Say you have five product images and a script and want to turn these images into an animated video with transitions and background music — the backend processes it in about 1-2 minutes and hands you a 1080p MP4.

Tip: using fewer than 10 images keeps render times under a minute.

Matching Input to Actions

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

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

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

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 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)

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

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

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