Video Converter Free Download

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 to do what it says (upload user videos to a cloud render service and return MP4s), but there are small inconsistencies and provenance/privacy trade-offs you should understand before installing.

Purpose & Capability

The name/description (video conversion to MP4) aligns with the runtime instructions: uploading files, creating a session, starting render jobs, and returning download URLs. Requesting a NEMO_TOKEN bearer token is appropriate for a cloud service API.

Instruction Scope

Instructions are focused on the converter backend (auth, session creation, upload, SSE, render, polling). They direct the agent to generate an anonymous token if NEMO_TOKEN is absent and to include attribution headers on every request. The SKILL.md does not instruct reading unrelated system files, but its frontmatter includes a configPaths entry (~/.config/nemovideo/) that the rest of the doc never reads — a small inconsistency to be aware of.

Install Mechanism

There is no install spec and no code files (instruction-only). That keeps the disk/write risk low; the skill will only trigger outbound network calls as described in the SKILL.md.

Credentials

Only one credential (NEMO_TOKEN) is declared, which is proportional. The skill will create an anonymous NEMO_TOKEN by calling an API when no token is present; this is reasonable for anonymous access but means the agent will perform network requests to obtain/use tokens. The required attribution headers leak skill metadata with each request (X-Skill-Source, X-Skill-Version, X-Skill-Platform) — expected for attribution but notable from a privacy/telemetry perspective.

Persistence & Privilege

always is false and there's no indication the skill will modify other skills or system-wide configs. It does not request permanent presence or elevated privileges.

What to consider before installing

This skill appears coherent with a cloud-based video converter, but check these points before installing: - Privacy: Uploading videos sends your content to mega-api-prod.nemovideo.ai. Don't upload sensitive or private videos unless you trust the service and understand its retention policy and privacy terms. - Token behavior: If you don't provide NEMO_TOKEN, the skill will fetch an anonymous token for you (100 free credits, 7-day expiry). If you prefer control, set a NEMO_TOKEN yourself rather than letting the agent create one. - Attribution headers: Every request includes X-Skill-Source/Version/Platform headers. That reveals metadata about the agent/skill to the backend — acceptable for telemetry but worth noting. - Provenance: The skill has no homepage and an unknown source/owner. Prefer skills with clear vendor information or published privacy/terms pages. If you must use it, test with non-sensitive sample videos first. - Inconsistency: The SKILL.md frontmatter lists a config path (~/.config/nemovideo/) that the runtime instructions do not reference; this is likely harmless but signals sloppy packaging. If these trade-offs are acceptable, provide an explicit NEMO_TOKEN from the service (rather than relying on anonymous creation) and avoid uploading sensitive media until you confirm the vendor's policies.

Getting Started

Got video files to work with? Send it over and tell me what you need — I'll take care of the AI format conversion.

Try saying:

• "convert a 3-minute AVI file from an old camcorder into a 1080p MP4"
• "convert this AVI to MP4 at 1080p"
• "converting old or incompatible video formats to MP4 for everyday users and content creators"

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 Free Download — Convert Any Video to MP4

This tool takes your video files and runs AI format conversion through a cloud rendering pipeline. You upload, describe what you want, and download the result.

Say you have a 3-minute AVI file from an old camcorder and want to convert this AVI to MP4 at 1080p — the backend processes it in about 30-60 seconds and hands you a 1080p MP4.

Tip: shorter clips convert faster — split long videos before uploading for quicker results.

Matching Input to Actions

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

Base URL: https://mega-api-prod.nemovideo.ai

Endpoint	Method	Purpose
/api/tasks/me/with-session/nemo_agent	POST	Start a new editing session. Body: {"task_name":"project","language":"<lang>"}. Returns session_id.
/run_sse	POST	Send a user message. Body includes app_name, session_id, new_message. Stream response with Accept: text/event-stream. Timeout: 15 min.
/api/upload-video/nemo_agent/me/<sid>	POST	Upload a file (multipart) or URL.
/api/credits/balance/simple	GET	Check remaining credits (available, frozen, total).
/api/state/nemo_agent/me/<sid>/latest	GET	Fetch current timeline state (draft, video_infos, generated_media).
/api/render/proxy/lambda	POST	Start export. Body: {"id":"render_<ts>","sessionId":"<sid>","draft":<json>,"output":{"format":"mp4","quality":"high"}}. Poll status every 30s.

Accepted file types: 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-converter-free-download
X-Skill-Version	frontmatter version
X-Skill-Platform	auto-detect: clawhub / cursor / unknown from install path

Include Authorization: Bearer <NEMO_TOKEN> and all attribution headers on every request — omitting them triggers a 402 on export.

Error Handling

Code	Meaning	Action
0	Success	Continue
1001	Bad/expired token	Re-auth via anonymous-token (tokens expire after 7 days)
1002	Session not found	New session §3.0
2001	No credits	Anonymous: show registration URL with ?bind=<id> (get <id> from create-session or state response when needed). Registered: "Top up credits in your account"
4001	Unsupported file	Show supported formats
4002	File too large	Suggest compress/trim
400	Missing X-Client-Id	Generate Client-Id and retry (see §1)
402	Free plan export blocked	Subscription tier issue, NOT credits. "Register or upgrade your plan to unlock export."
429	Rate limit (1 token/client/7 days)	Retry in 30s once

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.

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

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)

Tips and Tricks

The backend processes faster when you're specific. Instead of "make it look better", try "convert this AVI to MP4 at 1080p" — concrete instructions get better results.

Max file size is 500MB. Stick to AVI, MOV, MKV, WebM for the smoothest experience.

Export as MP4 for widest compatibility across devices and platforms.

Common Workflows

Quick edit: Upload → "convert this AVI to MP4 at 1080p" → Download MP4. Takes 30-60 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.