Translator Generator

Turn a 3-minute tutorial video in English into 1080p translated captioned videos just by typing what you need. Whether it's translating video content into mu...

Security Scan

The skill's requests and runtime instructions are coherent with a video-translation service (it uses a single service token and uploads files to an external rendering API), but the package is instruction-only, from an unknown source, and has a small metadata mismatch that lowers confidence.

Purpose & Capability

Name/description (translate videos, produce captioned MP4s) match the instructions: upload video files, call a cloud render API, and return download URLs. The only required credential (NEMO_TOKEN) is consistent with a cloud service integration. Minor inconsistency: SKILL.md frontmatter lists a config path (~/.config/nemovideo/) while the registry metadata reported no required config paths; this is likely benign but should be confirmed.

Instruction Scope

SKILL.md gives explicit, narrow runtime instructions: authenticate (use NEMO_TOKEN or obtain an anonymous token from the service), create a session, upload files, call render endpoints, and handle SSE/state polling. All network calls are to the documented nemovideo API and are expected for this purpose. Note: the skill will automatically create an anonymous token if none is provided and will upload user video files to the external service — users should expect outbound network traffic and file transfer. No instructions ask the agent to read unrelated system files or other credentials.

Install Mechanism

Instruction-only skill with no install spec and no code files — lowest install risk; nothing is written to disk by an installer. The runtime behavior still performs network activity, but there is no packaged code being downloaded or executed by an installer step.

Credentials

Only NEMO_TOKEN is declared as required and is the primary credential — appropriate for a cloud translation/render service. The SKILL.md frontmatter references a config path (~/.config/nemovideo/), which could imply reading/writing local config; the registry metadata did not list config paths. Confirm whether the skill will access that directory. Otherwise, environment and credential requests are proportionate.

Persistence & Privilege

Skill does not request always:true and does not ask to modify other skills or system-wide settings. It instructs storing a session_id/token for session continuity, which is normal for a service client. Autonomous invocation is allowed by default (platform normal) but not excessive here.

Assessment

This skill appears to do what it says: it uploads videos to nemovideo.ai, creates sessions, and returns rendered videos. Before installing, consider: (1) Privacy — your video files will be uploaded to an external service; avoid uploading sensitive content. (2) Token handling — the skill can auto-generate an anonymous NEMO_TOKEN (100 free credits) if you don't provide one; if you prefer control, create/store your own NEMO_TOKEN instead of allowing anonymous provisioning. (3) Metadata mismatch — SKILL.md references a local config path (~/.config/nemovideo/) even though registry metadata omitted it; ask the publisher whether the skill will read/write that directory. (4) Source accountability — the skill has no homepage and an unknown source; if provenance matters, request publisher information or choose a published/verified equivalent. Because this is an instruction-only skill, there was no packaged code to scan; network behavior will occur at runtime, so review logs/requests if you need additional assurance.

Getting Started

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

Try saying:

• "translate my video files"
• "export 1080p MP4"
• "translate this video's audio and subtitles"

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.

Translator Generator — Translate Videos Into Any Language

This tool takes your video files and runs AI translation generation through a cloud rendering pipeline. You upload, describe what you want, and download the result.

Say you have a 3-minute tutorial video in English and want to translate this video's audio and subtitles into Spanish and French — the backend processes it in about 1-2 minutes and hands you a 1080p MP4.

Tip: shorter clips under 5 minutes produce the most accurate translations.

Matching Input to Actions

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

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

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.

Translating GUI Instructions

The backend responds as if there's a visual interface. Map its instructions to API calls:

• "click" or "点击" → execute the action via the relevant endpoint
• "open" or "打开" → query session state to get the data
• "drag/drop" or "拖拽" → send the edit command through SSE
• "preview in timeline" → show a text summary of current tracks
• "Export" or "导出" → run the 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)

Tips and Tricks

The backend processes faster when you're specific. Instead of "make it look better", try "translate this video's audio and subtitles into 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 and devices.

Common Workflows

Quick edit: Upload → "translate this video's audio and subtitles into 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.