Ai Subtitle Translator Free

Turn a 3-minute YouTube video in Spanish into 1080p subtitled translated videos just by typing what you need. Whether it's translating subtitles into multipl...

Security Scan

The skill's instructions broadly match a subtitle-translation service, but there are inconsistencies and a few scope items you should verify before installing (notably a referenced config path and automatic remote uploads).

Purpose & Capability

Name/description (translate subtitles, produce MP4s) align with the API endpoints and the single required credential (NEMO_TOKEN). However the SKILL.md frontmatter lists a config path (~/.config/nemovideo/) that is not reflected in the registry 'Required config paths' metadata — this mismatch should be explained. Otherwise the network calls and headers described are proportional to the stated purpose.

Instruction Scope

Instructions are focused on uploading videos, creating sessions, streaming SSE, and polling render state — all consistent with a cloud render service. They do instruct automatic generation of an anonymous token when NEMO_TOKEN is missing and to upload user-provided files to an external API. The page also requests 'auto-detect' of X-Skill-Platform from an install path (which may imply reading agent/installation paths). No instructions ask for unrelated system credentials, but automatic token creation and filesystem detection are behavioral decisions you should be comfortable with.

Install Mechanism

This is an instruction-only skill with no install spec and no code files, so nothing is written to disk by the skill package itself — lowest install risk.

Credentials

The only declared required credential is NEMO_TOKEN, which makes sense for a cloud video service. However SKILL.md frontmatter references a config path (~/.config/nemovideo/) that could contain local credentials or configuration; the registry metadata earlier listed no required config paths. This inconsistency is important because reading that path would increase the skill's access to local state beyond the single declared env var.

Persistence & Privilege

The skill does not request 'always: true' and has no install steps that modify other skills or system-wide settings. It can be invoked autonomously by default (platform normal), which increases runtime scope but is not an unusual privilege on its own.

What to consider before installing

This skill appears to do what it says (upload a video to a cloud backend, translate/subtitle it, and return a download URL), but confirm a few things before enabling it: 1) Ask the publisher to clarify the inconsistent metadata: SKILL.md references ~/.config/nemovideo/ but the registry says no config paths — confirm whether the skill will read that directory and what it contains. 2) Understand that any video or audio you drop into chat will be uploaded to mega-api-prod.nemovideo.ai; don't send sensitive or private content unless you trust that service and its terms. 3) The skill will create an anonymous token if you don't provide one; that token still allows remote processing and has an expiry — know what data retention/processing rules apply. 4) If you keep cloud credentials or other secrets on your machine, verify the skill will not access them (inspect logs or ask for explicit guarantees). 5) If you are uncomfortable with autonomous invocation, disable or restrict the skill's autonomous use in your agent settings. More evidence that would raise confidence: a verified source/homepage, explicit statement whether ~/.config/nemovideo/ is read, or a vendor/publisher identity and privacy/terms link.

Getting Started

Ready when you are. Drop your video files here or describe what you want to make.

Try saying:

• "translate a 3-minute YouTube video in Spanish into a 1080p MP4"
• "translate subtitles from Spanish to English and French"
• "translating subtitles into multiple languages for free for content creators"

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.

AI Subtitle Translator Free — Translate Subtitles Into Any Language

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

Here's a typical use: you send a a 3-minute YouTube video in Spanish, ask for translate subtitles from Spanish to English and French, and about 30-60 seconds 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 and translate significantly faster.

Matching Input to Actions

User prompts referencing ai subtitle translator free, 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	ai-subtitle-translator-free
X-Skill-Version	frontmatter version
X-Skill-Platform	auto-detect: clawhub / cursor / unknown from install path

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

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

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 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 subtitles from Spanish to English 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 subtitles from Spanish to English and French" → Download MP4. Takes 30-60 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.