Image To Video Models
by @susan4731-wilfordf
Get animated video clips ready to post, without touching a single slider. Upload your still images (JPG, PNG, WEBP, HEIC, up to 50MB), say something like "an...
clawhub install image-to-video-modelsπ About This Skill
name: image-to-video-models version: "1.0.0" displayName: "Image to Video Models β Convert Images into Video Clips" description: > Get animated video clips ready to post, without touching a single slider. Upload your still images (JPG, PNG, WEBP, HEIC, up to 50MB), say something like "animate this image into a 5-second video with smooth motion", and download 1080p MP4 when it's done. Built for marketers, social media creators, designers who move fast and want to bring still images to life without manual animation skills. metadata: {"openclaw": {"emoji": "πΌοΈ", "requires": {"env": ["NEMO_TOKEN"], "configPaths": ["~/.config/nemovideo/"]}, "primaryEnv": "NEMO_TOKEN", "variant": "greeting_v2"}}
Getting Started
> Send me your still images and I'll handle the AI video generation. Or just describe what you're after.
Try saying:
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:
https://mega-api-prod.nemovideo.ai/api/auth/anonymous-token with X-Client-Id headerdata.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 Models β Convert Images into Video Clips
Drop your still images in the chat and tell me what you need. I'll handle the AI video generation on cloud GPUs β you don't need anything installed locally.
Here's a typical use: you send a a single product photo or landscape image, ask for animate this image into a 5-second video with smooth motion, 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 the most natural-looking motion.
Matching Input to Actions
User prompts referencing image to video models, 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":". 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/ β 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/ β current draft and media info.
6. Export β POST /api/render/proxy/lambda with render ID and draft JSON. Poll GET /api/render/proxy/lambda/ every 30s for completed status and download URL.
Formats: mp4, mov, avi, webm, mkv, jpg, png, gif, webp, mp3, wav, m4a, aac.
Three attribution headers are required on every request and must match this file's frontmatter:
| Header | Value |
|--------|-------|
| X-Skill-Source | image-to-video-models |
| X-Skill-Version | frontmatter version |
| X-Skill-Platform | auto-detect: clawhub / cursor / unknown from install path |
Include Authorization: Bearer and all attribution headers on every request β omitting them triggers a 402 on export.
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)
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.
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= (get 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 |
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 with smooth motion" β concrete instructions get better results.
Max file size is 50MB. Stick to JPG, PNG, WEBP, HEIC for the smoothest experience.
Use PNG for images with transparency to preserve edge quality before conversion.
Common Workflows
Quick edit: Upload β "animate this image into a 5-second video with smooth motion" β 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.
π‘ Examples
> Send me your still images and I'll handle the AI video generation. Or just describe what you're after.
Try saying:
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:
https://mega-api-prod.nemovideo.ai/api/auth/anonymous-token with X-Client-Id headerdata.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 Models β Convert Images into Video Clips
Drop your still images in the chat and tell me what you need. I'll handle the AI video generation on cloud GPUs β you don't need anything installed locally.
Here's a typical use: you send a a single product photo or landscape image, ask for animate this image into a 5-second video with smooth motion, 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 the most natural-looking motion.