Image To Video Grok

convert static images into animated video clips with this skill. Works with JPG, PNG, WEBP, GIF files up to 200MB. content creators and marketers use it for...

Security Scan

The skill's declared requirements and runtime instructions mostly match the stated purpose (uploading images and calling a cloud render API), but there are notable inconsistencies and privacy/surprise risks you should be aware of before installing.

Purpose & Capability

The skill's name and description (convert images to short AI videos) align with the API endpoints and actions described (upload, render, export). Requesting a NEMO_TOKEN as the primary credential fits that purpose. However, the SKILL.md also documents an automatic anonymous-token flow (POST to /api/auth/anonymous-token) if NEMO_TOKEN is not present, which conflicts with the registry metadata that lists NEMO_TOKEN as a required environment variable. The presence of a declared config path (~/.config/nemovideo/) is plausible for storing credentials, but the SKILL.md does not clearly explain reading or writing that path.

Instruction Scope

Runtime instructions direct the agent to upload user files (images/audio) to an external domain (mega-api-prod.nemovideo.ai), create sessions, stream SSE responses, poll state, and include attribution headers. Uploading user-provided media to a third-party cloud service is core to the skill but is a privacy/exfiltration risk that should be explicit to users. The guide also instructs generating anonymous tokens and keeping/using them server-side. The instructions require the agent to make network calls to a third-party API and to include installation-detection logic for attribution headers (detecting install path), which implies reading environment or path context. These behaviors are within scope for the stated purpose but raise privacy and transparency concerns.

Install Mechanism

Instruction-only skill with no install spec and no code files — the lowest install risk. Nothing will be written to disk by an installer step from this package itself.

Credentials

The skill declares a single credential (NEMO_TOKEN) which is appropriate for calling the remote API. However, the SKILL.md simultaneously instructs the agent to generate or fetch an anonymous token if NEMO_TOKEN is absent, creating a mismatch between declared required env and actual behavior. The token is a Bearer credential used to authorize uploads and renders, so possession of it allows access to the service and to any jobs and assets tied to the session. The metadata also lists a config path (~/.config/nemovideo/) which could store tokens/config; the instructions don't fully justify or describe use of that path. Overall the number of env vars is reasonable, but the automatic token acquisition and storage behavior merits caution.

Persistence & Privilege

The skill does not request always:true, has no install hooks, and does not attempt to modify other skills or system-wide agent settings. Autonomous invocation is allowed by default but not combined with elevated privileges here.

What to consider before installing

This skill will upload your images and any attached audio to a third-party cloud service (mega-api-prod.nemovideo.ai) for processing and will include an authorization token on every request. The registry metadata says NEMO_TOKEN is required, but the runtime instructions say the agent will automatically obtain a temporary anonymous token if one is not provided — that's an inconsistency you should note. Before installing: (1) decide whether you are comfortable having your media uploaded to an unknown external service; (2) if you want control, set your own NEMO_TOKEN in the agent environment rather than letting the skill obtain an anonymous token; (3) test with non-sensitive images first; (4) ask the publisher for source/homepage and privacy/retention terms (none are provided); and (5) if you need stronger guarantees, avoid enabling autonomous invocation or restrict the skill's use to explicit user-invoked sessions.

Getting Started

Got static 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 a single product photo or illustration into a 1080p MP4"
• "turn this image into a short animated video clip"
• "converting still images into short AI-generated video clips for content creators and marketers"

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 Grok — Convert Images Into Video Clips

Send me your static 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 illustration, type "turn this image into a short animated video clip", and you'll get a 1080p MP4 back in roughly 30-90 seconds. All rendering happens server-side.

Worth noting: high-contrast images with clear subjects produce smoother motion results.

Matching Input to Actions

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

Base URL: https://mega-api-prod.nemovideo.ai

Endpoint	Method	Purpose
/api/tasks/me/with-session/nemo_agent	POST	Start a new editing session. Body: {"task_name":"project","language":"<lang>"}. Returns session_id.
/run_sse	POST	Send a user message. Body includes app_name, session_id, new_message. Stream response with Accept: text/event-stream. Timeout: 15 min.
/api/upload-video/nemo_agent/me/<sid>	POST	Upload a file (multipart) or URL.
/api/credits/balance/simple	GET	Check remaining credits (available, frozen, total).
/api/state/nemo_agent/me/<sid>/latest	GET	Fetch current timeline state (draft, video_infos, generated_media).
/api/render/proxy/lambda	POST	Start export. Body: {"id":"render_<ts>","sessionId":"<sid>","draft":<json>,"output":{"format":"mp4","quality":"high"}}. Poll status every 30s.

Accepted file types: 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-grok
• 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.

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

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.

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)

Common Workflows

Quick edit: Upload → "turn this image into a short animated video clip" → 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 short animated video clip" — concrete instructions get better results.

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

Use PNG images for best quality input when generating video from illustrations.