Converter Ai

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

Security Scan

The skill's requests and runtime instructions are consistent with a cloud-based video conversion service: it only requires a NEMO_TOKEN and instructs the agent to upload user video files to the nemo video API for processing.

Purpose & Capability

Name/description (video conversion) align with required credential NEMO_TOKEN and the API endpoints described. Minor inconsistency: the registry metadata showed no required config paths, but the SKILL.md frontmatter lists a config path (~/.config/nemovideo/)—this suggests the skill may read/write a local nemo config directory but the registry did not declare it.

Instruction Scope

Instructions keep to conversion workflow: obtain or use NEMO_TOKEN, create a session, upload user-supplied video files, poll for render completion, and return download URLs. Important: the runtime explicitly uploads user media to an external domain (mega-api-prod.nemovideo.ai) and may generate and persist an anonymous token; users should expect their video data to be sent to that third-party service. The SKILL.md also instructs deriving X-Skill-* headers from metadata and the install path (harvesting install-path info is benign but notable).

Install Mechanism

Instruction-only skill with no install spec and no code files — nothing is written to disk by an installer. This is the lowest install risk.

Credentials

Only one credential (NEMO_TOKEN) is required, which is proportional to a service that performs server-side work. The SKILL.md may create an anonymous token if none is supplied; that's consistent with its stated behavior.

Persistence & Privilege

The skill is not always-on and can be invoked by the user. It does not request system-wide privileges or other skills' configs. It may persist session/token info for continued use (normal for this service).

Assessment

This skill uploads any video you give it to an external service (mega-api-prod.nemovideo.ai) and uses a service token (NEMO_TOKEN) to authenticate. Before installing or using it: (1) confirm you trust the nemo video service and its privacy terms — do not upload sensitive or private videos unless you're comfortable with that third party; (2) prefer supplying your own service token only if you understand where it is stored and used; (3) note the SKILL.md mentions a local config path (~/.config/nemovideo/) that wasn't declared in the registry—ask the publisher how/where tokens or session IDs are persisted; (4) verify the API hostname is legitimate for the service and consider testing with non-sensitive sample files first.

Getting Started

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

Try saying:

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

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 AI — Convert and Export Video Files

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 2-minute MP4 recorded on an iPhone, ask for convert this MOV file to MP4 at 1080p, and about 20-40 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 convert faster — split long videos before uploading.

Matching Input to Actions

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

All calls go to https://mega-api-prod.nemovideo.ai. The main endpoints:

1. Session — POST /api/tasks/me/with-session/nemo_agent with {"task_name":"project","language":"<lang>"}. Gives you a session_id.
2. Chat (SSE) — POST /run_sse with session_id and your message in new_message.parts[0].text. Set Accept: text/event-stream. Up to 15 min.
3. Upload — POST /api/upload-video/nemo_agent/me/<sid> — multipart file or JSON with URLs.
4. Credits — GET /api/credits/balance/simple — returns available, frozen, total.
5. State — GET /api/state/nemo_agent/me/<sid>/latest — current draft and media info.
6. Export — POST /api/render/proxy/lambda with render ID and draft JSON. Poll GET /api/render/proxy/lambda/<id> every 30s for completed status and download URL.

Formats: mp4, mov, avi, webm, mkv, jpg, png, gif, webp, mp3, wav, m4a, aac.

Headers are derived from this file's YAML frontmatter. X-Skill-Source is converter-ai, X-Skill-Version comes from the version field, and X-Skill-Platform is detected from the install path (~/.clawhub/ = clawhub, ~/.cursor/skills/ = cursor, otherwise 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.

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)

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

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.

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 MOV file to MP4 at 1080p" → 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 MOV file to MP4 at 1080p" — concrete instructions get better results.

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

Export as MP4 for widest compatibility.