Converter To Mp4

convert video files into converted MP4 files with this skill. Works with AVI, MOV, MKV, WebM files up to 500MB. content creators use it for converting video...

Security Scan

The skill's requests and runtime instructions are consistent with a cloud-based video-to-MP4 converter: it asks for one service token, describes API calls to a rendering backend, and has no install or unrelated credential demands.

Purpose & Capability

The name/description (convert video → MP4) matches the SKILL.md instructions (create session, upload video, request render, download URL). Requiring NEMO_TOKEN and calls to mega-api-prod.nemovideo.ai are coherent with remote rendering.

Instruction Scope

Runtime instructions only direct the agent to obtain or use an API token, create sessions, upload files, use SSE for streaming responses, poll render status, and return download URLs. They do not instruct reading unrelated system files, other environment variables, or exfiltrating data beyond the rendering service. The skill explicitly instructs not to print tokens or raw JSON.

Install Mechanism

There is no install specification and no code files — the skill is instruction-only, which minimizes disk-writing/install risk.

Credentials

The skill only requires one credential (NEMO_TOKEN), which is proportional for a third‑party API. One minor inconsistency: the SKILL.md frontmatter references a config path (~/.config/nemovideo/) while the registry metadata listed 'Required config paths: none' — this should be clarified (the skill may expect to read or write a per-user config directory). Otherwise no unrelated secrets are requested.

Persistence & Privilege

always:false (not force-included). Model invocation is allowed (normal). The skill does not request to modify other skills or system-wide configuration in its instructions.

Assessment

This skill sends whatever video files you provide to a third-party rendering service (mega-api-prod.nemovideo.ai) and needs a NEMO_TOKEN (or it can create a 7-day anonymous token). Before using it, consider: 1) Do you trust the remote service to store/process your videos (privacy/confidentiality)? 2) If you already have a NEMO_TOKEN, this skill will use it—avoid supplying a token that authorizes more than you intend. 3) Clarify the config-path mention (~/.config/nemovideo/) with the author—it could read or write a local config directory. 4) No local install is required, but the agent will upload files you provide; avoid uploading sensitive content unless you’re comfortable with the service’s policies.

Getting Started

Share your video files and I'll get started on video 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"

Automatic Setup

On first interaction, connect to the processing API before doing anything else. Show a brief status like "Setting things up...".

Token: If NEMO_TOKEN environment variable is already set, use it and skip to Session below.

Free token: Generate a UUID as client identifier, then POST to https://mega-api-prod.nemovideo.ai/api/auth/anonymous-token with header X-Client-Id: <uuid>. The response field data.token becomes your NEMO_TOKEN (100 credits, 7-day expiry).

Session: POST to https://mega-api-prod.nemovideo.ai/api/tasks/me/with-session/nemo_agent with Bearer auth and body {"task_name":"project"}. Save session_id from the response.

Confirm to the user you're connected and ready. Don't print tokens or raw JSON.

Converter to MP4 — Convert Any Video to MP4

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

A quick example: upload a 3-minute AVI file from a screen recorder, 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 you need quick results.

Matching Input to Actions

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

Three attribution headers are required on every request and must match this file's frontmatter:

Header	Value
X-Skill-Source	converter-to-mp4
X-Skill-Version	frontmatter version
X-Skill-Platform	auto-detect: clawhub / cursor / unknown from install path

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.

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 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)

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.

H.264 codec gives the best balance of quality and file size for MP4 output.