Image To Video Generator Unrestricted

Skip the learning curve of professional editing software. Describe what you want — turn this image into a 10-second animated video clip with motion effects —...

Security Scan

The skill's requested access and runtime instructions are largely consistent with an image→video cloud service (it needs a NEMO_TOKEN or will obtain an anonymous token and then call nemovideo.ai APIs); nothing in the instructions suggests it will do unrelated or hidden actions, but there are small metadata inconsistencies and no public source/homepage to verify the backend.

Purpose & Capability

The skill claims to convert images to short videos and all declared requirements (NEMO_TOKEN) and API calls in SKILL.md align with that purpose. Minor inconsistency: registry metadata listed 'Required config paths: none' while the skill frontmatter declares a configPath (~/.config/nemovideo/). This is likely benign but should be clarified.

Instruction Scope

Runtime instructions stay within the image→video domain: session creation, SSE for edits, uploads, render polling and exports. The skill also instructs reading its own YAML frontmatter and detecting install paths (~/.clawhub/, ~/.cursor/skills/) to set X-Skill-Platform — reading the install path is extraneous to core functionality but not clearly dangerous. Instructions explicitly prohibit exposing tokens or raw API output.

Install Mechanism

No install spec and no code files (instruction-only). That minimizes on-disk writes and arbitrary code installs — lowest-risk install mechanism.

Credentials

Only NEMO_TOKEN is declared as required (primaryEnv). The skill will acquire an anonymous token itself if NEMO_TOKEN is absent, which is coherent for a service offering anonymous trials. The frontmatter's mention of a config path (~/.config/nemovideo/) conflicts with registry 'none' entry — reading that path could expose local config if present; this should be justified or removed.

Persistence & Privilege

Skill is not always-enabled and uses normal model invocation. It stores session tokens/ids for the session lifecycle (expected). It does not request system-wide or cross-skill configuration changes.

Assessment

This skill appears to do what it says: it will call a nemovideo.ai backend to convert uploaded images into short videos and either use a provided NEMO_TOKEN or obtain a short-lived anonymous token for you. Before installing, consider: (1) Privacy — images are uploaded to a third-party cloud (verify you’re comfortable uploading any proprietary images). (2) Trust and verification — the skill has no public homepage/source; confirm you trust the backend domain (mega-api-prod.nemovideo.ai) and the skill owner. (3) Config-path ambiguity — the skill's frontmatter references ~/.config/nemovideo/ (potentially reading local config) although the registry listed no required config paths; ask the author to clarify why that path is needed. If you need higher assurance, request the skill's source code or a privacy/terms link and verify the backend operator and token handling policy.

Getting Started

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

Try saying:

• "convert my still images"
• "export 1080p MP4"
• "turn this image into a 10-second"

Quick Start Setup

This skill connects to a cloud processing backend. On first use, set up the connection automatically and let the user know ("Connecting...").

Token check: Look for NEMO_TOKEN in the environment. If found, skip to session creation. Otherwise:

• Generate a UUID as client identifier
• POST https://mega-api-prod.nemovideo.ai/api/auth/anonymous-token with X-Client-Id header
• Extract data.token from the response — this is your NEMO_TOKEN (100 free credits, 7-day expiry)

Session: POST https://mega-api-prod.nemovideo.ai/api/tasks/me/with-session/nemo_agent with Bearer auth and body {"task_name":"project"}. Keep the returned session_id for all operations.

Let the user know with a brief "Ready!" when setup is complete. Don't expose tokens or raw API output.

Image to Video Generator Unrestricted — 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 a single product photo or illustrated scene, ask for turn this image into a 10-second animated video clip with motion effects, and about 30-90 seconds later you've got a MP4 file ready to download. The whole thing runs at 1080p by default.

One thing worth knowing — high-contrast images with clear subjects produce smoother motion output.

Matching Input to Actions

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

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

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

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

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)

Common Workflows

Quick edit: Upload → "turn this image into a 10-second animated video clip with motion effects" → Download MP4. Takes 30-90 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 with motion effects" — concrete instructions get better results.

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

Export as MP4 for widest compatibility across social platforms and devices.