Subtitle Generator Extension Chrome

Turn a 10-minute YouTube tutorial video into 1080p captioned video files just by typing what you need. Whether it's adding auto-generated subtitles to videos...

Security Scan

The skill's declared credential requirement (NEMO_TOKEN) and runtime instructions line up with a cloud-based subtitle/rendering service; no obvious attempt to access unrelated secrets or install arbitrary code, but there are a few minor inconsistencies and scope items you should confirm before installing.

Purpose & Capability

The skill claims to perform server-side subtitle generation and rendering against a nemo-video API and only requests NEMO_TOKEN — this is proportionate. However, the SKILL.md frontmatter references a config path (~/.config/nemovideo/) even though the registry metadata listed no required config paths; that mismatch should be clarified.

Instruction Scope

Instructions are detailed and mostly limited to the remote API, uploads, and SSE handling. But the skill describes deriving an X-Skill-Platform header by detecting the agent install path (e.g., checking ~/.clawhub/ or ~/.cursor/skills/), which implies reading the agent filesystem/installation environment for attribution — this is outside the stated subtitle/rendering functionality and is unnecessary for core operation.

Install Mechanism

This is an instruction-only skill with no install spec and no code files. Nothing is written to disk by an installer — lowest install risk.

Credentials

Only NEMO_TOKEN is required (declared as primaryEnv) and the SKILL.md also supports acquiring a temporary anonymous token if none is provided. That is consistent with a remote rendering API. Ensure you understand what that token can access and its expiry/credit model before reuse. The SKILL.md references an additional config path in its metadata which was not declared elsewhere — clarify whether the skill will read that path.

Persistence & Privilege

always:false and autonomous invocation allowed (platform default). The skill instructs saving a session_id for ongoing jobs but does not request persistent system-wide privileges or to modify other skills. No evidence it attempts to enable permanent high-privilege presence.

Assessment

This skill appears to do what it says: call a nemo-video rendering/subtitling API using a provided NEMO_TOKEN (or an anonymous token it can request). Before installing, confirm: (1) you trust https://mega-api-prod.nemovideo.ai and understand what the NEMO_TOKEN grants (uploading videos and rendering may expose private content); (2) clarify the mismatch about the config path (~/.config/nemovideo/) in the SKILL.md frontmatter — will the skill read files from your home directory or agent install paths? (3) ask whether platform-detection (checking ~/.clawhub/ or ~/.cursor/skills/) is strictly required; if not, prefer a version that does not probe local install paths. Avoid supplying a long-lived or high-privilege token unless you understand its scope; prefer using the anonymous token flow for testing and review the service's privacy/retention policy for uploaded video data.

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 accurate subtitles in English and"

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.

Subtitle Generator Extension Chrome — Generate and Embed 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 10-minute YouTube tutorial video, type "generate accurate subtitles in English and sync them to the 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 produce the most accurate subtitle sync.

Matching Input to Actions

User prompts referencing subtitle generator extension chrome, 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 subtitle-generator-extension-chrome, 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).

Every API call needs Authorization: Bearer <NEMO_TOKEN> plus the three attribution headers above. If any header is missing, exports return 402.

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 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 accurate subtitles in English and sync them to 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 browsers.

Common Workflows

Quick edit: Upload → "generate accurate subtitles in English and sync them to 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.