Ai Image To Video Converter

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

Security Scan

The skill's requests and runtime instructions are consistent with an image→video cloud service: it needs a single service token, talks to a nemo video API, and has no install steps or unrelated credential requests.

Purpose & Capability

The name/description (convert images to short videos) matches the declared requirement (NEMO_TOKEN) and the SKILL.md REST endpoints for uploads, SSE, render/export, and credits. One minor inconsistency: the SKILL.md frontmatter lists a config path (~/.config/nemovideo/) while the registry metadata shown to you said no required config paths — this is a small metadata mismatch but doesn't change the core functionality.

Instruction Scope

Runtime instructions are focused on creating a session, uploading files, driving SSE for edits, polling export status, and returning a download URL. The skill instructs the agent to read its own YAML frontmatter and check typical install paths to set an attribution header (X-Skill-Platform) — that requires only reading expected skill/install paths. There are no instructions to read unrelated system files or additional environment variables. It does instruct the agent not to print tokens/raw JSON.

Install Mechanism

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

Credentials

Only one environment variable is required (NEMO_TOKEN) and it is directly used as the Bearer token for the described API. The skill also documents a flow to obtain a short-lived anonymous token from the provider if NEMO_TOKEN is not present. Aside from the frontmatter-configPath mention (~/.config/nemovideo/), there are no additional secret or unrelated credential requests.

Persistence & Privilege

The skill is not always-enabled and uses the platform default (agent-invocable/autonomous allowed). It does not request elevated platform privileges or to modify other skills. It asks to save session_id for ongoing jobs, which is expected for a cloud render workflow.

Assessment

What to consider before installing: this skill will upload any images you give it to mega-api-prod.nemovideo.ai and requires a NEMO_TOKEN (you can supply your own paid token or let the skill request an anonymous short-lived token). Only provide images you are comfortable sending to a third party (avoid sensitive personal or proprietary images). Confirm you trust the nemovideo.ai domain and its privacy/storage policy. Note the small metadata mismatch (SKILL.md references a config path) — that suggests the skill might read or store config under ~/.config/nemovideo/ if implemented; verify where tokens/sessions are stored if you care about persistence. If you want higher assurance, ask the publisher for a homepage/source repo or a privacy policy, or run uploads with synthetic test images first. If the skill later requests additional env vars, arbitrary downloads, or file-system access beyond the listed paths, stop and re-evaluate.

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"
• "convert these images into a smooth 30-second video with transitions"
• "turning static images into shareable videos for marketers, social media creators"

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.

AI Image to Video Converter — Convert Images into 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 convert these images into a smooth 30-second video with transitions — the backend processes it in about 30-60 seconds and hands you a 1080p MP4.

Tip: using images with similar aspect ratios produces smoother transitions.

Matching Input to Actions

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

Skill attribution — read from this file's YAML frontmatter at runtime:

• X-Skill-Source: ai-image-to-video-converter
• X-Skill-Version: from frontmatter version
• X-Skill-Platform: detect from install path (~/.clawhub/ → clawhub, ~/.cursor/skills/ → cursor, else unknown)

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.

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 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 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 "convert these images into a smooth 30-second video with 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.

Common Workflows

Quick edit: Upload → "convert these images into a smooth 30-second 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.