Subtitle Video Hd

Get captioned HD 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 declared needs (a single NEMO_TOKEN) and runtime instructions mostly match a subtitle-rendering service, but there are inconsistencies and a few privacy/transparency concerns you should understand before installing.

Purpose & Capability

The skill's name/description (add subtitles and render HD videos) is consistent with calling a remote video-rendering API and asking for an API token (NEMO_TOKEN). However, the frontmatter in SKILL.md references a config path (~/.config/nemovideo/) which the registry summary lists as 'none' — this metadata mismatch is unexplained and could imply additional filesystem access that isn't documented elsewhere.

Instruction Scope

SKILL.md gives detailed API workflows for creating sessions, uploading videos, SSE streaming, polling render status, and exporting — all within the stated purpose. It explicitly instructs the agent to use an in-environment NEMO_TOKEN or acquire an anonymous token from the external endpoint. One small concern: it tells the agent to 'keep the technical details out of the chat,' which reduces transparency about background actions for end users.

Install Mechanism

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

Credentials

Only one secret is requested (NEMO_TOKEN) which is appropriate for an API-backed service. The skill will also obtain an anonymous token from https://mega-api-prod.nemovideo.ai if no token is present. The earlier metadata reference to a config path (~/.config/nemovideo/) suggests possible additional access to local configuration (not otherwise explained), which warrants caution.

Persistence & Privilege

always:false (no forced/invisible always-on behavior). The skill runs remote API calls and does not request elevated platform privileges or persistent presence beyond normal API usage.

Scan Findings in Context

[no-findings] expected: The static regex scanner had no code files to analyze (instruction-only SKILL.md). That's expected for this kind of skill, but absence of findings is not evidence of safety — the SKILL.md itself is the security surface.

What to consider before installing

What to consider before installing: - This skill will send your video files and an API token (NEMO_TOKEN) to mega-api-prod.nemovideo.ai. Only provide a token if you trust that external service. If you don't have a token, the skill will request a short-lived anonymous token from that same domain. - The SKILL.md contains a metadata line referencing a local config path (~/.config/nemovideo/) though the registry summary did not require it. Ask the author whether the skill will read local config files, and why. If you don't want the agent reading that path, do not install or run the skill. - The skill tells the agent to ‘keep technical details out of the chat,’ which can hide background network activity and make auditing harder. Prefer skills that are transparent about actions they perform. - The package has no homepage and an unknown source/owner ID. If you plan to use this for sensitive or production work, request more provenance (owner, privacy policy, or source code) and verify the API endpoint and token handling. - If you proceed, limit exposure: use an account/token scoped for this service only (not shared credentials), or rely on the anonymous token flow rather than pasting high-privilege secrets into the environment. If you can get the skill source or a clear privacy policy from the author, that information would reduce uncertainty and could move this assessment toward benign.

Getting Started

Got video files to work with? Send it over and tell me what you need — I'll take care of the subtitle generation.

Try saying:

• "add a 3-minute YouTube video in MP4 format into a 1080p MP4"
• "add subtitles in English to my HD video and export in 1080p"
• "adding subtitles to HD videos for YouTube or social media for YouTubers and content creators"

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 HD — Add Subtitles to HD 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 YouTube video in MP4 format, type "add subtitles in English to my HD video and export in 1080p", 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 significantly faster.

Matching Input to Actions

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

Headers are derived from this file's YAML frontmatter. X-Skill-Source is subtitle-video-hd, X-Skill-Version comes from the version field, and X-Skill-Platform is detected from the install path (~/.clawhub/ = clawhub, ~/.cursor/skills/ = cursor, otherwise unknown).

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

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

Tips and Tricks

The backend processes faster when you're specific. Instead of "make it look better", try "add subtitles in English to my HD video and export in 1080p" — 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 HD quality and file size.

Common Workflows

Quick edit: Upload → "add subtitles in English to my HD video and export in 1080p" → 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.