Image To Video Converter Ai

Turn three product photos in JPG format into 1080p animated video clips just by typing what you need. Whether it's converting static photos into shareable vi...

Security Scan

The skill's declared requirements and runtime instructions line up with a cloud-based image→video service: it needs a NEMO_TOKEN and instructs the agent to call nemovideo.ai endpoints to upload images, run jobs, and download results — there are no unrelated credentials, installs, or hidden steps, but you should be aware that your images and an auth token are sent to an external service.

Purpose & Capability

The name/description (convert images to short videos) match the required credential (NEMO_TOKEN) and the SKILL.md describes APIs for uploading images, creating sessions, running exports, and downloading results. There is a minor metadata mismatch: the frontmatter lists a config path (~/.config/nemovideo/) that the SKILL.md itself never reads or explains, but this is likely informational.

Instruction Scope

Runtime instructions direct the agent to check for NEMO_TOKEN, create an anonymous token from the service if missing, create sessions, upload files, use SSE for streaming responses, poll render status, and return download URLs. All of these actions are within the stated purpose, but they imply that user images and session tokens will be sent to an external cloud backend (mega-api-prod.nemovideo.ai). If you expect local-only processing or want to avoid external uploads of sensitive images, this is not the right skill.

Install Mechanism

This is instruction-only with no install spec and no code files. That minimizes disk-write/execute risk — the skill relies on making HTTP calls at runtime rather than downloading or running additional packages.

Credentials

Only one environment variable (NEMO_TOKEN) is declared and is appropriate for a cloud API. The SKILL.md also describes an anonymous-token flow when NEMO_TOKEN is absent, meaning the skill can operate without a pre-provided secret. The metadata lists a config path that isn’t used in the instructions — harmless but inconsistent.

Persistence & Privilege

The skill does not request always:true and does not declare actions that modify other skills or system-wide settings. It will store session IDs for job coordination (normal for a service-backed tool) but does not ask for elevated or persistent platform privileges.

Assessment

This skill appears to do what it says: it uploads your images to a third‑party cloud service (mega-api-prod.nemovideo.ai) and returns rendered video URLs. Before installing or using it, consider: 1) privacy: do not upload sensitive or restricted images unless you trust the service and have read its retention/privacy policy; 2) tokens: you can either provide your own NEMO_TOKEN or let the skill request an anonymous token from the service (100 free credits, 7‑day expiry) — prefer an ephemeral token if possible; 3) verify the external domain and terms of service if you care about intellectual property or retention; 4) note the small metadata inconsistency (declared config path not used) — not dangerous but worth knowing. If any of the above concerns you, do not use the skill or provide sample images instead of production content.

Getting Started

Got 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 photos into a 30-second video with smooth transitions"
• "converting static photos into shareable video content for marketers, social media creators"

Quick Start Setup

This skill connects to a cloud processing backend. On first use, set up the connection automatically and let the user know ("Connecting...").

Token check: Look for NEMO_TOKEN in the environment. If found, skip to session creation. Otherwise:

• Generate a UUID as client identifier
• POST https://mega-api-prod.nemovideo.ai/api/auth/anonymous-token with X-Client-Id header
• Extract data.token from the response — this is your NEMO_TOKEN (100 free credits, 7-day expiry)

Session: POST https://mega-api-prod.nemovideo.ai/api/tasks/me/with-session/nemo_agent with Bearer auth and body {"task_name":"project"}. Keep the returned session_id for all operations.

Let the user know with a brief "Ready!" when setup is complete. Don't expose tokens or raw API output.

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

Tip: using 5-10 images gives the AI enough content to build smooth transitions.

Matching Input to Actions

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

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

Header	Value
X-Skill-Source	image-to-video-converter-ai
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.

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

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 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 photos into a 30-second video with smooth transitions" — concrete instructions get better results.

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

Export as MP4 for widest compatibility across social platforms.

Common Workflows

Quick edit: Upload → "turn these photos into a 30-second video with smooth transitions" → 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.