convert images into animated video clips with this skill. Works with JPG, PNG, WEBP, HEIC files up to 200MB. TikTok creators use it for turning still photos...
---
name: ai-image-to-video-effect
version: "1.0.0"
displayName: "AI Image to Video Effect β Animate Images into Video Clips"
description: >
convert images into animated video clips with this skill. Works with JPG, PNG, WEBP, HEIC files up to 200MB. TikTok creators use it for turning still photos into motion videos for social media β processing takes 20-40 seconds on cloud GPUs and you get 1080p MP4 files.
metadata: {"openclaw": {"emoji": "ποΈ", "requires": {"env": ["NEMO_TOKEN"], "configPaths": ["~/.config/nemovideo/"]}, "primaryEnv": "NEMO_TOKEN", "variant": "greeting_v2"}}
---
## Getting Started
> Ready when you are. Drop your images here or describe what you want to make.
**Try saying:**
- "convert a single product photo or portrait image into a 1080p MP4"
- "animate this image with a cinematic zoom and motion effect"
- "turning still photos into motion videos for social media for TikTok creators"
### 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.
# AI Image to Video Effect β Animate Images into Video Clips
Send me your 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 portrait image, type "animate this image with a cinematic zoom and motion effect", and you'll get a 1080p MP4 back in roughly 20-40 seconds. All rendering happens server-side.
Worth noting: high-contrast images with clear subjects produce the most noticeable motion effects.
## Matching Input to Actions
User prompts referencing ai image to video effect, 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.
Headers are derived from this file's YAML frontmatter. `X-Skill-Source` is `ai-image-to-video-effect`, `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`).
**All requests** must include: `Authorization: Bearer <NEMO_TOKEN>`, `X-Skill-Source`, `X-Skill-Version`, `X-Skill-Platform`. Missing attribution headers will cause export to fail with 402.
**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)
```
### 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.
### 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
## Common Workflows
**Quick edit**: Upload β "animate this image with a cinematic zoom and motion effect" β Download MP4. Takes 20-40 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 "animate this image with a cinematic zoom and motion effect" β 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.
don't have the plugin yet? install it then click "run inline in claude" again.