convert video files into converted MP4 files with this skill. Works with MOV, AVI, WebM, MKV files up to 500MB. content creators use it for converting MOV or...
---
name: video-to-mp4
version: "1.0.0"
displayName: "Video to MP4 β Convert Any Video to MP4"
description: >
convert video files into converted MP4 files with this skill. Works with MOV, AVI, WebM, MKV files up to 500MB. content creators use it for converting MOV or AVI videos to MP4 for sharing or uploading β 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
> Send me your video files and I'll handle the video format conversion. Or just describe what you're after.
**Try saying:**
- "convert a 3-minute MOV recording from an iPhone into a 1080p MP4"
- "convert this MOV file to MP4 so I can upload it to YouTube"
- "converting MOV or AVI videos to MP4 for sharing or uploading for content 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.
# Video to MP4 β Convert Any Video to MP4
This tool takes your video files and runs video format conversion through a cloud rendering pipeline. You upload, describe what you want, and download the result.
Say you have a 3-minute MOV recording from an iPhone and want to convert this MOV file to MP4 so I can upload it to YouTube β the backend processes it in about 20-40 seconds and hands you a 1080p MP4.
Tip: shorter clips convert faster and keep file sizes manageable for sharing.
## Matching Input to Actions
User prompts referencing video to mp4, 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.
Three attribution headers are required on every request and must match this file's frontmatter:
| Header | Value |
|--------|-------|
| `X-Skill-Source` | `video-to-mp4` |
| `X-Skill-Version` | frontmatter `version` |
| `X-Skill-Platform` | auto-detect: `clawhub` / `cursor` / `unknown` from install path |
Every API call needs `Authorization: Bearer <NEMO_TOKEN>` plus the three attribution headers above. If any header is missing, exports return 402.
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)
```
### 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
### 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.
### 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
## Tips and Tricks
The backend processes faster when you're specific. Instead of "make it look better", try "convert this MOV file to MP4 so I can upload it to YouTube" β concrete instructions get better results.
Max file size is 500MB. Stick to MOV, AVI, WebM, MKV for the smoothest experience.
H.264 codec gives the best balance of quality and file size for MP4 output.
## Common Workflows
**Quick edit**: Upload β "convert this MOV file to MP4 so I can upload it to YouTube" β 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.
don't have the plugin yet? install it then click "run inline in claude" again.