Multilingual Video Dubbing

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

Security Scan

The skill's declared purpose (cloud video dubbing) matches its runtime behavior, but there are inconsistencies in its declared requirements and the instructions ask the agent to read a local config path and to obtain/use tokens from an external API — details you should confirm before installing.

Purpose & Capability

The skill claims to do cloud-based multilingual video dubbing and all network calls, endpoints, and the single required credential (NEMO_TOKEN) are consistent with that purpose. However, the SKILL.md frontmatter lists a config path (~/.config/nemovideo/) while the registry summary earlier said no config paths are required — this mismatch is unexplained.

Instruction Scope

Runtime instructions tell the agent to use NEMO_TOKEN if present, or to request an anonymous token from https://mega-api-prod.nemovideo.ai and then upload user video files to that domain. They also require adding attribution headers on every request. The agent is instructed to access a local config path (per frontmatter) which could contain tokens — reading that directory is not strictly necessary to perform uploads and is not justified in the SKILL.md.

Install Mechanism

No install spec and no code files — instruction-only skill. This is the lowest-risk install mechanism because nothing will be written to disk by an installer.

Credentials

Only one credential is declared (NEMO_TOKEN) which is appropriate for a cloud API integration. The instructions also permit obtaining an anonymous token from the vendor service. The unexplained frontmatter reference to a local config path could permit reading saved credentials and is disproportionate unless the skill uses local tokens for convenience — the SKILL.md does not justify this.

Persistence & Privilege

always:false and normal autonomous invocation settings. The skill does not request permanent platform-level presence. Nothing in the instructions attempts to modify other skills or system-wide agent settings.

What to consider before installing

This skill largely does what it says (uploads videos to a cloud API and returns dubbed files), but there are two things to confirm before installing: (1) The SKILL.md frontmatter references a local config path (~/.config/nemovideo/) that could be read for tokens — ask the author whether the skill will read that directory and why; if you keep any production credentials there, avoid exposing them. (2) The skill will send user video files and metadata to https://mega-api-prod.nemovideo.ai and may obtain anonymous tokens on your behalf — verify the vendor, privacy policy, and retention of uploaded media. If you provide a real NEMO_TOKEN, treat it like any API key (scoped/minimal privileges, rotate if you suspect exposure). If unsure, prefer using an anonymous/starter token or a disposable test account until you confirm the service's behavior and data handling.

Getting Started

Got video files to work with? Send it over and tell me what you need — I'll take care of the AI voice dubbing.

Try saying:

• "convert a 3-minute product explainer video in English into a 1080p MP4"
• "dub this video into Spanish, French, and German with synced audio"
• "translating and dubbing videos into multiple languages for global audiences for marketers"

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.

Multilingual Video Dubbing — Dub Videos Into Multiple Languages

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

Here's a typical use: you send a a 3-minute product explainer video in English, ask for dub this video into Spanish, French, and German with synced audio, and about 1-3 minutes 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 5 minutes process significantly faster and with higher lip-sync accuracy.

Matching Input to Actions

User prompts referencing multilingual video dubbing, 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.

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

Header	Value
X-Skill-Source	multilingual-video-dubbing
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.

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

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 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 "dub this video into Spanish, French, and German with synced audio" — 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 across platforms and devices.

Common Workflows

Quick edit: Upload → "dub this video into Spanish, French, and German with synced audio" → Download MP4. Takes 1-3 minutes 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.