Image To Video Converter Online

convert images into animated video clips with this skill. Works with JPG, PNG, WEBP, GIF files up to 200MB. marketers, social media creators, small business...

Security Scan

The skill's declared purpose (cloud image→video conversion) matches most of its instructions (calls to a remote nemovideo API and file uploads), but there are inconsistencies about config paths and some privacy/operational implications you should understand before installing.

Purpose & Capability

The skill claims to convert images to videos and requires a single credential NEMO_TOKEN for API access — that is coherent. However the SKILL.md frontmatter includes a config path (~/.config/nemovideo/) while the registry metadata listed no required config paths, creating an inconsistency about local config access.

Instruction Scope

Runtime instructions are explicit: obtain/use NEMO_TOKEN (or request an anonymous token), create a session, upload user files, stream SSE responses, poll for render status, and include attribution headers. This is in-scope for a cloud conversion service. Important privacy/behavior note: the skill will upload users' images/audio to mega-api-prod.nemovideo.ai (third-party cloud) — any sensitive content will be transmitted off-device. Instructions also tell the agent to 'save session_id' (unspecified where), which could imply storing identifiers locally or in-memory.

Install Mechanism

This is an instruction-only skill with no install spec and no code files, so nothing is written to disk by an installer. Lowest install risk.

Credentials

Only NEMO_TOKEN is declared as required and is the primary credential — appropriate for an API-backed converter. The frontmatter’s configPaths entry (~/.config/nemovideo/) is not reflected in the registry metadata and is not referenced in the main instructions, creating ambiguity about whether the skill will read or write local config files. No other unrelated secrets or broad permissions are requested.

Persistence & Privilege

The skill is not always-enabled and allows user invocation (defaults). It does not request elevated platform privileges. The only potential persistence concern is unspecified saving of session_id or token management (e.g., where the skill stores tokens or session state), which is not detailed.

What to consider before installing

This skill appears to be what it says (a cloud image→video converter) but it will upload your images and audio to an external domain (mega-api-prod.nemovideo.ai). Before installing, consider: (1) Do not use it with sensitive or private images unless you trust the service and its privacy policy; (2) confirm how and where session IDs and tokens are stored (the SKILL.md says 'save session_id' but doesn't say whether that's local disk or memory); (3) clarify the config path inconsistency (~/.config/nemovideo/ is in the frontmatter but not the registry metadata) — if the skill will read/write that directory, you should know what it stores; (4) verify the NEMO_TOKEN issuer and whether automatic anonymous-token generation is acceptable (those tokens expire in 7 days and grant credits); and (5) because the source/homepage are unknown, prefer only non-sensitive test data and ask the publisher for provenance and a privacy/terms link before using with real content.

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 photos into a 30-second"

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.

Image to Video Converter Online — Convert Photos 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 five product photos in JPG format and want to turn these photos into a 30-second video with transitions and background music — the backend processes it in about 30-60 seconds and hands you a 1080p MP4.

Tip: using 5-10 images gives the best pacing for a 15-30 second video.

Matching Input to Actions

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

Base URL: https://mega-api-prod.nemovideo.ai

Endpoint	Method	Purpose
/api/tasks/me/with-session/nemo_agent	POST	Start a new editing session. Body: {"task_name":"project","language":"<lang>"}. Returns session_id.
/run_sse	POST	Send a user message. Body includes app_name, session_id, new_message. Stream response with Accept: text/event-stream. Timeout: 15 min.
/api/upload-video/nemo_agent/me/<sid>	POST	Upload a file (multipart) or URL.
/api/credits/balance/simple	GET	Check remaining credits (available, frozen, total).
/api/state/nemo_agent/me/<sid>/latest	GET	Fetch current timeline state (draft, video_infos, generated_media).
/api/render/proxy/lambda	POST	Start export. Body: {"id":"render_<ts>","sessionId":"<sid>","draft":<json>,"output":{"format":"mp4","quality":"high"}}. Poll status every 30s.

Accepted file types: 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	image-to-video-converter-online
X-Skill-Version	frontmatter version
X-Skill-Platform	auto-detect: clawhub / cursor / unknown from install path

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

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

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)

Tips and Tricks

The backend processes faster when you're specific. Instead of "make it look better", try "turn these photos 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 and devices.

Common Workflows

Quick edit: Upload → "turn these photos into a 30-second video with transitions and background music" → Download MP4. Takes 30-60 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.