Image To Video Editor Ai

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

Security Scan

The skill's instructions mostly match its stated purpose (converting images to videos) but contain a few inconsistencies and minor scope-creep (automatic anonymous token retrieval, filesystem checks for install paths, and a metadata/config-path mismatch) that you should understand before enabling it.

Purpose & Capability

The name/description (image→video) aligns with the runtime instructions and required NEMO_TOKEN credential. However, the skill's YAML frontmatter embeds a configPaths value (~/.config/nemovideo/) even though the registry metadata declared no required config paths — that's an internal inconsistency to be aware of.

Instruction Scope

SKILL.md instructs the agent to upload user images and to call the nemovideo API endpoints (session, SSE, upload, export), which is expected. It also instructs the agent to: (a) automatically obtain an anonymous token by POSTing to an external endpoint if NEMO_TOKEN is absent, and (b) inspect the filesystem (check for ~/.clawhub/ and ~/.cursor/skills/ and read the skill's frontmatter) to set attribution headers. Those filesystem checks and automatic anonymous-token acquisition are beyond simple 'convert images' instructions and are scope creep worth noting.

Install Mechanism

There is no install spec and no code files (instruction-only), which is the lowest-risk install model — nothing is written to disk by an installer.

Credentials

The skill only requests a single credential (NEMO_TOKEN), which is appropriate for a cloud-backend media service. It also instructs obtaining an anonymous token automatically if none is present; this behaviour means the agent will contact an external API and produce/use a token on your behalf. The YAML also mentions a config path (~/.config/nemovideo/) that was not declared in registry metadata — a small mismatch.

Persistence & Privilege

The skill is not always-enabled and does not request elevated agent privileges. It describes per-session tokens and ephemeral render jobs; there is no instruction to persistently modify other skills or system-wide config.

What to consider before installing

What to consider before installing: - The skill does what it says (uploads images, calls a cloud render API) but it will make network requests to https://mega-api-prod.nemovideo.ai and may auto-create an anonymous token if you don't provide NEMO_TOKEN. Decide whether you trust that external domain and its privacy policy. - The SKILL.md instructs the agent to check for certain folders in your home (~/.clawhub/, ~/.cursor/skills/) to build attribution headers — this requires simple filesystem reads (presence checks). If you prefer the agent not touch your home directory, do not install or ask the author to remove that behavior. - There's a small metadata inconsistency: the skill's frontmatter mentions a config path (~/.config/nemovideo/) even though registry metadata lists no config paths. That could be harmless but worth clarifying with the publisher. - If you accept the risk: provide a scoped NEMO_TOKEN (not a high-privilege credential), and test with non-sensitive images first. If you are unsure, do not enable the skill or ask the publisher for an integrity statement and a privacy/terms URL for nemovideo.ai.

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 five product photos in JPG format into a 1080p MP4"
• "turn these images into a 30-second video with transitions and background music"
• "turning static images into shareable videos for social media creators"

Getting Connected

Before handling any user request, establish a connection to the backend API. Show a brief status like "Connecting...".

If NEMO_TOKEN is in the environment, use it directly and create a session. Otherwise, acquire a free starter token:

• Generate a UUID as client identifier
• POST to https://mega-api-prod.nemovideo.ai/api/auth/anonymous-token with the X-Client-Id header
• The response includes a token with 100 free credits valid for 7 days — use it as NEMO_TOKEN

Then create a session by POSTing to https://mega-api-prod.nemovideo.ai/api/tasks/me/with-session/nemo_agent with Bearer authorization and body {"task_name":"project","language":"en"}. The session_id in the response is needed for all following requests.

Tell the user you're ready. Keep the technical details out of the chat.

Image to Video Editor AI — 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 five product photos in JPG format, ask for turn these images into a 30-second 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 images with similar aspect ratios produces smoother transitions.

Matching Input to Actions

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

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

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

Every API call needs Authorization: Bearer <NEMO_TOKEN> plus the three attribution headers above. If any header is missing, exports return 402.

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)

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

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

Common Workflows

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

Tips and Tricks

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