Ai Subtitle Japanese To English

Get English-captioned videos ready to post, without touching a single slider. Upload your Japanese video files (MP4, MOV, AVI, WebM, up to 500MB), say someth...

Security Scan

The skill’s declared purpose (translating/burning English subtitles onto Japanese videos) aligns with its runtime instructions and the single required credential (NEMO_TOKEN); there are no unrelated secrets or installs requested, but a couple of small metadata/clarity issues are worth noting before use.

Purpose & Capability

Name/description match the instructions: the SKILL.md describes uploading video files to a nemovideo.ai cloud render pipeline and using a NEMO_TOKEN for authorization. Requiring a service token to call the remote API is proportionate to the stated purpose.

Instruction Scope

Instructions are focused on creating sessions, uploading media, driving SSE/chat, polling export/status endpoints, and returning download URLs — all consistent with a cloud subtitle/render service. Note: the skill instructs generating an anonymous token if a NEMO_TOKEN isn’t present and requires the agent to include specific attribution headers. Also be aware the instructions send user video files to an external service (privacy consideration).

Install Mechanism

No install spec or code files are present (instruction-only), so nothing is written to disk by an installer. This is the lowest-risk install posture and matches the skill style.

Credentials

Only one credential is required (NEMO_TOKEN), which is appropriate for a cloud API. Minor inconsistency: the registry metadata reported no required config paths, but the SKILL.md frontmatter lists a config path (~/.config/nemovideo/). That mismatch should be clarified (does the agent need to read that path or not?).

Persistence & Privilege

Skill is not marked always:true and is user-invocable. It does not request permanent agent-level privileges. Autonomous invocation is allowed (default) but is not a special escalation here.

Assessment

This skill appears to do what it claims: it uses a single NEMO_TOKEN to call nemovideo.ai endpoints, upload your videos, and return processed MP4s. Before installing/use: 1) Confirm you are comfortable uploading videos to mega-api-prod.nemovideo.ai and review that service’s privacy/retention policy for sensitive content. 2) Keep your NEMO_TOKEN secret; the skill will use it in Authorization headers (the instructions state not to print tokens). 3) Ask the author to clarify the config path discrepancy (~/.config/nemovideo/ appears in the SKILL.md frontmatter but registry metadata shows none) and how X-Skill-Platform should be determined when there is no install path. 4) Verify the required attribution headers and version string are acceptable for your environment. If you need these clarifications answered, treat the discrepancy as a minor red flag but not a blocker.

Getting Started

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

Try saying:

• "convert a 10-minute Japanese interview video into a 1080p MP4"
• "translate Japanese speech to English subtitles and burn them into the video"
• "translating Japanese video content into English subtitles for language learners, content translators, anime fans"

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.

AI Subtitle Japanese to English — Translate Japanese Videos to English

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

Say you have a 10-minute Japanese interview video and want to translate Japanese speech to English subtitles and burn them into the video — the backend processes it in about 1-2 minutes and hands you a 1080p MP4.

Tip: clear audio with minimal background noise improves translation accuracy significantly.

Matching Input to Actions

User prompts referencing ai subtitle japanese to english, 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 calls go to https://mega-api-prod.nemovideo.ai. The main endpoints:

1. Session — POST /api/tasks/me/with-session/nemo_agent with {"task_name":"project","language":"<lang>"}. Gives you a session_id.
2. Chat (SSE) — POST /run_sse with session_id and your message in new_message.parts[0].text. Set Accept: text/event-stream. Up to 15 min.
3. Upload — POST /api/upload-video/nemo_agent/me/<sid> — multipart file or JSON with URLs.
4. Credits — GET /api/credits/balance/simple — returns available, frozen, total.
5. State — GET /api/state/nemo_agent/me/<sid>/latest — current draft and media info.
6. Export — POST /api/render/proxy/lambda with render ID and draft JSON. Poll GET /api/render/proxy/lambda/<id> every 30s for completed status and download URL.

Formats: 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-japanese-to-english
X-Skill-Version	frontmatter version
X-Skill-Platform	auto-detect: clawhub / cursor / unknown from install path

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.

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)

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.

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

Common Workflows

Quick edit: Upload → "translate Japanese speech to English subtitles 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 Japanese speech to English subtitles 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.