Image To Video Io Ai

Skip the learning curve of professional editing software. Describe what you want — turn these images into a smooth animated video with transitions — and get...

Security Scan

The skill mostly does what its name says (call a remote API to turn images into video) and only needs a single API token, but there are small inconsistencies in the metadata and a few instructional details that deserve clarification before installing or providing credentials.

Purpose & Capability

The skill's name/description (image→video) matches the actions described in SKILL.md (upload images, create session, render, download). Requested credential (NEMO_TOKEN) is appropriate. However, the SKILL.md frontmatter includes a configPaths entry (~/.config/nemovideo/) that is not listed in the registry metadata (registry reported no config paths) — this mismatch is unexpected and should be explained.

Instruction Scope

Runtime instructions are focused on the remote API (anonymous token acquisition, session creation, SSE message stream, file upload, render/poll). The instructions do not direct the agent to read arbitrary local files beyond user-provided uploads. Two areas to clarify: (1) header derivation uses the agent's install path (detecting ~/.clawhub/ or ~/.cursor/skills/), which implies the agent may inspect its environment/install location to set X-Skill-Platform; (2) SKILL.md references 'the three attribution headers above' but the exact set and usage is a little inconsistent in the document. These are scope/clarity issues rather than direct red flags, but they warrant confirmation.

Install Mechanism

No install spec or code files — instruction-only skill. Nothing is downloaded or written to disk by an installer, which reduces persistence and host-side risk.

Credentials

Only NEMO_TOKEN is declared as required and is used in the instructions. That is proportionate to a cloud-rendering service. The SKILL.md frontmatter's configPaths (~/.config/nemovideo/) suggests the skill might access a user config directory; this was not declared in the registry metadata and should be clarified. No other sensitive env vars or unrelated credentials are requested.

Persistence & Privilege

Skill is not always-enabled and does not request installation. It does not request elevated privileges or to modify other skills. Autonomous invocation is allowed (default) but this is normal for skills and not by itself concerning.

What to consider before installing

This skill appears to implement its stated purpose (remote image→video rendering) and only asks for a single API token, but you should confirm a few things before installing or supplying credentials: 1) Ask the publisher why SKILL.md lists a config path (~/.config/nemovideo/) while the registry metadata does not — confirm whether the skill will read files from that directory. 2) Confirm exactly which HTTP headers the skill will send (X-Client-Id, X-Skill-Source, X-Skill-Version, X-Skill-Platform, etc.) and whether any other local identifiers are read. 3) If you're asked to provide a long-lived NEMO_TOKEN, prefer using an anonymous starter token or short-lived credential for testing; avoid supplying other unrelated secrets. 4) Treat uploaded images as potentially exposed to the remote service; do not upload sensitive or private images until you verify the service's privacy policy and ownership. 5) Because the skill has no published homepage or known owner, consider requesting more provenance (source code, privacy/terms, or an official homepage) before trusting it with production or sensitive data.

Getting Started

Got static images to work with? Send it over and tell me what you need — I'll take care of the AI video creation.

Try saying:

• "convert three product photos in JPG format into a 1080p MP4"
• "turn these images into a smooth animated video with transitions"
• "converting still images into shareable video content for marketers and social media creators"

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.

Image to Video IO AI — Convert Images into Video Clips

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

A quick example: upload three product photos in JPG format, type "turn these images into a smooth animated video with transitions", and you'll get a 1080p MP4 back in roughly 30-90 seconds. All rendering happens server-side.

Worth noting: using high-resolution images produces noticeably smoother motion output.

Matching Input to Actions

User prompts referencing image to video io ai, 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.

Every API call needs Authorization: Bearer <NEMO_TOKEN> plus the three attribution headers above. If any header is missing, exports return 402.

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

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.

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

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.

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)

Common Workflows

Quick edit: Upload → "turn these images into a smooth animated video with transitions" → Download MP4. Takes 30-90 seconds 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 a smooth animated video with transitions" — concrete instructions get better results.

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

Export as MP4 for widest compatibility across social platforms.