Audio Video To

Skip the learning curve of professional editing software. Describe what you want — merge this audio and video into a single MP4 file — and get merged video f...

Security Scan

The skill's declared purpose (cloud-based audio/video merging) matches its instructions and required credential (NEMO_TOKEN); nothing required is disproportionate, though there's a small metadata inconsistency to be aware of.

Purpose & Capability

The name/description (merge audio and video via a cloud backend) align with the operations described in SKILL.md (session creation, upload, render, export). The single required credential NEMO_TOKEN is appropriate for a cloud rendering service. Minor inconsistency: the SKILL.md frontmatter lists a config path (~/.config/nemovideo/) while the registry metadata reported earlier lists no required config paths.

Instruction Scope

Instructions are narrowly focused on interacting with the remote API (auth, session, upload, SSE, export). They do not instruct reading arbitrary local files beyond user-provided media. Scope notes: the skill will auto-generate/obtain an anonymous token when NEMO_TOKEN is not present, and it asks the agent to 'auto-detect' install path for setting X-Skill-Platform—small scope creep but understandable for attribution headers. The SKILL.md explicitly instructs not to expose tokens or raw API output.

Install Mechanism

No install spec and no code files — instruction-only. This is the lowest-risk install posture; nothing is downloaded or written to disk by an installer.

Credentials

Only NEMO_TOKEN is required (declared as primaryEnv), which is proportionate for a hosted media service. The skill will also fetch an anonymous token from the API if NEMO_TOKEN is absent (100 free credits, short expiry). No other sensitive environment variables are requested. As noted, there's a small mismatch between SKILL.md metadata (config path) and the registry's reported config paths.

Persistence & Privilege

always:false and normal agent invocation settings. The skill stores and uses ephemeral session_id values for jobs, but it does not request persistent platform privileges or attempt to modify other skills/configurations.

Assessment

This skill appears to do what it says: upload your audio/video to mega-api-prod.nemovideo.ai, render on their cloud GPUs, and return a download URL. Before installing/using it: (1) Confirm you trust the external domain (mega-api-prod.nemovideo.ai) and are okay sending media there. (2) Prefer supplying your own NEMO_TOKEN if you have one — otherwise the skill will obtain an anonymous short-lived token on your behalf. (3) Note the small metadata mismatch: SKILL.md references a local config path (~/.config/nemovideo/) not listed in the registry metadata — verify whether the agent will read or write that path if you care about local files. (4) Avoid uploading sensitive or legally protected content unless you accept that it will be processed by the remote service. (5) Because the skill is instruction-only, there is no installer, but network egress to the service is required. If any of these points are unacceptable, don't enable the skill or ask the provider for clarification on token handling and local config usage.

Getting Started

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

Try saying:

• "convert my audio and video"
• "export 1080p MP4"
• "merge this audio and video into"

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.

Audio Video To — Merge Audio and Video Files

Drop your audio and video 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 with separate audio track, ask for merge this audio and video into a single MP4 file, 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 — keep audio and video the same length to avoid sync issues in the output.

Matching Input to Actions

User prompts referencing audio video to, 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.

Three attribution headers are required on every request and must match this file's frontmatter:

Header	Value
X-Skill-Source	audio-video-to
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.

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.

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.

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 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

Common Workflows

Quick edit: Upload → "merge this audio and video into a single MP4 file" → 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 "merge this audio and video into a single MP4 file" — concrete instructions get better results.

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

Export as MP4 for widest compatibility.