Subtitle Video Professional

add video files into captioned video files with this skill. Works with MP4, MOV, AVI, WebM files up to 500MB. content creators, marketers, educators use it f...

Security Scan

The skill mostly matches its stated purpose (upload a video and get AI-generated subtitles via a Nemovideo API) but has small inconsistencies and a couple of instructions that ask the agent to inspect local install/config paths, so you should review what local data the agent will read and how tokens are handled before installing.

Purpose & Capability

Name/description and the runtime instructions consistently target a cloud subtitle/rendering API (nemovideo). Requesting a single service token (NEMO_TOKEN) is proportionate. However, the skill's frontmatter metadata references a config path (~/.config/nemovideo/) while registry metadata lists no required config paths — this mismatch is unexplained and worth clarifying.

Instruction Scope

SKILL.md directs the agent to obtain/refresh a token via an anonymous POST, create sessions, upload files (multipart or by URL), stream SSE messages, poll render endpoints, and include several custom headers. Most of that is expected for a cloud render service. Concerningly, the headers require auto-detecting the install platform by checking the agent install path (clawhub/cursor/unknown), which requires reading environment/install paths and may expose system layout. The doc also demands including attribution headers that must match frontmatter; combined with the metadata/config-path mismatch, it expands what the agent may read and send.

Install Mechanism

Instruction-only skill with no install spec and no code files. This is low-risk from a code distribution perspective (nothing downloaded or written by an installer).

Credentials

Only one credential (NEMO_TOKEN) is declared as required, which aligns with contacting an external API. However, the frontmatter's configPaths (~/.config/nemovideo/) suggests the skill may try to read local config files (which could contain tokens or other metadata). Registry metadata earlier indicated no required config paths — this inconsistency should be resolved. The anonymous-token flow lessens the need to supply a long-lived secret, which is positive.

Persistence & Privilege

Skill is not marked always:true and is user-invocable. It does instruct storing session_id in-session for job management, which is normal. There is no instruction to modify other skills or global agent settings.

What to consider before installing

This skill appears to be a thin wrapper around an external Nemovideo rendering API and only needs a NEMO_TOKEN to operate. Before installing: 1) Confirm the service domain (mega-api-prod.nemovideo.ai) is legitimate for the provider you expect. 2) Ask the author to reconcile the metadata: the frontmatter lists a config path (~/.config/nemovideo/) but the registry says none — find out whether the skill will read local files and what it will do with them. 3) Prefer using the anonymous-token flow rather than pasting a long-lived secret; if you must supply NEMO_TOKEN, ensure it is scoped/limited and revocable. 4) Be aware the skill may inspect the agent install path to populate the X-Skill-Platform header — if you are uncomfortable exposing system layout, request that this detection be removed or run in a sandbox. 5) Check the provider's privacy/retention policy for uploaded videos (sensitive content may be retained). If the author clarifies the config-path behavior and confirms no extraneous local reads, the skill is reasonable; until then, proceed with caution.

Getting Started

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

Try saying:

• "add my video files"
• "export 1080p MP4"
• "add accurate subtitles in English and"

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.

Subtitle Video Professional — Add Captions and Export Videos

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

Here's a typical use: you send a a 10-minute interview recording in MP4, ask for add accurate subtitles in English and Spanish with professional styling, 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 under 5 minutes produce the most accurate subtitle sync.

Matching Input to Actions

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

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

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.

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)

Common Workflows

Quick edit: Upload → "add accurate subtitles in English and Spanish with professional styling" → 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 accurate subtitles in English and Spanish with professional styling" — 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 all platforms and devices.