Subtitles Generator

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

Security Scan

The skill's requests and runtime instructions are consistent with a cloud subtitle/rendering service: it asks for one service token (NEMO_TOKEN), describes API calls to a single backend, and has no install or unrelated credentials — but there are a few small mismatches and privacy implications you should review before use.

Purpose & Capability

The skill is a cloud-based subtitle/render pipeline and it only requests a service token (NEMO_TOKEN) appropriate for that role. No unrelated binaries or credentials are requested. One inconsistency: the registry metadata summary lists no required config paths while the SKILL.md frontmatter includes a configPaths entry (~/.config/nemovideo/). This is plausibly a minor metadata mismatch but should be clarified.

Instruction Scope

Instructions tell the agent to obtain/send tokens, open sessions, upload user video files, stream SSE responses, poll render status, and include specific attribution headers. These actions are within the expected scope for a cloud render/subtitle service. Two items to note: (1) the skill instructs generating an anonymous token and treating it as NEMO_TOKEN — it does not clearly specify whether that token should be stored persistently or kept in-memory; (2) X-Skill-Platform is to be auto-detected from the install path, which may require reading the agent's install path. Neither is necessarily malicious, but both affect privacy/operation and should be documented.

Install Mechanism

This is an instruction-only skill with no install spec and no code files — lowest install risk. Nothing is downloaded or written by an install step per the package metadata.

Credentials

Only one credential (NEMO_TOKEN) is required, which aligns with the described cloud API usage. The frontmatter's declared config path (~/.config/nemovideo/) is plausible for cached session data but is inconsistent with the registry's 'no config paths' listing. Confirm whether the skill will access that path and whether generated anonymous tokens are persisted there.

Persistence & Privilege

The skill does not request permanent system-wide privileges and 'always' is false. It asks the agent to save a session_id and to handle tokens for API calls, which is expected for a remote-render service. The skill does not instruct changing other skills or global agent settings.

Assessment

This skill appears to do what it says (cloud subtitle + render) and only needs a single API token. Before installing or using it: 1) Verify the backend domain (mega-api-prod.nemovideo.ai) is the service you expect — uploading videos sends potentially sensitive content to that host. 2) Ask the maintainer or check docs how the anonymous NEMO_TOKEN is stored (ephemeral in-memory vs written to ~/.config/nemovideo/) and whether it is reused by other tools. 3) Confirm you’re comfortable with video uploads to a third-party cloud and review retention/privacy policy. 4) Note the required attribution headers — these are harmless but the skill will read install paths to set X-Skill-Platform. 5) Because the skill owner is unknown, prefer testing with non-sensitive videos and a throwaway account/token first. If any of these points are unclear, consider contacting the author or restricting use until clarified.

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 1080p MP4"
• "add captions in English and Spanish"

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.

Subtitles Generator — Generate and Burn In Captions

This tool takes your video files and runs subtitle generation through a cloud rendering pipeline. You upload, describe what you want, and download the result.

Say you have a 3-minute YouTube tutorial video and want to add captions in English and Spanish — the backend processes it in about 30-60 seconds and hands you a 1080p MP4.

Tip: shorter clips under 5 minutes generate subtitles significantly faster.

Matching Input to Actions

User prompts referencing subtitles generator, 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.

Base URL: https://mega-api-prod.nemovideo.ai

Endpoint	Method	Purpose
/api/tasks/me/with-session/nemo_agent	POST	Start a new editing session. Body: {"task_name":"project","language":"<lang>"}. Returns session_id.
/run_sse	POST	Send a user message. Body includes app_name, session_id, new_message. Stream response with Accept: text/event-stream. Timeout: 15 min.
/api/upload-video/nemo_agent/me/<sid>	POST	Upload a file (multipart) or URL.
/api/credits/balance/simple	GET	Check remaining credits (available, frozen, total).
/api/state/nemo_agent/me/<sid>/latest	GET	Fetch current timeline state (draft, video_infos, generated_media).
/api/render/proxy/lambda	POST	Start export. Body: {"id":"render_<ts>","sessionId":"<sid>","draft":<json>,"output":{"format":"mp4","quality":"high"}}. Poll status every 30s.

Accepted file types: mp4, mov, avi, webm, mkv, jpg, png, gif, webp, mp3, wav, m4a, aac.

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

Header	Value
X-Skill-Source	subtitles-generator
X-Skill-Version	frontmatter version
X-Skill-Platform	auto-detect: clawhub / cursor / unknown from install path

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.

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

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

Common Workflows

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

Tips and Tricks

The backend processes faster when you're specific. Instead of "make it look better", try "add captions in English and Spanish" — 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 devices.