Image To Video Creator Ai

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

Security Scan

The skill's instructions mostly match an image→video service (it only needs a single API token and uploads images to a remote renderer), but the package has no provenance, an unknown backend domain, and small metadata inconsistencies that warrant caution before installing.

Purpose & Capability

The name/description (convert images to MP4) aligns with the SKILL.md which calls a remote rendering API and describes upload, SSE and export flows. Requesting a single NEMO_TOKEN credential is proportional. However, the skill has no listed source/homepage and the registry metadata in the scanned manifest omitted config paths while the SKILL.md frontmatter includes a configPaths entry (~/.config/nemovideo/) — a mild inconsistency in metadata/provenance.

Instruction Scope

Instructions remain within the service's domain: creating/using a NEMO_TOKEN, creating a session, uploading images, streaming SSE, polling render status, and returning a download URL. The agent is instructed to upload local files (multipart -F "files=@/path"), which is expected for this skill but means user images are transmitted to the external API. The SKILL.md does not ask the agent to read unrelated system files, but it does reference a config path in metadata that is not otherwise used in the instructions.

Install Mechanism

Instruction-only skill with no install spec and no code files — lowest installation risk. Nothing will be written to disk by an installer step. The runtime instructions will, however, cause outbound network calls to the described API.

Credentials

Only one environment variable (NEMO_TOKEN) is required and declared as primaryEnv, which is appropriate for an API-backed renderer. The SKILL.md also describes generating an anonymous token via API if no NEMO_TOKEN is present. The frontmatter's configPaths claim (~/.config/nemovideo/) is not reflected in the registry 'Requirements' listing and is not necessary to the documented flows — this mismatch should be clarified.

Persistence & Privilege

always is false and there is no install step that modifies other skills or system-wide settings. The skill runs as an instruction-only integration and does not request permanent elevated presence.

What to consider before installing

Before installing, consider the following: (1) provenance — this skill has no source repo or homepage and calls an external host (mega-api-prod.nemovideo.ai); verify that domain and the project are legitimate. (2) Privacy — using the skill will upload your images (including any sensitive content) to that external service; review their terms, retention policy, and whether uploads are encrypted in transit and at rest. (3) Credentials — the skill accepts a NEMO_TOKEN; provide a scoped or throwaway token if possible (do not put a long-lived account-wide secret in a global NEMO_TOKEN). (4) Metadata mismatch — ask the publisher to clarify why SKILL.md frontmatter mentions a config path (~/.config/nemovideo/) that is not declared elsewhere. (5) Testing — if you proceed, test with non-sensitive images first and monitor network calls. If the vendor/source cannot be verified or you cannot obtain privacy/retention guarantees, avoid installing or restrict use to disposable tokens and dummy content.

Getting Started

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

Try saying:

• "convert three product photos or a single landscape image into a 1080p MP4"
• "turn these photos into a 30-second video with smooth transitions and background music"
• "converting still images into shareable videos for social media for marketers, social media creators, small business owners"

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 Creator AI — Turn Images into MP4 Videos

Send me your images and describe the result you want. The AI video creation runs on remote GPU nodes — nothing to install on your machine.

A quick example: upload three product photos or a single landscape image, type "turn these photos into a 30-second video with smooth transitions and background music", and you'll get a 1080p MP4 back in roughly 30-60 seconds. All rendering happens server-side.

Worth noting: using high-resolution images produces sharper, more professional-looking output videos.

Matching Input to Actions

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

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

Common Workflows

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

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 and background music" — 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 all social platforms.