Skills free-video-converter
git clone https://github.com/openclaw/skills
T=$(mktemp -d) && git clone --depth=1 https://github.com/openclaw/skills "$T" && mkdir -p ~/.claude/skills && cp -r "$T/skills/bwbernardweston18/free-video-converter" ~/.claude/skills/openclaw-skills-free-video-converter && rm -rf "$T"
T=$(mktemp -d) && git clone --depth=1 https://github.com/openclaw/skills "$T" && mkdir -p ~/.openclaw/skills && cp -r "$T/skills/bwbernardweston18/free-video-converter" ~/.openclaw/skills/openclaw-skills-free-video-converter && rm -rf "$T"
skills/bwbernardweston18/free-video-converter/SKILL.mdGetting Started
Got video files to work with? Send it over and tell me what you need — I'll take care of the format conversion.
Try saying:
- "convert a 3-minute AVI file from an old camcorder into a 1080p MP4"
- "convert this AVI to MP4 so I can upload it to YouTube"
- "converting old or incompatible video formats to MP4 for everyday users and 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.
- Obtain a free token: Generate a random UUID as client identifier. POST to
with headerhttps://mega-api-prod.nemovideo.ai/api/auth/anonymous-token
set to that UUID. The responseX-Client-Id
is your NEMO_TOKEN — 100 free credits, valid 7 days.data.token - Create a session: POST to
withhttps://mega-api-prod.nemovideo.ai/api/tasks/me/with-session/nemo_agent
,Authorization: Bearer <token>
, and bodyContent-Type: application/json
. Store the returned{"task_name":"project","language":"<detected>"}
for all subsequent requests.session_id
Keep setup communication brief. Don't display raw API responses or token values to the user.
Free Video Converter — Convert Any Video to MP4
Drop your video files in the chat and tell me what you need. I'll handle the format conversion on cloud GPUs — you don't need anything installed locally.
Here's a typical use: you send a a 3-minute AVI file from an old camcorder, ask for convert this AVI to MP4 so I can upload it to YouTube, and about 20-40 seconds later you've got a MP4 file ready to download. The whole thing runs at 1080p by default.
One thing worth knowing — shorter clips under 2 minutes convert in under 30 seconds.
Matching Input to Actions
User prompts referencing free video converter, 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.
Include
Authorization: Bearer <NEMO_TOKEN> and all attribution headers on every request — omitting them triggers a 402 on export.
Skill attribution — read from this file's YAML frontmatter at runtime:
:X-Skill-Sourcefree-video-converter
: from frontmatterX-Skill-Versionversion
: detect from install path (X-Skill-Platform
→~/.clawhub/
,clawhub
→~/.cursor/skills/
, elsecursor
)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
— success, continue normally0
— token expired or invalid; re-acquire via1001/api/auth/anonymous-token
— session not found; create a new one1002
— out of credits; anonymous users get a registration link with2001
, registered users top up?bind=<id>
— unsupported file type; show accepted formats4001
— file too large; suggest compressing or trimming4002
— missing400
; generate one and retryX-Client-Id
— free plan export blocked; not a credit issue, subscription tier402
— rate limited; wait 30s and retry once429
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 |
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.
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 → "convert this AVI 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.
Tips and Tricks
The backend processes faster when you're specific. Instead of "make it look better", try "convert this AVI to MP4 so I can upload it to YouTube" — concrete instructions get better results.
Max file size is 500MB. Stick to AVI, MOV, MKV, WebM for the smoothest experience.
MP4 with H.264 codec gives the best balance of quality and file size.