Ai Subtitle For Video

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

Security Scan

The skill generally matches its stated purpose (cloud subtitle/rendering) and only needs a single service token, but the instructions contain minor inconsistencies and request behaviors (probing install/config paths and generating/using anonymous tokens) that aren't fully explained and deserve caution.

Purpose & Capability

The name/description (auto-generate and burn-in subtitles via a cloud backend) aligns with the required credential (NEMO_TOKEN) and the API endpoints described. Minor mismatch: top-level description mentions MP4/MOV/AVI/WebM up to 500MB, while the runtime instructions list many more formats (mkv, png, mp3, etc.) — not malicious but inconsistent. Frontmatter metadata also declares a config path (~/.config/nemovideo/) whereas the registry metadata reports no required config paths.

Instruction Scope

Runtime instructions explicitly tell the agent to check the environment for NEMO_TOKEN and, if absent, POST to an anonymous-token endpoint to obtain a token. They also instruct deriving and sending attribution headers and detecting the platform by examining install paths (~/.clawhub/, ~/.cursor/skills/) to set X-Skill-Platform. That implies probing filesystem/install locations (or at least inspecting an install path) beyond simply using the declared environment variable. The steps to create and reuse anonymous tokens and the requirement to keep session_id in memory are reasonable for a cloud service, but filesystem probing and the configPath discrepancy are scope-creep signals that should be clarified.

Install Mechanism

This is an instruction-only skill with no install spec and no code files, so it won't write binaries to disk or download third-party packages. That minimizes installation risk.

Credentials

Only a single service credential (NEMO_TOKEN) is declared as required and is proportionate for a cloud-rendering subtitle service. However, SKILL.md describes generating an anonymous token if NEMO_TOKEN is absent (by POSTing to the service), and frontmatter mentions a config path (~/.config/nemovideo/). The presence of a configPath in the frontmatter but not in the registry metadata is inconsistent and warrants confirmation whether the skill will read that directory.

Persistence & Privilege

The skill does not request always:true, does not modify other skills, and only asks to hold session state (session_id) for the duration of operations. This is typical for a cloud API integration.

What to consider before installing

This skill appears to be a straightforward cloud-based subtitle/renderer that needs one service token (NEMO_TOKEN) to operate. Before installing or enabling it, consider: 1) Confirm whether the skill will read ~/.config/nemovideo/ or inspect install paths on your machine — the SKILL.md suggests platform detection and a configPath but the registry metadata didn't list any config paths. 2) Understand the anonymous-token behavior: if you don't provide NEMO_TOKEN the skill will request a short-lived anonymous token from mega-api-prod.nemovideo.ai; this is expected but you should confirm you trust that domain and the service's privacy policy. 3) Avoid uploading highly sensitive videos to the service until you verify its data retention and privacy terms. 4) Ask the skill author to clarify the configPath/install-path checks and to remove any filesystem probing that isn't necessary. If you need higher assurance, request the skill source or an official homepage and a privacy/security statement from the author before enabling autonomous invocation.

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 subtitles in English and Spanish"

Quick Start Setup

This skill connects to a cloud processing backend. On first use, set up the connection automatically and let the user know ("Connecting...").

Token check: Look for NEMO_TOKEN in the environment. If found, skip to session creation. Otherwise:

• Generate a UUID as client identifier
• POST https://mega-api-prod.nemovideo.ai/api/auth/anonymous-token with X-Client-Id header
• Extract data.token from the response — this is your NEMO_TOKEN (100 free credits, 7-day expiry)

Session: POST https://mega-api-prod.nemovideo.ai/api/tasks/me/with-session/nemo_agent with Bearer auth and body {"task_name":"project"}. Keep the returned session_id for all operations.

Let the user know with a brief "Ready!" when setup is complete. Don't expose tokens or raw API output.

AI Subtitle for Video — Auto-Generate and Burn In Subtitles

This tool takes your video files and runs AI 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 subtitles in English and Spanish to my video — 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 ai subtitle for video, 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.

All calls go to https://mega-api-prod.nemovideo.ai. The main endpoints:

1. Session — POST /api/tasks/me/with-session/nemo_agent with {"task_name":"project","language":"<lang>"}. Gives you a session_id.
2. Chat (SSE) — POST /run_sse with session_id and your message in new_message.parts[0].text. Set Accept: text/event-stream. Up to 15 min.
3. Upload — POST /api/upload-video/nemo_agent/me/<sid> — multipart file or JSON with URLs.
4. Credits — GET /api/credits/balance/simple — returns available, frozen, total.
5. State — GET /api/state/nemo_agent/me/<sid>/latest — current draft and media info.
6. Export — POST /api/render/proxy/lambda with render ID and draft JSON. Poll GET /api/render/proxy/lambda/<id> every 30s for completed status and download URL.

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

Headers are derived from this file's YAML frontmatter. X-Skill-Source is ai-subtitle-for-video, 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).

Every API call needs Authorization: Bearer <NEMO_TOKEN> plus the three attribution headers above. If any header is missing, exports return 402.

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)

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

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.

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 and Spanish to my 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 across platforms and devices.

Common Workflows

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