Online Subtitle Generator

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

Security Scan

The skill's requirements and runtime instructions are broadly consistent with a cloud-based subtitle/rendering service, but there are small metadata inconsistencies and it will upload user video data and obtain/handle tokens on your behalf — review privacy and trust before use.

Purpose & Capability

The skill is described as a cloud subtitle + render pipeline and its instructions target a single external API (mega-api-prod.nemovideo.ai) for session creation, SSE chat, upload, and export. Requesting a service token (NEMO_TOKEN) is coherent with this purpose. Note: the SKILL.md frontmatter declares a config path (~/.config/nemovideo/) but the registry metadata lists no required config paths — this inconsistency is likely a minor packaging/orchestration error but should be corrected.

Instruction Scope

Instructions stay within the stated purpose (auth, create session, upload videos, use SSE, poll exports). They explicitly direct the agent to POST user video files and metadata to an external service and to store a returned session_id for subsequent requests. They also instruct the agent to automatically obtain an anonymous token if NEMO_TOKEN is not set. There is no instruction to read unrelated local files, but the skill will transmit user video/audio data off-device — verify you consent to external uploads.

Install Mechanism

There is no install spec or code to be written to disk (instruction-only). This minimizes local install risk; all runtime activity is network calls described in SKILL.md.

Credentials

The only declared environment credential is NEMO_TOKEN, which matches the API authorization scheme. The skill also describes how to auto-generate an anonymous token when NEMO_TOKEN is missing; this is functionally reasonable but means the skill can obtain credentials without user-supplied secrets. The frontmatter's configPaths value (~/.config/nemovideo/) appears in the skill but the registry metadata shown earlier listed no config paths — this mismatch should be clarified. No other unrelated secrets are requested.

Persistence & Privilege

The skill does not request always: true and does not claim system-wide modifications. It asks to persist a session_id for ongoing jobs, which is reasonable for a multi-step render workflow. There is no instruction to modify other skills or agent-wide settings.

Assessment

This skill is coherent for a cloud subtitle + render service, but it will upload your video/audio to an external domain (mega-api-prod.nemovideo.ai) and will create or use a token (NEMO_TOKEN) to do so. Before installing: 1) Confirm you trust the service and are comfortable with third-party processing of any videos you supply (do not upload sensitive or private videos). 2) Ask the publisher for a homepage/privacy policy and data-retention terms (none provided in the manifest). 3) Note the skill will auto-generate an anonymous token if none is present — if you prefer to control credentials, set NEMO_TOKEN yourself. 4) The frontmatter references a local config path (~/.config/nemovideo/) though the registry metadata did not — ask the author whether the skill will read or write files there. 5) Consider testing with non-sensitive sample videos first. If any of these points are unacceptable or you cannot verify the service owner, do not install or invoke the skill.

Getting Started

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

Try saying:

• "generate my video files"
• "export 1080p MP4"
• "generate subtitles in English and translate"

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 Generator — Generate and Embed Video Subtitles

This tool takes your video files and runs AI subtitle 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 MP4 format and want to generate subtitles in English and translate them to Spanish — the backend processes it in about 30-60 seconds and hands you a 1080p MP4.

Tip: shorter clips under 5 minutes generate subtitles significantly faster.

Matching Input to Actions

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

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	online-subtitle-generator
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.

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

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.

Error Codes

• 0 — success, continue normally
• 1001 — token expired or invalid; re-acquire via /api/auth/anonymous-token
• 1002 — session not found; create a new one
• 2001 — out of credits; anonymous users get a registration link with ?bind=<id>, registered users top up
• 4001 — unsupported file type; show accepted formats
• 4002 — file too large; suggest compressing or trimming
• 400 — missing X-Client-Id; generate one and retry
• 402 — free plan export blocked; not a credit issue, subscription tier
• 429 — rate limited; wait 30s and retry once

Tips and Tricks

The backend processes faster when you're specific. Instead of "make it look better", try "generate subtitles in English and translate them to Spanish" — 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 → "generate subtitles in English and translate them to Spanish" → 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.