Video To Subtitle Generator

Turn a 3-minute tutorial video recorded on a laptop into 1080p captioned video files just by typing what you need. Whether it's adding accurate subtitles to...

Security Scan

The skill's runtime instructions, requested credential (NEMO_TOKEN), and network endpoints align with a cloud-based video subtitle/rendering service; nothing requested is disproportionate to the stated purpose, though there are small metadata inconsistencies and the service/source is unknown so caution is warranted.

Purpose & Capability

The skill claims to produce captioned video via a remote render service and the instructions exclusively call the nemovideo.ai API and require a single service token (NEMO_TOKEN). That is coherent. Note: frontmatter metadata mentions a config path (~/.config/nemovideo/) while the registry metadata listed no config paths — minor inconsistency to verify (where to read/store tokens).

Instruction Scope

SKILL.md only instructs the agent to obtain/use a service token, create a session, upload videos, stream edits via SSE, poll export status, and return download URLs. It does not instruct reading unrelated system files or exfiltrating other credentials. It does instruct not to print tokens/raw JSON.

Install Mechanism

This is an instruction-only skill with no install spec and no code files — lowest-risk installation footprint.

Credentials

Only one credential is required (NEMO_TOKEN), which is proportional for a hosted rendering API. The metadata's mention of a config path may imply reading a local token file; confirm whether the agent will read that path and whether that file could contain other secrets.

Persistence & Privilege

Skill is not always:true, does not request elevated or cross-skill config changes, and has no install-time persistence. Autonomous invocation is allowed (platform default) but not unusual here.

Assessment

This skill appears to do what it says: it talks to a nemovideo.ai service and needs one service token. Before installing: 1) Confirm you trust mega-api-prod.nemovideo.ai (check the vendor, homepage, and privacy/terms) because you will upload video content to their servers. 2) Clarify the config-path inconsistency (SKILL.md metadata lists ~/.config/nemovideo/) so you know whether the agent will read or store a token file locally. 3) Prefer short-lived/anonymous tokens for sensitive content; avoid supplying long-lived system credentials. 4) Don’t upload private or regulated videos without verifying the service’s retention and access policies. 5) If you need higher assurance, request the skill author/publisher information or a vetted homepage/source before use.

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 Spanish"

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.

Video to Subtitle Generator — Auto-Generate Subtitles for Videos

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 tutorial video recorded on a laptop, type "generate subtitles in English and Spanish and burn them into the video", and you'll get a 1080p MP4 back in roughly 30-60 seconds. All rendering happens server-side.

Worth noting: cleaner audio produces more accurate subtitle timing and fewer corrections needed.

Matching Input to Actions

User prompts referencing video to 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	video-to-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 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)

Translating GUI Instructions

The backend responds as if there's a visual interface. Map its instructions to API calls:

• "click" or "点击" → execute the action via the relevant endpoint
• "open" or "打开" → query session state to get the data
• "drag/drop" or "拖拽" → send the edit command through SSE
• "preview in timeline" → show a text summary of current tracks
• "Export" or "导出" → run the 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 Spanish 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.

Common Workflows

Quick edit: Upload → "generate subtitles in English and Spanish and burn them into the 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.