Image To Ai

Skip the learning curve of professional editing software. Describe what you want — turn these images into a short video with transitions and background music...

Security Scan

The skill's requested tokens and API calls are consistent with its stated image→video rendering purpose, but there are a few small metadata/instruction inconsistencies and privacy trade-offs you should understand before using it.

Purpose & Capability

The skill converts images to server-side AI-rendered videos and all runtime instructions describe calling a single external rendering service (mega-api-prod.nemovideo.ai) using a bearer token (NEMO_TOKEN). Requesting a service token is proportionate to the stated purpose.

Instruction Scope

Instructions direct the agent to automatically connect to the remote API on first interaction, upload user images, open sessions, use SSE for streaming responses, and poll export status — all expected for a remote rendering service. They also instruct deriving headers from the YAML frontmatter and detecting install path to set X-Skill-Platform, which implies inspecting local paths/metadata (not strictly necessary for core functionality). The file warns not to print tokens/raw JSON — good practice.

Install Mechanism

This is an instruction-only skill with no install spec or code files, so nothing is written to disk at install time — lowest-risk install mechanism.

Credentials

The only required credential is NEMO_TOKEN, which is appropriate for authenticating to the remote API. SKILL.md metadata references a config path (~/.config/nemovideo/) even though the registry metadata did not list config paths, which is a minor inconsistency. The skill also supports creating an anonymous token automatically if NEMO_TOKEN isn't set.

Persistence & Privilege

always is false and the skill does not request elevated platform-wide privileges. It instructs storing a session_id for job management (expected) but does not instruct modifying other skills or system-wide configurations.

Assessment

This skill sends your images and edit instructions to mega-api-prod.nemovideo.ai for server-side rendering and requires a NEMO_TOKEN (it can also create a short-lived anonymous token). Before installing: 1) Consider privacy — do not upload sensitive images to a third-party service you don't trust. 2) The skill source/homepage is unknown; confirm the domain and service reputation if you plan to use a persistent NEMO_TOKEN tied to your account. 3) Prefer the anonymous-token flow or a disposable account if you only need occasional use. 4) Be aware the SKILL.md mentions a local config path and install-path detection (minor inconsistency); the skill may inspect local metadata/paths for header values but does not install code. 5) If you set NEMO_TOKEN in your environment, treat it like any API key (don't expose it broadly and revoke it if you stop using the skill). If you want higher assurance, ask the publisher for a homepage, privacy policy, and a clear statement of how uploaded media is stored/retained.

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 images into a short video with transitions and background music"
• "turning static images into animated or narrated videos for marketers"

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 AI — Convert Images into AI 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 in JPG format, type "turn these images into a short video with 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 output video frames.

Matching Input to Actions

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

All calls go to https://mega-api-prod.nemovideo.ai. The main endpoints:

1. Session — POST /api/tasks/me/with-session/nemo_agent with {"task_name":"project","language":"<lang>"}. Gives you a session_id.
2. Chat (SSE) — POST /run_sse with session_id and your message in new_message.parts[0].text. Set Accept: text/event-stream. Up to 15 min.
3. Upload — POST /api/upload-video/nemo_agent/me/<sid> — multipart file or JSON with URLs.
4. Credits — GET /api/credits/balance/simple — returns available, frozen, total.
5. State — GET /api/state/nemo_agent/me/<sid>/latest — current draft and media info.
6. Export — POST /api/render/proxy/lambda with render ID and draft JSON. Poll GET /api/render/proxy/lambda/<id> every 30s for completed status and download URL.

Formats: mp4, mov, avi, webm, mkv, jpg, png, gif, webp, mp3, wav, m4a, aac.

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

Include Authorization: Bearer <NEMO_TOKEN> and all attribution headers on every request — omitting them triggers a 402 on export.

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)

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

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.

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 images into a short video with 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.

Common Workflows

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