Video Converter Mov To Mp4

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

Security Scan

The skill's requirements and runtime instructions are consistent with a remote video-conversion API: it needs a NEMO_TOKEN (or will request an anonymous token) and uploads user videos to nemovideo's backend; nothing in the manifest asks for unrelated secrets or weird installs.

Purpose & Capability

The name/description match the instructions: the SKILL.md describes uploading videos, creating a session, and calling nemovideo API endpoints to render MP4s. Requested NEMO_TOKEN and the listed API endpoints are coherent with a cloud video-conversion service. Note: the frontmatter includes a configPaths entry (~/.config/nemovideo/) while the registry metadata earlier said no required config paths — this mismatch should be clarified but is not necessarily malicious.

Instruction Scope

Instructions limit activity to connecting to mega-api-prod.nemovideo.ai, creating sessions, uploading files, reading stream events, and polling render status. They also instruct the agent to detect install path (to set X-Skill-Platform) and to read this file's YAML frontmatter for attribution headers. Those filesystem checks are narrow and plausibly meant only for attribution, but they do require the agent to inspect its environment and skill file.

Install Mechanism

No install spec and no code files — instruction-only skill. This is the lowest-risk install mechanism; nothing will be written or executed locally by an installer.

Credentials

Only NEMO_TOKEN is declared as required (primaryEnv). The SKILL.md also implements a fallback to obtain an anonymous token from the service if NEMO_TOKEN is absent, which makes the token optional in practice. No unrelated credentials or broad environment access are requested. The only minor inconsistency: frontmatter lists a configPath (~/.config/nemovideo/) which wasn't listed elsewhere.

Persistence & Privilege

always is false and there's no install step or persistent agent modification. The skill can be invoked by the model (normal behavior) and will interact with the remote service but does not request permanent platform-wide privileges.

Assessment

This skill appears to do what it says: it uploads videos to nemovideo's cloud service, creates sessions, and returns an MP4 download URL. Before installing or invoking it, consider the following: 1) Privacy: your uploaded video files will be sent to https://mega-api-prod.nemovideo.ai — don't upload sensitive or private videos unless you trust the service and its policy. 2) Tokens: if you provide NEMO_TOKEN the skill will use it; if you don't it will automatically request an anonymous token from the vendor (100 free credits for 7 days). If you have an account, use your own token to maintain control. 3) Attribution/config: the SKILL.md asks the agent to detect install path and read its YAML frontmatter to set X-Skill-Platform/X-Skill-Version headers; this requires the agent to inspect its environment and the skill file — benign but worth knowing. 4) Metadata mismatch: there is a minor inconsistency between the registry metadata (no config paths) and the SKILL.md frontmatter (lists ~/.config/nemovideo/) — ask the publisher to clarify whether any local config is read. 5) Verify the service/domain and its privacy/retention/billing terms if you plan to process confidential content or large volumes. If you want a higher-assurance review, provide the skill's publisher URL, the API's published docs or a sample server response so I can validate endpoints, token format, and what data the service stores.

Getting Started

Ready when you are. Drop your MOV video files here or describe what you want to make.

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 iPhone or Mac MOV files to MP4 for broader compatibility for iPhone users, Mac creators, video editors"

Getting Connected

Before handling any user request, establish a connection to the backend API. Show a brief status like "Connecting...".

If NEMO_TOKEN is in the environment, use it directly and create a session. Otherwise, acquire a free starter token:

• Generate a UUID as client identifier
• POST to https://mega-api-prod.nemovideo.ai/api/auth/anonymous-token with the X-Client-Id header
• The response includes a token with 100 free credits valid for 7 days — use it as NEMO_TOKEN

Then create a session by POSTing to https://mega-api-prod.nemovideo.ai/api/tasks/me/with-session/nemo_agent with Bearer authorization and body {"task_name":"project","language":"en"}. The session_id in the response is needed for all following requests.

Tell the user you're ready. Keep the technical details out of the chat.

Video Converter MOV to MP4 — Convert MOV Files to MP4

Send me your MOV 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 MOV recording from an iPhone, type "convert this MOV file 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 MOV clips convert faster — split long files before uploading if you need quick results.

Matching Input to Actions

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

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.

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

• X-Skill-Source: video-converter-mov-to-mp4
• X-Skill-Version: from frontmatter version
• X-Skill-Platform: detect from install path (~/.clawhub/ → clawhub, ~/.cursor/skills/ → cursor, else unknown)

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.

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

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.

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)

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, MP4, AVI, WebM for the smoothest experience.

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

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.