Image To Video Comfyui

Skip the learning curve of professional editing software. Describe what you want — animate this image into a 5-second video clip using ComfyUI workflow — and...

Security Scan

The skill's requirements and runtime instructions are largely consistent with a remote image->video service (it needs a NEMO_TOKEN and uploads images to nemovideo.ai), with a small metadata mismatch and a couple of operational details you should be aware of before installing.

Purpose & Capability

Name/description claim remote ComfyUI-based video generation; the skill only requires a single service credential (NEMO_TOKEN) and its API endpoints are all for the stated rendering backend. Requiring a token is proportionate to the described functionality.

Instruction Scope

SKILL.md instructs the agent to upload user images, create/check sessions, poll render jobs, and obtain an anonymous token automatically if NEMO_TOKEN is not set. Those actions are within the stated purpose. Note: the skill also tells the agent to 'detect install path' to set an X-Skill-Platform header and to keep token values hidden from the user — the install-path detection implies the agent may check well-known paths (~/.clawhub/, ~/.cursor/skills/) which touches the local filesystem beyond just reading user-supplied image file paths.

Install Mechanism

No install spec or third-party downloads — instruction-only skill. Nothing is written to disk by an installer, so install risk is low.

Credentials

The only declared required environment variable is NEMO_TOKEN which matches the API usage. However, the SKILL.md frontmatter lists a configPaths entry (~/.config/nemovideo/) while the registry metadata summary provided earlier said no required config paths — this is an inconsistency worth clarifying. The skill also instructs creating an anonymous token automatically if no NEMO_TOKEN is present, which means it will call the external API and retain session_id/token state for subsequent calls.

Persistence & Privilege

always:false and no instructions to modify other skills or system-wide settings. The skill asks the agent to store session_id/token for the session, which is expected for an API-backed workflow.

Assessment

This skill appears to do what it says: it uploads images to a remote GPU-backed service (mega-api-prod.nemovideo.ai) and returns rendered videos, requiring a NEMO_TOKEN. Before installing, consider: (1) privacy — your images will be sent to an external service (don’t upload sensitive content unless you trust the provider); (2) token handling — the skill will create and use an anonymous token for you if none is provided (valid 7 days); (3) minor metadata mismatch — SKILL.md references a config path (~/.config/nemovideo/) that wasn't listed in the registry metadata, so ask the publisher whether the skill will read/write that path; (4) verify you trust the external domain (mega-api-prod.nemovideo.ai) because it will receive your files and generate tokens. If you need higher assurance, request an explicit privacy policy or service homepage, and prefer providing your own NEMO_TOKEN rather than letting the skill create one automatically.

Getting Started

Share your static images and I'll get started on AI video generation. Or just tell me what you're thinking.

Try saying:

• "convert my static images"
• "export 1080p MP4"
• "animate this image into a 5-second"

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.

Image to Video ComfyUI — Animate Images Into Video Clips

Send me your static images and describe the result you want. The AI video generation runs on remote GPU nodes — nothing to install on your machine.

A quick example: upload a single product photo or illustrated scene, type "animate this image into a 5-second video clip using ComfyUI workflow", and you'll get a 1080p MP4 back in roughly 1-3 minutes. All rendering happens server-side.

Worth noting: higher resolution input images produce smoother motion and cleaner output frames.

Matching Input to Actions

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

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

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

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.

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

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

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.

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)

Tips and Tricks

The backend processes faster when you're specific. Instead of "make it look better", try "animate this image into a 5-second video clip using ComfyUI workflow" — concrete instructions get better results.

Max file size is 200MB. Stick to PNG, JPG, WEBP, BMP for the smoothest experience.

Use PNG input images for best quality since they are lossless before generation.

Common Workflows

Quick edit: Upload → "animate this image into a 5-second video clip using ComfyUI workflow" → Download MP4. Takes 1-3 minutes 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.