Image To Video Invideo

convert images into animated video clips with this skill. Works with JPG, PNG, WEBP, GIF files up to 200MB. marketers use it for turning static images into s...

Security Scan

The skill's declared purpose (turning images into short videos) matches what its instructions do, but there are a few small inconsistencies you should be aware of before installing.

Purpose & Capability

The skill name and description align with the runtime instructions: it uploads images and calls a cloud rendering API. The single required credential (NEMO_TOKEN) is appropriate for an external video-rendering service.

Instruction Scope

Instructions direct the agent to send user images and metadata to https://mega-api-prod.nemovideo.ai (upload endpoints, SSE streaming, render/polling). That data flow is expected for this functionality, but it means user media will be transmitted to a third-party backend. The SKILL.md also asks the agent to auto-generate anonymous tokens if no NEMO_TOKEN is present and to auto-detect platform/install path for an X-Skill-Platform header — detecting the install path may require reading local agent paths. Those behaviors are within scope for the stated purpose but have privacy implications.

Install Mechanism

Instruction-only skill with no install spec and no code files. No binaries or archives are downloaded or written to disk by the skill itself.

Credentials

The skill declares only NEMO_TOKEN as required, which is proportional. However, the SKILL.md frontmatter references a config path (~/.config/nemovideo/) while the registry metadata lists no required config paths — this mismatch is an inconsistency. If the agent accesses that config directory (to read stored tokens or settings) it should have been declared.

Persistence & Privilege

The skill does not request always:true, does not install persistent components, and does not declare modifications to other skills or system-wide settings. Autonomous invocation is allowed by default but is not additionally privileged here.

Assessment

This skill appears to do what it says — upload images to a cloud API and return MP4s — but it will transmit your media and metadata to mega-api-prod.nemovideo.ai. Consider: (1) only install if you trust that domain and its privacy/TOS, (2) provide your own NEMO_TOKEN if you prefer not to let the skill auto-request an anonymous token, (3) be aware the skill may read or look for a local config path (~/.config/nemovideo/) despite the registry listing no config paths — ask the publisher to clarify that discrepancy, and (4) if you handle sensitive images, avoid using this skill or verify how uploads and stored renders are retained/deleted by the service.

Getting Started

Share your images and I'll get started on AI video creation. Or just tell me what you're thinking.

Try saying:

• "convert my images"
• "export 1080p MP4"
• "turn these images into a 30-second"

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 InVideo — Convert Images Into Shareable Videos

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

Say you have three product photos in JPG format and want to turn these images into a 30-second video with transitions and background music — the backend processes it in about 1-2 minutes and hands you a 1080p MP4.

Tip: using fewer images with longer durations per slide produces smoother-looking results.

Matching Input to Actions

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

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

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

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

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.

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)

Tips and Tricks

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

Common Workflows

Quick edit: Upload → "turn these images into a 30-second 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.