Multilingual Video

generate video files into subtitled multilingual videos with this skill. Works with MP4, MOV, AVI, WebM files up to 500MB. content creators and marketers use...

Security Scan

The skill's behavior mostly matches a video-rendering backend, but there are inconsistencies and unclear storage/credential handling that you should review before installing.

Purpose & Capability

Name/description match the runtime instructions (calls a nemo video rendering API to add multilingual subtitles). Requesting a NEMO_TOKEN is coherent for a third‑party API. However, the SKILL.md frontmatter lists a config path (~/.config/nemovideo/) while the registry metadata reported no required config paths — this mismatch should be clarified.

Instruction Scope

The instructions tell the agent to: obtain anonymous tokens from an external API if NEMO_TOKEN is not set, create and persist a session_id, upload user video files, and detect the agent install path to set X-Skill-Platform. They also instruct the agent to 'not display raw API responses or token values' (which masks what is being stored). These are network and file‑system actions beyond simple local processing and the token/session persistence location is not explicitly defined.

Install Mechanism

No install spec and no code files — this is instruction-only, so nothing is written during an install step. Runtime will perform network calls but no package downloads or archive extraction are specified.

Credentials

Only NEMO_TOKEN is declared as required (primaryEnv), which fits the stated API usage. But the skill also instructs generating an anonymous token automatically if NEMO_TOKEN is absent and implies storing it; it also references a config path in its frontmatter. Ensure you are comfortable with the skill creating/storing credentials on your behalf.

Persistence & Privilege

The skill instructs storing session_id and potentially the anonymous token for subsequent requests and references a config directory (~/.config/nemovideo/). Although always:false and autonomous invocation are normal, persistent storage of tokens/sessions without a clear storage location or retention policy raises privacy and lifecycle concerns (token expiry, orphaned jobs, and where secrets are written).

What to consider before installing

This skill will call an external API (https://mega-api-prod.nemovideo.ai), upload videos, and create/store session tokens. Confirm you trust that domain and are okay with the skill automatically obtaining and persisting an anonymous token if you don't provide NEMO_TOKEN. Ask the author where tokens/session IDs are stored (in-memory vs. ~/.config/nemovideo/), how long they are retained, and whether uploads or tokens are shared with other accounts. Also request they fix the metadata mismatch (registry says no config paths, SKILL.md declares one) and clarify exactly what the skill will write to disk before you enable it.

Getting Started

Share your video files and I'll get started on multilingual subtitle generation. Or just tell me what you're thinking.

Try saying:

• "generate my video files"
• "export 1080p MP4"
• "add subtitles in English, Spanish, and"

First-Time Connection

When a user first opens this skill, connect to the processing backend automatically. Briefly let them know (e.g. "Setting up...").

Authentication: Check if NEMO_TOKEN is set in the environment. If it is, skip to step 2.

1. Obtain a free token: Generate a random UUID as client identifier. POST to https://mega-api-prod.nemovideo.ai/api/auth/anonymous-token with header X-Client-Id set to that UUID. The response data.token is your NEMO_TOKEN — 100 free credits, valid 7 days.
2. Create a session: POST to https://mega-api-prod.nemovideo.ai/api/tasks/me/with-session/nemo_agent with Authorization: Bearer <token>, Content-Type: application/json, and body {"task_name":"project","language":"<detected>"}. Store the returned session_id for all subsequent requests.

Keep setup communication brief. Don't display raw API responses or token values to the user.

Multilingual Video — Add Subtitles in Multiple Languages

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

Here's a typical use: you send a a 3-minute product demo video in English, ask for add subtitles in English, Spanish, and French, and about 1-2 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.

Matching Input to Actions

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

Skill attribution — read from this file's YAML frontmatter at runtime:

• X-Skill-Source: multilingual-video
• 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 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

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.

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 "add subtitles in English, Spanish, and French" — 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.

Common Workflows

Quick edit: Upload → "add subtitles in English, Spanish, and French" → Download MP4. Takes 1-2 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.