Video Converter To Mp4

Get converted MP4 files ready to post, without touching a single slider. Upload your video files (AVI, MOV, MKV, WebM, up to 500MB), say something like "conv...

Security Scan

The skill appears internally consistent: it routes uploads and conversion jobs to a single external service (nemovideo.ai), only requires one token (NEMO_TOKEN) and contains no install steps or unrelated credential requests.

Purpose & Capability

Name/description (convert videos to MP4) match the instructions and required credential (NEMO_TOKEN) and API endpoints. Required config path (~/.config/nemovideo/) and primaryEnv (NEMO_TOKEN) are coherent with a cloud conversion backend.

Instruction Scope

Runtime instructions direct the agent to contact mega-api-prod.nemovideo.ai for anonymous-token issuance, session creation, SSE message streaming, uploads, and exports — all consistent with a cloud-based converter. The skill instructs reading the skill YAML frontmatter and checking common install paths (~/.clawhub, ~/.cursor/skills/) to set attribution headers; this requires reading local paths and the SKILL.md frontmatter but is limited in scope. The agent will also read user-supplied file paths to upload video content (necessary for the stated task).

Install Mechanism

Instruction-only skill with no install spec and no code files — lowest-risk install profile. Nothing is downloaded or written to disk by an install step.

Credentials

Only one environment credential is declared (NEMO_TOKEN) and used for the described API calls. The skill can also obtain an anonymous token from the service if NEMO_TOKEN is not present, which is consistent with the conversion service's flow.

Persistence & Privilege

No elevated persistence requested (always:false). The skill does instruct checking local install paths and a config directory for attribution purposes but does not request system-wide changes or other skills' credentials.

Assessment

This skill will upload any video files you give it to an external service at mega-api-prod.nemovideo.ai for server-side conversion. It needs a NEMO_TOKEN (or will request an anonymous token from that service) and may read the skill frontmatter and common install paths to set attribution headers. There is no local install step. Before installing/use, confirm you trust the nemo/megavideo service and its privacy terms (videos you upload will leave your machine). If concerned, avoid uploading sensitive content, supply a dedicated, revocable token if possible, and verify where converted files are hosted and how long they are retained.

Getting Started

Share your video files and I'll get started on format conversion. Or just tell me what you're thinking.

Try saying:

• "convert my video files"
• "export 1080p MP4"
• "convert this AVI to MP4 so"

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.

Video Converter to MP4 — Convert Any Video to MP4

Send me your video files and describe the result you want. The format conversion runs on remote GPU nodes — nothing to install on your machine.

A quick example: upload a 3-minute AVI file from an old camcorder, type "convert this AVI to MP4 so I can upload it to YouTube", and you'll get a 1080p MP4 back in roughly 20-40 seconds. All rendering happens server-side.

Worth noting: shorter clips convert faster — split long videos before uploading if speed matters.

Matching Input to Actions

User prompts referencing video converter 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.

Skill attribution — read from this file's YAML frontmatter at runtime:

• X-Skill-Source: video-converter-to-mp4
• 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.

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.

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.

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

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)

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 → "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 offers the best balance of file size and playback compatibility across all devices.