Image To Video Free Unlimited

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

Security Scan

The skill generally matches an image→video cloud service (it only needs a NEMO_TOKEN and uses a remote API), but there are small internal inconsistencies and a few instructions that warrant caution before installing.

Purpose & Capability

The declared primary credential (NEMO_TOKEN) and the API endpoints in SKILL.md align with an image-to-video cloud service. However the SKILL.md YAML frontmatter lists a config path (~/.config/nemovideo/) while the registry metadata says no required config paths — an internal mismatch that should be clarified.

Instruction Scope

Runtime instructions request using NEMO_TOKEN or obtaining an anonymous token from https://mega-api-prod.nemovideo.ai, creating sessions, uploading files (multipart or URL), and polling renders — all expected. But the agent is also instructed to derive attribution headers from the skill's YAML frontmatter and to detect the install path to set X-Skill-Platform; reading install paths or skill files for headers is unnecessary for core functionality and could reveal local environment structure.

Install Mechanism

No install spec or code is provided (instruction-only). This minimizes on-disk write/execution risk.

Credentials

Only one credential (NEMO_TOKEN) is required, which is proportionate. The SKILL.md flow also allows acquiring a short-lived anonymous token if none is provided. Still, the frontmatter's mention of a config path implies possible access to ~/.config/nemovideo/ that wasn't declared in the registry metadata — clarify whether that path will be read or used.

Persistence & Privilege

Skill is not force-included (always: false) and does not request system-wide privileges. It does instruct creating ephemeral sessions with the remote service and does not request modifying other skills.

What to consider before installing

This skill appears to be an instruction-only integration with a remote image→video API and primarily needs a NEMO_TOKEN. Before installing: (1) verify the upstream domain (mega-api-prod.nemovideo.ai) is the intended service and trustworthy; (2) prefer using an anonymous starter token (the skill supports it) rather than placing sensitive or long-lived secrets in NEMO_TOKEN; (3) ask the publisher to explain the discrepancy between the registry (no config paths) and the SKILL.md frontmatter (~/.config/nemovideo/) and whether the skill will read local paths or files; (4) avoid uploading sensitive images to any third-party service unless you understand their retention/privacy policy; and (5) because the skill source/homepage is unknown, treat it as unverified until you can confirm provenance.

Getting Started

Ready when you are. Drop your still images here or describe what you want to make.

Try saying:

• "convert three product photos in JPG format into a 1080p MP4"
• "turn these images into a smooth video with transitions"
• "converting static images into shareable videos for 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 Free Unlimited — Convert Images Into Shareable Videos

This tool takes your still 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 smooth video with transitions — the backend processes it in about 30-60 seconds and hands you a 1080p MP4.

Tip: fewer images per batch means faster processing and smoother output.

Matching Input to Actions

User prompts referencing image to video free unlimited, 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-free-unlimited, 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 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 images into a smooth 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 all platforms.

Common Workflows

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