Subtitle Video Youtube

Get captioned YouTube videos ready to post, without touching a single slider. Upload your YouTube video (MP4, MOV, AVI, WebM, up to 500MB), say something lik...

Security Scan

The skill's requests and runtime instructions are consistent with a remote video captioning service: it needs a NEMO_TOKEN (or can mint an anonymous one), uploads user videos to the nemovideo.ai backend, and does not install code locally.

Purpose & Capability

The name/description (add captions and render videos) aligns with required artifacts: a single API credential (NEMO_TOKEN), session creation, upload, SSE, and export endpoints on mega-api-prod.nemovideo.ai. Nothing requested (binaries, unrelated credentials) is outside that scope.

Instruction Scope

SKILL.md instructs the agent to create sessions, stream SSE, upload user files/URLs, poll render status, and translate backend messages — all expected. It also instructs reading the skill's YAML frontmatter and detecting install path to set X-Skill-Platform; these require filesystem metadata access (read-only) which is reasonable but worth noting.

Install Mechanism

No install spec and no code files are present (instruction-only). This is low-risk: nothing is downloaded or executed locally by the skill itself.

Credentials

Only NEMO_TOKEN is required (primaryEnv). The manifest also declares a config path (~/.config/nemovideo/) and the instructions may read install path and the skill file; that access is plausible for platform attribution but users should be aware the skill may read those paths if platform permissions allow.

Persistence & Privilege

always is false and the skill does not request persistent system-wide changes. It does instruct use of session tokens for remote jobs (render jobs live server-side), which is expected for an external render service.

Assessment

This skill will upload videos and metadata to mega-api-prod.nemovideo.ai for remote captioning and rendering. Before installing or using it: (1) confirm you trust nemovideo.ai and its privacy/terms because uploaded video/audio will be processed off-device; (2) if you don't set NEMO_TOKEN, the skill will request an anonymous token from the service (no local secrets required); (3) the skill may read its own frontmatter and detect install paths or a ~/.config/nemovideo/ directory for attribution—if you have sensitive files in those paths, consider restricting access; and (4) avoid uploading private or sensitive footage unless you have verified the provider's data-handling policies. If you want higher assurance, request the skill author/publisher and privacy policy for the nemovideo API before use.

Getting Started

Ready when you are. Drop your YouTube video here or describe what you want to make.

Try saying:

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

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 Video YouTube — Add Captions to YouTube Videos

Send me your YouTube video and describe the result you want. The subtitle generation runs on remote GPU nodes — nothing to install on your machine.

A quick example: upload a 10-minute YouTube tutorial video, type "add subtitles in English and Spanish to my YouTube video", and you'll get a 1080p MP4 back in roughly 1-2 minutes. All rendering happens server-side.

Worth noting: shorter clips under 5 minutes process significantly faster.

Matching Input to Actions

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

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

Common Workflows

Quick edit: Upload → "add subtitles in English and Spanish 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 Spanish 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 with YouTube uploads.