Free Image To

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

Security Scan

The skill's requests and runtime instructions align with its stated purpose (image → video conversion using a remote API); nothing appears to be trying to do unrelated or covert actions, but there are a few small inconsistencies and privacy considerations you should know before installing.

Purpose & Capability

Name/description (convert images to short MP4s) matches the instructions, which call a remote video-rendering API. Requiring a NEMO_TOKEN (API token) is proportional and expected for a hosted rendering service.

Instruction Scope

The SKILL.md gives explicit API flows (anonymous-token acquisition, session creation, SSE streaming, upload endpoints) and limits itself to operations needed for rendering. It does reference reading/storing a session_id and detecting install path to set X-Skill-Platform, which implies the agent may inspect its environment/paths; this is reasonable for attribution headers but should be noted. The instructions also assume file uploads via local paths or URLs — the agent will transmit user-supplied images to the external API, so sensitive images are sent off-host.

Install Mechanism

Instruction-only skill with no install spec or code files; nothing is downloaded or written to disk by an installer. This is the lowest-risk install pattern.

Credentials

Only one environment variable is declared (NEMO_TOKEN) which is appropriate for an API-backed service. The SKILL.md and metadata additionally reference a config path (~/.config/nemovideo/) and detect install path for header attribution; the registry metadata listed no required config paths — this mismatch is minor but worth noting.

Persistence & Privilege

always is false and the skill does not request elevated or persistent platform-wide privileges. It asks to store a session token for ongoing requests (normal for a session-based API) but does not attempt to modify other skills or system settings.

Assessment

This skill appears to be what it says: it will upload images to a third‑party rendering service (mega-api-prod.nemovideo.ai) and use a NEMO_TOKEN for authorization. If you install it, be aware that: (1) any images you send will be transmitted to that external service — do not upload sensitive or private images unless you accept that; (2) if you don't provide a NEMO_TOKEN, the skill will automatically request an anonymous token from the vendor and use it (tokens are described as temporary/7-day), which means an outbound network call will be made on first use; (3) metadata mentions a config folder (~/.config/nemovideo/) and the instructions read the agent's install path to set attribution headers — this is mainly for telemetry/attribution but is an inconsistency with the registry metadata you may want clarified. If these behaviors are acceptable, the skill is coherent with moderate confidence. If you need stronger guarantees about data retention/privacy or explicit storage locations, ask the publisher for their privacy/retention policy and whether uploads are persisted beyond rendering.

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

First-Time Connection

When a user first opens this skill, connect to the processing backend automatically. Briefly let them know (e.g. "Setting up...").

Authentication: Check if NEMO_TOKEN is set in the environment. If it is, skip to step 2.

1. Obtain a free token: Generate a random UUID as client identifier. POST to https://mega-api-prod.nemovideo.ai/api/auth/anonymous-token with header X-Client-Id set to that UUID. The response data.token is your NEMO_TOKEN — 100 free credits, valid 7 days.
2. Create a session: POST to https://mega-api-prod.nemovideo.ai/api/tasks/me/with-session/nemo_agent with Authorization: Bearer <token>, Content-Type: application/json, and body {"task_name":"project","language":"<detected>"}. Store the returned session_id for all subsequent requests.

Keep setup communication brief. Don't display raw API responses or token values to the user.

Free Image To Video — Convert Images Into Videos

Drop your images in the chat and tell me what you need. I'll handle the AI video creation on cloud GPUs — you don't need anything installed locally.

Here's a typical use: you send a three product photos in JPG format, ask for turn these images into a slideshow video with transitions and background music, and about 30-60 seconds later you've got a MP4 file ready to download. The whole thing runs at 1080p by default.

One thing worth knowing — using fewer than 10 images speeds up processing significantly.

Matching Input to Actions

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

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

Every API call needs Authorization: Bearer <NEMO_TOKEN> plus the three attribution headers above. If any header is missing, exports return 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.

SSE Event Handling

Event	Action
Text response	Apply GUI translation (§4), present to user
Tool call/result	Process internally, don't forward
heartbeat / empty data:	Keep waiting. Every 2 min: "⏳ Still working..."
Stream closes	Process final response

~30% of editing operations return no text in the SSE stream. When this happens: poll session state to verify the edit was applied, then summarize changes to the user.

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

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

Tips and Tricks

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

Common Workflows

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