Online Subtitle Video

add video files into captioned video files with this skill. Works with MP4, MOV, AVI, WebM files up to 500MB. YouTubers, content creators, educators use it f...

Security Scan

The skill's requests and runtime instructions are consistent with an online video subtitling service, but it uploads user video files to a third-party backend and stores short-lived tokens/sessions — review before sending sensitive content.

Purpose & Capability

The skill's name and description match its required credential (NEMO_TOKEN) and the SKILL.md describes calls to a video-processing backend. One minor inconsistency: the registry metadata listed no required config paths, while the SKILL.md frontmatter declares a config path (~/.config/nemovideo/) — this is likely for storing session/token info but the mismatch should be noted.

Instruction Scope

The SKILL.md instructs the agent to upload user-provided video/audio files to a remote service (mega-api-prod.nemovideo.ai), stream SSE responses, and poll render status. It also directs automatic anonymous-token acquisition (POST to /api/auth/anonymous-token), generation and storage of session_id and inclusion of attribution headers. These behaviors are expected for a cloud render/subtitle service, but they mean user media and generated tokens are transmitted off-device and some local state will be stored.

Install Mechanism

Instruction-only skill with no install steps or code to download — lowest install risk.

Credentials

Only one credential (NEMO_TOKEN) is declared as primary, which is appropriate for a remote API. The SKILL.md also references a config path for storing session/token data; confirm you are comfortable with a token and session metadata being stored locally. No other unrelated credentials or secrets are requested.

Persistence & Privilege

The skill does not request always:true and defaults allow autonomous invocation (normal). It will persist session_id and may write to ~/.config/nemovideo/ per its frontmatter, which is expected for session management but is limited in scope and does not modify other skills or system-wide settings.

Assessment

This skill sends your uploaded videos to a third‑party backend (mega-api-prod.nemovideo.ai) and will obtain and store a short‑lived NEMO_TOKEN/session ID (tokens are described as 7 days/100 free credits). Before installing or using: 1) Don’t upload sensitive or private videos unless you trust the service; 2) Verify the service domain and privacy policy (skill source/homepage are unknown); 3) Note the skill may create a config folder (~/.config/nemovideo/) to store session info — remove it if you revoke access; 4) If you prefer, provide your own NEMO_TOKEN rather than relying on anonymous-token generation; and 5) The registry metadata and SKILL.md disagree about config path requirements — ask the skill author to clarify if you need stricter guarantees about local persistence or data retention.

Getting Started

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

Try saying:

• "add a 3-minute YouTube tutorial recording into a 1080p MP4"
• "add subtitles in English and French to my video"
• "adding subtitles to videos online without editing software for YouTubers, content creators, educators"

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.

Online Subtitle Video — Add Subtitles to Videos Online

Send me your video files and describe the result you want. The AI subtitle generation runs on remote GPU nodes — nothing to install on your machine.

A quick example: upload a 3-minute YouTube tutorial recording, type "add subtitles in English and French to my video", and you'll get a 1080p MP4 back in roughly 30-60 seconds. All rendering happens server-side.

Worth noting: shorter clips under 5 minutes generate subtitles significantly faster.

Matching Input to Actions

User prompts referencing online subtitle video, 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.

Headers are derived from this file's YAML frontmatter. X-Skill-Source is online-subtitle-video, 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.

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

Tips and Tricks

The backend processes faster when you're specific. Instead of "make it look better", try "add subtitles in English and French to my 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.

Common Workflows

Quick edit: Upload → "add subtitles in English and French to my video" → 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.