Youtube Subtitle Video

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

Security Scan

The skill's requirements and runtime instructions line up with its stated purpose (calling a nemo video-processing API using a single NEMO_TOKEN); nothing in the SKILL.md asks for unrelated credentials or system-wide access.

Purpose & Capability

The skill claims to call a cloud render/subtitle service and only requires a single API token (NEMO_TOKEN). The declared primaryEnv matches the API calls shown in SKILL.md and is proportional to the described functionality.

Instruction Scope

Instructions are narrowly focused on session creation, SSE streaming, uploads, state checks, and exports to the nemovideo.ai API. They expect the agent to upload user-provided video files (multipart form or URL) and to POST/GET specific endpoints. Two minor notes: (1) the flow includes an anonymous-token POST to the external endpoint if NEMO_TOKEN is not present (this creates an external call that yields a token); (2) the doc says to auto-detect platform from an install path ('clawhub'/'cursor'/'unknown'), which implies reading an install path or environment to set X-Skill-Platform — that requires the agent to access its runtime/install info but is not otherwise broad data collection.

Install Mechanism

This is instruction-only with no install spec or downloads, so nothing is written to disk by the skill itself during install.

Credentials

Only NEMO_TOKEN is required (appropriate for calling the nemo API). The frontmatter also mentions a config path (~/.config/nemovideo/) although SKILL.md does not explicitly instruct reading/writing that path; that metadata entry looks unnecessary but not dangerous by itself. The anonymous-token flow produces a short-lived token if you don't provide NEMO_TOKEN.

Persistence & Privilege

The skill is not always-enabled and does not request elevated platform privileges. It instructs saving a session_id for in-session operations (expected) but does not request modifications to other skills or system-wide settings.

Assessment

This skill appears to do what it says: it uploads videos and drives a remote nemo-video API using a single API token. Before installing or invoking it, consider: (1) Only provide a NEMO_TOKEN you trust — the token grants the remote service access to create and manage render jobs and uploads. If you don't want to set a permanent token, the skill's anonymous-token flow will request a short-lived token from https://mega-api-prod.nemovideo.ai, which still authorizes the service. (2) Don't upload sensitive or private videos you wouldn't want processed by an external service. (3) The skill may read its runtime/install path to set an X-Skill-Platform header; if you have concerns about exposing environment or path metadata, ask the skill author to remove that behavior. (4) The metadata lists a config path (~/.config/nemovideo/) that the SKILL.md doesn't explicitly use — expect possible local caching of session info in that directory; if you want to avoid local persistence, check how tokens/session IDs are stored. If you want additional assurance, ask the author for a privacy policy or for exact details on how/where session tokens are stored and for the retention policy of uploaded videos on the nemovideo.ai backend.

Getting Started

Send me your YouTube video and I'll handle the subtitle generation. Or just describe what you're after.

Try saying:

• "add a 10-minute YouTube tutorial video into a 1080p MP4"
• "add subtitles in English and Japanese to my YouTube video"
• "adding subtitles to YouTube videos for YouTubers"

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.

YouTube Subtitle Video — Add Subtitles to YouTube Videos

Drop your YouTube video in the chat and tell me what you need. I'll handle the subtitle generation on cloud GPUs — you don't need anything installed locally.

Here's a typical use: you send a a 10-minute YouTube tutorial video, ask for add subtitles in English and Japanese to my YouTube video, and about 1-2 minutes later you've got a MP4 file ready to download. The whole thing runs at 1080p by default.

One thing worth knowing — shorter video segments generate subtitles faster and with higher accuracy.

Matching Input to Actions

User prompts referencing youtube subtitle video, 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.

Three attribution headers are required on every request and must match this file's frontmatter:

Header	Value
X-Skill-Source	youtube-subtitle-video
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.

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.

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

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 → "add subtitles in English and Japanese to my YouTube video" → Download MP4. Takes 1-2 minutes 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 "add subtitles in English and Japanese to my YouTube 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 YouTube and other platforms.