Subtitle Generator Download

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

Security Scan

The skill's requests and runtime instructions align with its stated purpose (remote subtitle/video render via Nemo API); minor inconsistencies and a few data-flow details mean you should review the external API and token use before installing.

Purpose & Capability

The name/description describe remote subtitle generation and video export; the skill only asks for a single service credential (NEMO_TOKEN) and its runtime instructions call the NemoVideo API endpoints described in the SKILL.md — this is coherent with the stated purpose. Minor inconsistency: the registry metadata lists no required config paths while the SKILL.md frontmatter declares a configPaths entry (~/.config/nemovideo/).

Instruction Scope

Instructions largely stay within the domain of uploading videos, creating sessions, SSE streaming, and polling render status. The skill will: read its own frontmatter for attribution, detect install path to set an X-Skill-Platform header, read NEMO_TOKEN if present, and (if no token) request an anonymous token from a public endpoint. These actions are explainable by the workflow but do mean user videos and metadata will be uploaded to mega-api-prod.nemovideo.ai; the skill also requests reading the install path and its own file metadata which are broader than strictly necessary but understandable for attribution.

Install Mechanism

There is no install spec and no code files — instruction-only skill — so nothing is written to disk by an installer. This is the lowest install risk.

Credentials

Only NEMO_TOKEN is declared as required (primary credential), which matches the described API usage. The SKILL.md additionally describes obtaining an anonymous token automatically if NEMO_TOKEN is absent; this behavior is reasonable but means the skill will perform network auth even without a user-supplied secret. No unrelated credentials are requested.

Persistence & Privilege

The skill does not request always:true and does not attempt to modify other skills or system-wide settings. It will read the install path and its own frontmatter for header attribution but does not request elevated or persistent system privileges.

Assessment

This skill appears to do what it says: it uploads videos to a NemoVideo backend, creates a session, runs SSE-based generation, and returns a download URL. Before installing, consider: (1) Privacy — your video/audio will be uploaded to https://mega-api-prod.nemovideo.ai; verify you trust that service and its retention policy. (2) Token handling — the skill reads NEMO_TOKEN if present and will automatically obtain a short-lived anonymous token if not; avoid putting highly-privileged credentials in NEMO_TOKEN unless you trust the integration. (3) Attribution headers — the skill reads its own frontmatter and detects install path for X-Skill-Platform, which requires reading some local paths; this is read-only but worth noting. (4) Inconsistency — registry metadata lists no config paths while SKILL.md declares ~/.config/nemovideo/ in its frontmatter; you may want clarification from the author. If you’re comfortable with the external service and its policies, the skill is internally coherent. If you need higher assurance, ask the publisher for a provenance/hosting statement or use a disposable token.

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

Getting Connected

Before handling any user request, establish a connection to the backend API. Show a brief status like "Connecting...".

If NEMO_TOKEN is in the environment, use it directly and create a session. Otherwise, acquire a free starter token:

• Generate a UUID as client identifier
• POST to https://mega-api-prod.nemovideo.ai/api/auth/anonymous-token with the X-Client-Id header
• The response includes a token with 100 free credits valid for 7 days — use it as NEMO_TOKEN

Then create a session by POSTing to https://mega-api-prod.nemovideo.ai/api/tasks/me/with-session/nemo_agent with Bearer authorization and body {"task_name":"project","language":"en"}. The session_id in the response is needed for all following requests.

Tell the user you're ready. Keep the technical details out of the chat.

Subtitle Generator Download — Generate and Download 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 "generate and download subtitles in English with accurate timestamps", 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 faster and more accurately.

Matching Input to Actions

User prompts referencing subtitle generator download, 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.

Skill attribution — read from this file's YAML frontmatter at runtime:

• X-Skill-Source: subtitle-generator-download
• X-Skill-Version: from frontmatter version
• X-Skill-Platform: detect from install path (~/.clawhub/ → clawhub, ~/.cursor/skills/ → cursor, else unknown)

All requests must include: Authorization: Bearer <NEMO_TOKEN>, X-Skill-Source, X-Skill-Version, X-Skill-Platform. Missing attribution headers will cause export to fail with 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.

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.

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

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

Common Workflows

Quick edit: Upload → "generate and download subtitles in English with accurate timestamps" → 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.

Tips and Tricks

The backend processes faster when you're specific. Instead of "make it look better", try "generate and download subtitles in English with accurate timestamps" — 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 players.