Ai Image To Video Com

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 declared requirements and runtime instructions are consistent with an image→video cloud-rendering service: it only needs (and uses) an API token and uploads images to the vendor API; nothing in the package attempts to access unrelated credentials or install code locally.

Purpose & Capability

The skill is an image-to-video frontend and requests a single service credential (NEMO_TOKEN), which is appropriate. There is a minor inconsistency: the registry metadata at the top indicated no required config paths, but the SKILL.md frontmatter lists a config path (~/.config/nemovideo/). That discrepancy should be clarified, though either option could be legitimate (the service may store tokens/config there).

Instruction Scope

SKILL.md instructs the agent to upload user images and communicate with the nemovideo API endpoints (session creation, SSE chat, upload, render/export). It does not instruct reading arbitrary user files, system secrets, or sending unrelated data. It does include a small attribution heuristic that inspects the agent's install path to set an X-Skill-Platform header — this is limited and explains itself in the doc.

Install Mechanism

There is no install spec and no code files; the skill is instruction-only, so nothing is written to disk or downloaded by the skill itself. This is the lowest-risk install model.

Credentials

The only required credential is NEMO_TOKEN (declared as primaryEnv). The SKILL.md also documents an anonymous-token fallback via the service API if no token is provided — this is expected. Aside from a possible config path listed in SKILL.md frontmatter, no additional secrets or unrelated environment variables are requested.

Persistence & Privilege

The skill is not marked always:true, does not request persistent system-wide changes, and does not modify other skills or agent configs. Autonomous invocation is allowed (the platform default) but not combined here with broad credentials or persistence.

Assessment

This skill sends any images you provide to the nemovideo.ai backend and uses a Bearer token (NEMO_TOKEN) if present, otherwise it obtains a short-lived anonymous token from the service. Before installing, consider: (1) Do you trust the nemovideo.ai domain and its privacy policy? Your images (and any text you include) will be uploaded to their cloud GPUs. (2) If you set a persistent NEMO_TOKEN in your environment, the skill will use it — avoid placing unrelated secrets there. (3) The SKILL.md mentions a config path (~/.config/nemovideo/) and an attribution header that may reveal local install path info; if you prefer, do not provide a persistent token and let the skill use the anonymous token flow. If you need stronger assurance, ask the skill author for a privacy/data-retention statement or use a disposable token and avoid uploading sensitive images.

Getting Started

Ready when you are. Drop your still 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 my photo into a smooth animated video with transitions"
• "converting still photos into shareable video content 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.

AI Image to Video — Convert Images into Video Clips

Drop your still 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 three product photos or a single landscape image, ask for turn my photo into a smooth animated video with transitions, 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 — single high-resolution images produce smoother motion output than compressed thumbnails.

Matching Input to Actions

User prompts referencing ai image to video com, 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: ai-image-to-video-com
• X-Skill-Version: from frontmatter version
• X-Skill-Platform: detect from install path (~/.clawhub/ → clawhub, ~/.cursor/skills/ → cursor, else 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 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

Tips and Tricks

The backend processes faster when you're specific. Instead of "make it look better", try "turn my photo into a smooth animated 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 across all social platforms.

Common Workflows

Quick edit: Upload → "turn my photo into a smooth animated 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.