Video Converter Best

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

Security Scan

The skill mostly matches a cloud video-conversion service, but there are inconsistencies and small scope creeps (reading local paths, a configPath mismatch, and automatic token creation) that you should understand before installing.

Purpose & Capability

Name/description (convert various video formats to MP4 via cloud GPUs) aligns with the runtime instructions to call a remote render API. Requesting a single API token (NEMO_TOKEN) is proportional. However, the SKILL.md frontmatter lists a config path (~/.config/nemovideo/) that the registry metadata did not list — this mismatch is unexplained and worth asking the author about.

Instruction Scope

Instructions direct the agent to (a) create an anonymous token via POST if NEMO_TOKEN is absent, (b) create sessions and upload videos (multipart file uploads or by URL), and (c) read the skill file frontmatter and detect install paths to populate attribution headers. Reading install paths and config locations implies accessing the local filesystem; while reading the skill's own frontmatter is reasonable, the install-path detection and explicit multipart file path examples could allow the agent to attempt arbitrary file reads if implemented poorly. The SKILL.md otherwise stays within the converter's domain and does not request unrelated secrets.

Install Mechanism

No install spec or external downloads are included (instruction-only skill), so nothing will be written to disk by an installer. This is a low-risk install model.

Credentials

Only NEMO_TOKEN is declared as required and as the primary credential, which fits a cloud API integration. The anonymous-token flow will create a short-lived token if none is provided. The use of a config path in the frontmatter suggests the skill might read or store data under ~/.config/nemovideo/, but the registry metadata did not list that; this inconsistency should be clarified before providing credentials.

Persistence & Privilege

The skill does not request 'always: true' or other elevated persistent privileges. It asks to save a session_id for job management (normal). Autonomous invocation by the model is enabled by default (platform normal) and not by itself a reason to block installation.

What to consider before installing

This skill appears to be a straightforward cloud-based video converter that uses a single API token (NEMO_TOKEN). Before installing: 1) Confirm you trust the domain (mega-api-prod.nemovideo.ai) and understand the service's privacy/retention policy—your videos will be uploaded to that service. 2) Ask the publisher why registry metadata omits the ~/.config/nemovideo/ path present in the skill frontmatter and what is stored there. 3) If you will provide NEMO_TOKEN, prefer a short-lived or limited-scope token; avoid handing over long-lived credentials. 4) Ensure the agent is implemented to only upload user-provided files (not arbitrary filesystem paths). 5) If you need stricter control, request that the skill only accept file objects or URLs (not raw local path reads) and that it document exactly what it writes to ~/.config/nemovideo/ (if anything). If these questions are not answered to your satisfaction, treat the skill cautiously or do not install.

Getting Started

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

Try saying:

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

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.

Video Converter Best — Convert Any Video to MP4

Drop your video files in the chat and tell me what you need. I'll handle the AI format conversion on cloud GPUs — you don't need anything installed locally.

Here's a typical use: you send a a 3-minute AVI file from an old camcorder, ask for convert this AVI to MP4 at 1080p without losing quality, and about 30-60 seconds later you've got a MP4 file ready to download. The whole thing runs at 1080p by default.

One thing worth knowing — shorter clips under 2 minutes convert in under 30 seconds.

Matching Input to Actions

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

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)

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 at 1080p without losing quality" → 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.

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 without losing quality" — 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.