Ai Subtitle Browser

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

Security Scan

The skill's requirements and runtime instructions are generally consistent with a cloud-based subtitle/rendering service — the only issues are minor metadata mismatches and a few documentation assumptions you should verify before use.

Purpose & Capability

The skill claims to upload videos and request rendering/subtitle services from nemovideo.ai and only asks for a NEMO_TOKEN (or to obtain an anonymous token). That aligns with the stated purpose. Minor mismatch: the SKILL.md frontmatter declares a config path (~/.config/nemovideo/) whereas the registry metadata for this skill lists no required config paths.

Instruction Scope

All runtime instructions describe contacting the remote nemovideo API, creating sessions, uploading files, polling exports, and handling SSE — which is exactly what a cloud render/subtitle skill would do. The doc insists on three attribution headers and on reading NEMO_TOKEN if present. One small scope implication: the skill asks to auto-detect an install path to set X-Skill-Platform, which implies the agent may inspect its environment/install path; this is reasonable but worth noting.

Install Mechanism

No install spec / no code files. Instruction-only skills have lower surface area because nothing is written to disk by the skill package itself.

Credentials

The only declared credential is NEMO_TOKEN (primaryEnv). The SKILL.md provides an anonymous-token flow if NEMO_TOKEN is not set, which is coherent but slightly inconsistent with declaring NEMO_TOKEN as 'required' in registry — the agent can operate without a pre-configured token. No unrelated credentials are requested.

Persistence & Privilege

always is false and there's no install-time persistence. The skill can be invoked autonomously (platform default), which is normal; it does not request elevated system privileges or modify other skills' configs.

Assessment

This skill appears to do what it says: it uploads videos to a nemovideo.ai backend for AI subtitle generation and rendering. Before installing/using it, consider the following: 1) Trust & privacy — you will be uploading video content to https://mega-api-prod.nemovideo.ai; confirm you are comfortable with that service's data retention, privacy, and billing (anonymous tokens have 100 credits/7 days per the docs). 2) Token handling — the skill prefers a NEMO_TOKEN env var but can obtain an anonymous token itself; if you provide a long-lived NEMO_TOKEN, ensure it has the minimum necessary scope. 3) Headers & attribution — the skill requires three custom headers on every request (X-Skill-Source/Version/Platform); these identify requests as coming from this skill. 4) Metadata mismatch — the SKILL.md frontmatter lists a config path (~/.config/nemovideo/) that is not present in the registry metadata; confirm whether the agent will read or write files there. 5) Autonomy — the skill can be invoked by the agent normally; if you want to restrict networked actions, avoid granting the agent autonomous invocation. If you need higher assurance, ask the skill author for (a) a privacy/retention statement from nemovideo.ai, (b) clarification about the config path behavior, and (c) whether the anonymous-token endpoint or exported URLs could expose uploaded media to third parties.

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:

• "add my video files"
• "export 1080p MP4"
• "browse and add auto-generated subtitles in"

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 Browser — Browse and Add Video Subtitles

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 video, type "browse and add auto-generated subtitles in English and French", 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 ai subtitle browser, 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-browser
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)

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 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 "browse and add auto-generated subtitles in English and French" — 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 → "browse and add auto-generated subtitles in English and French" → 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.