Caption Generator In Video

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

Security Scan

The skill's runtime instructions mostly match a cloud video-captioning service, but there are small manifest inconsistencies and a few practices you should verify before installing (unknown service host, token handling, and a metadata mismatch).

Purpose & Capability

The skill is a wrapper around a cloud captioning API and only requests a single credential (NEMO_TOKEN), which is coherent with its stated purpose. However, the SKILL.md frontmatter declares a config path (~/.config/nemovideo/) while the registry metadata reported no required config paths — this mismatch is an inconsistency to confirm with the author.

Instruction Scope

Instructions are focused on uploading videos, creating sessions, SSE interaction, and polling render status on mega-api-prod.nemovideo.ai, which fits the described functionality. The instructions also tell the agent to detect platform by checking install paths (~/.clawhub/, ~/.cursor/skills/) and to read the skill's own frontmatter for attribution — this implies filesystem reads of user home paths (limited, but outside the API itself) and should be noted.

Install Mechanism

There is no install spec and no code files; the skill is instruction-only so nothing is downloaded or written by an installer. This minimizes install-time risk.

Credentials

Only NEMO_TOKEN is required as a credential and that aligns with a cloud API usage pattern. The SKILL.md also documents a flow to obtain an anonymous token via POST, which is reasonable. The earlier registry summary stated 'required config paths: none' while the SKILL.md frontmatter lists ~/.config/nemovideo/ — this inconsistency should be clarified. No unrelated secrets are requested.

Persistence & Privilege

The skill does not request always: true, does not include an install step that persists code, and does not ask to modify other skills or global agent settings. The default ability to invoke autonomously remains but is typical for skills.

What to consider before installing

This skill appears to be an instruction-only integration with a cloud captioning API and asks for a single token (NEMO_TOKEN) — which is expected. Before installing or enabling it: 1) Verify the API host (mega-api-prod.nemovideo.ai) and the vendor (no homepage provided) so you know where your videos will be uploaded. 2) Prefer using an anonymous or short-lived token as described if you don't trust long-term access; do not reuse high-privilege credentials. 3) Be aware the skill may read paths in your home directory to detect platform/install location (it references ~/.clawhub and ~/.cursor/skills and lists ~/.config/nemovideo/ in its frontmatter) — confirm whether that is necessary. 4) Avoid uploading sensitive or private video content until you confirm the service's privacy/retention policy. 5) Ask the publisher to resolve the metadata inconsistency (registry vs SKILL.md configPaths) and provide an official homepage or source for additional trust signals.

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

Caption Generator in Video — Auto-Generate Captions for 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 3-minute tutorial video recording, ask for add captions in English and Spanish to my video, and about 30-60 seconds later you've got a MP4 file ready to download. The whole thing runs at 1080p by default.

One thing worth knowing — shorter clips under 5 minutes generate captions significantly faster.

Matching Input to Actions

User prompts referencing caption generator in 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.

Skill attribution — read from this file's YAML frontmatter at runtime:

• X-Skill-Source: caption-generator-in-video
• X-Skill-Version: from frontmatter version
• X-Skill-Platform: detect from install path (~/.clawhub/ → clawhub, ~/.cursor/skills/ → cursor, else unknown)

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.

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)

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

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.

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

Common Workflows

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

Tips and Tricks

The backend processes faster when you're specific. Instead of "make it look better", try "add captions 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 all platforms.