Video Converter Mov

Skip the learning curve of professional editing software. Describe what you want — convert this MOV file to MP4 without losing quality — and get converted MP...

Security Scan

The skill's requests and runtime instructions are coherent with a cloud-based video conversion service: it needs a NEMO_TOKEN (or will fetch an anonymous one), uploads video files to the listed API, and uses session tokens to run conversions.

Purpose & Capability

Name and description describe cloud video conversion. The only declared credential (NEMO_TOKEN) and the declared config path (~/.config/nemovideo/) are consistent with a client for a third‑party video-rendering backend.

Instruction Scope

SKILL.md contains detailed, bounded instructions for creating a session, uploading files, polling render status, and exporting results. It does not instruct the agent to read unrelated system files or exfiltrate arbitrary data. It will detect install path and read the skill frontmatter for attribution (reasonable for telemetry/headers).

Install Mechanism

Instruction-only skill with no install steps or code to write to disk; lowest install risk.

Credentials

Only one credential is declared (NEMO_TOKEN). The SKILL.md explicitly supports obtaining an anonymous token if none is provided. No other unrelated secrets or credentials are requested.

Persistence & Privilege

Skill is not always-enabled, does not request elevated/system-wide changes, and only maintains session tokens for use with the backend during a session.

Assessment

This skill uploads your video files to a third-party backend (https://mega-api-prod.nemovideo.ai) and uses a bearer token (NEMO_TOKEN) to authenticate. If you don't provide a token the skill will obtain an anonymous token from that service and use it for conversions. Before installing, consider: (1) do you trust the nemovideo.ai service and its privacy/TOS for the content you'll upload? (2) avoid uploading sensitive or private videos to an external cloud service; (3) if you have a NEMO_TOKEN, ensure it has only the minimum privileges needed; (4) the skill will read its own frontmatter and try to detect an install path for attribution — this is benign but means the agent may inspect typical install locations. No code is installed locally by the skill. If you need stronger guarantees about data handling, verify the service's docs or run conversions locally with tools like ffmpeg instead.

Getting Started

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

Try saying:

• "convert my MOV video files"
• "export 1080p MP4"
• "convert this MOV file to MP4"

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 MOV — Convert MOV Files to MP4

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

Say you have a 3-minute MOV recording from an iPhone and want to convert this MOV file to MP4 without losing quality — the backend processes it in about 20-40 seconds and hands you a 1080p MP4.

Tip: shorter clips convert faster — split long MOV files before uploading if possible.

Matching Input to Actions

User prompts referencing video converter mov, 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-Source: video-converter-mov
• X-Skill-Version: from frontmatter version
• X-Skill-Platform: detect from install path (~/.clawhub/ → clawhub, ~/.cursor/skills/ → cursor, else 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

• 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

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

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.

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 MOV file to MP4 without losing quality" — concrete instructions get better results.

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

H.264 codec gives the best balance of quality and file size when converting MOV to MP4.

Common Workflows

Quick edit: Upload → "convert this MOV file to MP4 without losing quality" → 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.