Ai Subtitle Download

Skip the learning curve of professional editing software. Describe what you want — generate and download subtitles for my video in English — and get subtitle...

Security Scan

The skill's requirements and runtime instructions are consistent with a cloud-based video subtitle service: it needs a NEMO_TOKEN or will obtain an anonymous token, uploads video files to nemovideo.ai, and does not request unrelated credentials or install arbitrary code.

Purpose & Capability

The name/description are about generating and downloading subtitles. The only required environment variable is NEMO_TOKEN and the declared config path (~/.config/nemovideo/) aligns with a service-specific client. All declared requirements are proportionate to a cloud subtitle/rendering backend.

Instruction Scope

The SKILL.md instructs the agent to upload user video files or URLs to the nemovideo.ai API, create sessions, send SSE messages, and poll render jobs — all expected for this purpose. It also tells the agent to read the skill's YAML frontmatter (for attribution headers) and to attempt to detect the install path to set an X-Skill-Platform header; these are implementation details that require reading local context but are not obviously malicious. The skill will create/obtain anonymous tokens if NEMO_TOKEN is absent, so uploads can proceed without a pre-set secret; users should be aware their files will be sent to a third-party service.

Install Mechanism

No install spec or bundled code is present (instruction-only). Nothing is downloaded or written to disk by an installer step in the skill itself — lowest-risk installation surface.

Credentials

Only one declared credential (NEMO_TOKEN) is required and is directly relevant to calling the nemovideo.ai API. The skill documents how it will obtain an anonymous token if the env var is not present. No unrelated secrets or system credentials are requested.

Persistence & Privilege

The skill is not force-included (always: false) and does not request any privilege to modify other skills or system settings. It does not persist an installer or run background processes according to the provided metadata.

Assessment

This skill will upload your video files to a third-party service (mega-api-prod.nemovideo.ai) to generate subtitles. Before installing or using it: (1) Confirm you trust nemovideo.ai and are comfortable with your video's privacy — do not upload sensitive content unless you trust the service and its retention/policy. (2) Be aware the skill will use NEMO_TOKEN if present, or automatically request an anonymous token on first use (100 free credits, 7-day expiry). If you set NEMO_TOKEN, treat it like any API secret and store it appropriately. (3) The skill reads its own frontmatter and may check install-path context for header attribution; this is harmless but means it may access small local metadata. (4) If you need stronger guarantees, verify the service's privacy/terms, use a disposable account or anonymous token, and avoid uploading confidential videos. Overall the behavior is coherent with its described purpose.

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 for my"

Quick Start Setup

This skill connects to a cloud processing backend. On first use, set up the connection automatically and let the user know ("Connecting...").

Token check: Look for NEMO_TOKEN in the environment. If found, skip to session creation. Otherwise:

• Generate a UUID as client identifier
• POST https://mega-api-prod.nemovideo.ai/api/auth/anonymous-token with X-Client-Id header
• Extract data.token from the response — this is your NEMO_TOKEN (100 free credits, 7-day expiry)

Session: POST https://mega-api-prod.nemovideo.ai/api/tasks/me/with-session/nemo_agent with Bearer auth and body {"task_name":"project"}. Keep the returned session_id for all operations.

Let the user know with a brief "Ready!" when setup is complete. Don't expose tokens or raw API output.

AI Subtitle Download — Generate and Download 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 10-minute YouTube tutorial video and want to generate and download subtitles for my video in English — the backend processes it in about 30-60 seconds and hands you a 1080p MP4.

Tip: shorter clips under 5 minutes produce faster and more accurate subtitle results.

Matching Input to Actions

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

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.

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

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

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.

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

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.

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)

Tips and Tricks

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

Common Workflows

Quick edit: Upload → "generate and download subtitles for my video in English" → 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.