Subtitle Translator Generator

Get subtitled translated videos ready to post, without touching a single slider. Upload your video files (MP4, MOV, AVI, WebM, up to 500MB), say something li...

Security Scan

The skill's declared purpose (cloud subtitle translation and embedding) matches its runtime instructions and required credential (NEMO_TOKEN); it is an instruction-only integration that uploads user videos to nemovideo.ai and does not request unrelated system access.

Purpose & Capability

The skill claims to call a remote video-processing API and the only required credential is NEMO_TOKEN, which aligns with that purpose. No unrelated binaries or extraneous service credentials are requested. The metadata's configPaths (~/.config/nemovideo/) is consistent with a CLI client config location for the same service.

Instruction Scope

The SKILL.md instructs the agent to create/use an auth token (NEMO_TOKEN) and to upload user-supplied video files and session data to https://mega-api-prod.nemovideo.ai via the described endpoints. That behavior is expected for a cloud render/subtitle service, but it means user videos and session metadata will be transmitted to an external provider. The instructions do not ask the agent to read unrelated local files or extraneous environment variables.

Install Mechanism

This is an instruction-only skill with no install spec and no code files — nothing is downloaded or written to disk by the skill itself. That is the lowest-risk install model.

Credentials

Only one environment variable is required: NEMO_TOKEN (declared as primaryEnv). That is proportional to a remote API integration. Metadata also lists a config path (~/.config/nemovideo/) which may indicate a local place to persist session info or tokens; the SKILL.md does not instruct reading arbitrary local system files beyond typical token handling.

Persistence & Privilege

The skill is not marked always:true and does not request elevated platform privileges. It instructs creating and saving a session_id for use with the API (expected for long-running jobs) but does not ask to modify other skills or global agent settings.

Assessment

This skill will upload any video files you provide to an external service (mega-api-prod.nemovideo.ai) and will use NEMO_TOKEN if set or obtain a short-lived anonymous token. Before installing or using it: (1) confirm you trust nemovideo.ai (privacy, retention, and sharing of uploaded videos); (2) avoid uploading sensitive or private content unless you have reviewed the service policy; (3) if you must set a permanent NEMO_TOKEN, consider using a scoped or revocable token and revoke it after use; (4) note the skill may persist a session_id for job tracking — if you see unexpected behavior, revoke credentials and clear any nemovideo config; (5) if you want stricter control, do not set NEMO_TOKEN and instead allow the skill to use the anonymous token flow or use a disposable token.

Getting Started

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

Try saying:

• "translate a 3-minute YouTube tutorial in English into a 1080p MP4"
• "translate subtitles into Spanish and French and burn them into the video"
• "translating and adding subtitles to videos in multiple languages for YouTubers, content creators, educators"

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.

Subtitle Translator Generator — Translate and Embed Video Subtitles

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

Here's a typical use: you send a a 3-minute YouTube tutorial in English, ask for translate subtitles into Spanish and French and burn them into the video, 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 and yield more accurate translations.

Matching Input to Actions

User prompts referencing subtitle translator generator, 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.

Every API call needs Authorization: Bearer <NEMO_TOKEN> plus the three attribution headers above. If any header is missing, exports return 402.

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

Header	Value
X-Skill-Source	subtitle-translator-generator
X-Skill-Version	frontmatter version
X-Skill-Platform	auto-detect: clawhub / cursor / unknown from install path

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

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)

Common Workflows

Quick edit: Upload → "translate subtitles into Spanish and French and burn them into the video" → 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.

Tips and Tricks

The backend processes faster when you're specific. Instead of "make it look better", try "translate subtitles into Spanish and French and burn them into the video" — 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.