Ai Subtitle For Movie

add movie video files into subtitled movie files with this skill. Works with MP4, MOV, AVI, MKV files up to 500MB. movie editors and film creators use it for...

Security Scan

The skill's requirements and runtime instructions are consistent with a cloud-based subtitle/rendering service; nothing in the SKILL.md requests unrelated credentials or installs arbitrary code, but the skill will obtain and store short-lived tokens and send user video files to an external API, which you should understand before use.

Purpose & Capability

The skill is described as an AI subtitle/embedding service and only requests a single service credential (NEMO_TOKEN) and interaction with a single backend domain (mega-api-prod.nemovideo.ai), which matches the stated purpose. Minor inconsistency: the registry metadata earlier said no required config paths, but the SKILL.md YAML metadata declares a config path (~/.config/nemovideo/). This mismatch is likely an authoring oversight but worth noting.

Instruction Scope

Instructions stay within subtitle/rendering workflows (session creation, file upload, SSE, export polling). They also direct the agent to auto-obtain an anonymous token if NEMO_TOKEN is not present, to store session_id and tokens for subsequent requests, and to detect an install path to set an attribution header — these are operational/telemetry steps beyond pure subtitle work but are coherent with a cloud service client. The SKILL.md explicitly tells the agent not to display raw tokens to users.

Install Mechanism

No install spec and no code files — instruction-only. This is low-risk because nothing is written to disk by an installer. Network interactions are governed by the SKILL.md instructions.

Credentials

Only one credential (NEMO_TOKEN) is required, which is proportional to a cloud API client. The skill also instructs creating an anonymous token via the service API if no token is present and to persist session/token state (implied config path). Persisting tokens is reasonable for convenience but increases the persistence of credentials — confirm where tokens/sessions are stored and how long they live (SKILL.md says 7-day anonymous token).

Persistence & Privilege

always:false and no instructions to modify other skills or system-wide agent settings. The skill does request storing session state/tokens for ongoing API calls, which is normal for a client service and not an elevated privilege by itself.

Assessment

This skill appears to be a straightforward client for a cloud subtitle/render service. Before installing: (1) Understand that uploaded video files will be sent to https://mega-api-prod.nemovideo.ai — review that service's privacy, retention, and TOS if you care about sensitive content. (2) The skill will auto-create an anonymous NEMO_TOKEN (100 free credits, valid 7 days) and persist session tokens; if you prefer control, set NEMO_TOKEN yourself and verify where tokens are stored (SKILL.md references ~/.config/nemovideo/). (3) Note the small metadata mismatch about config paths between the registry and the SKILL.md — this looks like an authoring oversight, not malicious behavior. If you need stronger assurance, ask the publisher for a homepage, a privacy/billing policy, or to explain where session tokens are stored and how uploads are logged or retained.

Getting Started

Send me your movie video files and I'll handle the AI subtitle generation. Or just describe what you're after.

Try saying:

• "add a 2-hour movie file in MP4 format into a 1080p MP4"
• "generate subtitles for this movie in English and add them as burned-in captions"
• "adding subtitles to movies automatically for movie editors and film creators"

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.

AI Subtitle for Movie — Generate and Embed Movie Subtitles

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

Here's a typical use: you send a a 2-hour movie file in MP4 format, ask for generate subtitles for this movie in English and add them as burned-in captions, and about 1-3 minutes later you've got a MP4 file ready to download. The whole thing runs at 1080p by default.

One thing worth knowing — shorter movie clips process faster — split long films into scenes for quicker results.

Matching Input to Actions

User prompts referencing ai subtitle for movie, 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.

Headers are derived from this file's YAML frontmatter. X-Skill-Source is ai-subtitle-for-movie, X-Skill-Version comes from the version field, and X-Skill-Platform is detected from the install path (~/.clawhub/ = clawhub, ~/.cursor/skills/ = cursor, otherwise unknown).

Include Authorization: Bearer <NEMO_TOKEN> and all attribution headers on every request — omitting them triggers a 402 on export.

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.

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)

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 → "generate subtitles for this movie in English and add them as burned-in captions" → Download MP4. Takes 1-3 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 "generate subtitles for this movie in English and add them as burned-in captions" — concrete instructions get better results.

Max file size is 500MB. Stick to MP4, MOV, AVI, MKV for the smoothest experience.

Export as MP4 for widest compatibility across devices and streaming platforms.