Subtitle Video 4k

Get captioned 4K videos ready to post, without touching a single slider. Upload your video files (MP4, MOV, AVI, WebM, up to 500MB), say something like "add...

Security Scan

The skill's requirements and runtime instructions are consistent with a cloud-based subtitle/video-rendering tool, but it will make automatic network calls (including generating/storing an anonymous token if NEMO_TOKEN is absent) and the SKILL.md contains a small metadata mismatch about a config path.

Purpose & Capability

Name/description (add subtitles to uploaded 4K video) align with the declared primary credential (NEMO_TOKEN) and the API endpoints in the instructions. Minor inconsistency: SKILL.md frontmatter lists a config path (~/.config/nemovideo/) while the registry metadata in the manifest reported no required config paths.

Instruction Scope

Instructions are focused on: authenticate (use NEMO_TOKEN or request anonymous token), create a session, upload video files, stream SSE for generation, and export rendered MP4. They do not ask for unrelated files or unrelated credentials. They do instruct automatic connection/session creation if NEMO_TOKEN is not present, so the agent will perform outbound network calls as part of setup.

Install Mechanism

No install spec and no code files — instruction-only skill (lowest install risk). Nothing is written to disk by an installer step in the repository.

Credentials

Only NEMO_TOKEN is required (declared as primaryEnv), which is proportionate for a remote API service. SKILL.md references a config path (~/.config/nemovideo/), implying the skill might read/store session state on disk — this was not surfaced in the registry requirements and should be clarified.

Persistence & Privilege

always is false and the skill does not request system-wide changes or modification of other skills. It does instruct storing session_id for subsequent API calls (normal for a remote-service integration).

Assessment

This skill behaves like a cloud video-processing integration: it will make outbound network calls to mega-api-prod.nemovideo.ai, upload any videos you provide, and will either use an existing NEMO_TOKEN or request an anonymous token on your behalf (100 free credits, 7-day validity). Before installing: confirm you trust the nemo video service and are comfortable uploading the footage (privacy/retention concerns); if you prefer not to allow automatic token creation, set NEMO_TOKEN yourself instead of relying on anonymous-token flow; ask the publisher to clarify whether session tokens are stored under ~/.config/nemovideo/ and where tokens/session IDs are persisted and encrypted; and avoid sending sensitive or private video content until you verify the service's privacy and terms. The small metadata mismatch (config path present in SKILL.md but not in registry metadata) is not necessarily malicious but worth clarifying with the skill author.

Getting Started

Share your video files and I'll get started on subtitle generation. Or just tell me what you're thinking.

Try saying:

• "add my video files"
• "export 4K MP4"
• "add subtitles in English to my"

First-Time Connection

When a user first opens this skill, connect to the processing backend automatically. Briefly let them know (e.g. "Setting up...").

Authentication: Check if NEMO_TOKEN is set in the environment. If it is, skip to step 2.

1. Obtain a free token: Generate a random UUID as client identifier. POST to https://mega-api-prod.nemovideo.ai/api/auth/anonymous-token with header X-Client-Id set to that UUID. The response data.token is your NEMO_TOKEN — 100 free credits, valid 7 days.
2. Create a session: POST to https://mega-api-prod.nemovideo.ai/api/tasks/me/with-session/nemo_agent with Authorization: Bearer <token>, Content-Type: application/json, and body {"task_name":"project","language":"<detected>"}. Store the returned session_id for all subsequent requests.

Keep setup communication brief. Don't display raw API responses or token values to the user.

Subtitle Video 4K — Add Subtitles to 4K Videos

Send me your video files 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 3-minute 4K product walkthrough video, type "add subtitles in English to my 4K video", and you'll get a 4K MP4 back in roughly 1-2 minutes. All rendering happens server-side.

Worth noting: shorter clips process faster even at 4K resolution.

Matching Input to Actions

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

Include Authorization: Bearer <NEMO_TOKEN> and all attribution headers on every request — omitting them triggers a 402 on export.

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

Header	Value
X-Skill-Source	subtitle-video-4k
X-Skill-Version	frontmatter version
X-Skill-Platform	auto-detect: clawhub / cursor / unknown from install path

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

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

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 "add subtitles in English to my 4K video" — concrete instructions get better results.

Max file size is 500MB. Stick to MP4, MOV, AVI, WebM for the smoothest experience.

Export as MP4 with H.264 codec for the best balance of 4K quality and file size.

Common Workflows

Quick edit: Upload → "add subtitles in English to my 4K 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.