Ai Image To Video Mod

Get animated video clips ready to post, without touching a single slider. Upload your still images (JPG, PNG, WEBP, HEIC, up to 200MB), say something like "t...

Security Scan

The skill's behavior mostly matches its stated purpose (converting images to short videos), but it will automatically make network requests, obtain/store session tokens, and references a config path that is not declared in the registry metadata, so you should review where data and tokens are sent and stored before using it.

Purpose & Capability

The skill's name and description (image → video conversion) match the runtime instructions (upload images, request render, download MP4). Requesting a NEMO_TOKEN credential is consistent with calling a remote rendering API. However, the SKILL.md frontmatter references a config path (~/.config/nemovideo/) that is not listed in the registry metadata—an inconsistency that deserves attention.

Instruction Scope

Instructions direct the agent to automatically connect to a remote backend on first use (including generating/obtaining an anonymous token), upload user images to a third-party API, create and store session IDs, and poll/render jobs. The skill instructs not to display raw tokens but gives no explicit secure-storage guidance. Automatic outbound network activity and remote storage/processing of uploaded files are privacy-sensitive and broader than a purely local helper.

Install Mechanism

No install spec or code files — instruction-only skill — so nothing is written to disk by an installer. This minimizes install-time risk.

Credentials

The skill only declares one credential (NEMO_TOKEN), which is proportionate for calling the remote API. But the SKILL.md also references storing state/config and a config path (~/.config/nemovideo/) that was not declared in the registry metadata; this mismatch could mean the skill will read/write files outside what was advertised.

Persistence & Privilege

always is false and the skill does not request elevated agent privileges. It does instruct the agent to store session IDs/tokens for ongoing requests and may write config under a user path (per frontmatter). That persistence is expected for session-based APIs but you should confirm where session data is stored and how long tokens remain valid.

What to consider before installing

This skill will upload your images and make automatic network requests to https://mega-api-prod.nemovideo.ai, including creating or using a NEMO_TOKEN and storing session state. Before installing: (1) Confirm you trust the external service and accept that uploaded images will be processed remotely. (2) Verify how/where tokens and session IDs will be stored (the SKILL.md mentions ~/.config/nemovideo/ but the registry metadata omitted it). (3) If you want to limit exposure, provide a limited or ephemeral NEMO_TOKEN (or ensure the skill uses the anonymous 7‑day token flow instead of any sensitive credential). (4) Ask the publisher for a source/homepage or privacy/terms documentation (none is provided). (5) Avoid uploading sensitive images until you verify retention and deletion policies. The main red flags are the absent source/homepage and the metadata mismatch; these justify caution rather than immediate rejection.

Getting Started

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

Try saying:

• "convert a single product photo or illustrated scene into a 1080p MP4"
• "turn this image into a 10-second animated video clip"
• "converting static images into short animated videos for content creators"

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.

AI Image to Video Mod — Convert Images Into Video Clips

Send me your still 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 a single product photo or illustrated scene, type "turn this image into a 10-second animated video clip", and you'll get a 1080p MP4 back in roughly 30-60 seconds. All rendering happens server-side.

Worth noting: images with clear subjects and simple backgrounds produce smoother motion results.

Matching Input to Actions

User prompts referencing ai image to video mod, 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	ai-image-to-video-mod
X-Skill-Version	frontmatter version
X-Skill-Platform	auto-detect: clawhub / cursor / unknown from install path

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

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.

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

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 this image into a 10-second animated video clip" → 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 this image into a 10-second animated video clip" — 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 social platforms.