Video Subtitle Generator Free

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

Security Scan

The skill's actions (uploading videos and contacting an external nemo API) match its description, but there are small inconsistencies and a few operational instructions that merit caution before installing.

Purpose & Capability

The skill claims to generate and burn-in subtitles via a cloud pipeline; its instructions describe uploading videos and calling a nemo cloud API — this is coherent with the stated purpose. However, the SKILL.md frontmatter lists a config path (~/.config/nemovideo/) while the registry metadata earlier said no required config paths, which is an internal inconsistency.

Instruction Scope

Runtime instructions instruct the agent to (a) use NEMO_TOKEN from the environment or obtain an anonymous token by POSTing to an external endpoint, (b) create sessions and upload video files (multipart or URL), and (c) include attribution headers that require detecting install/platform paths. These behaviors will transmit user video files and metadata to an external service. The platform/install-path auto-detection and requirement to include install-path-derived header means the agent must examine its install path (system state). All of these are plausible for a cloud subtitle service but represent privacy/exfiltration vectors and exceed a purely local operation.

Install Mechanism

No install spec and no code files — instruction-only. This minimizes disk-write/install risk because nothing is downloaded or executed locally by the skill itself.

Credentials

The skill requires a single primary credential (NEMO_TOKEN), which is proportionate for a cloud API. The SKILL.md also provides a fallback to fetch an anonymous token automatically. The earlier registry summary showed no config paths, but the skill frontmatter declares ~/.config/nemovideo/ — this mismatch should be clarified. Otherwise, requested env access is limited and matches the service's needs.

Persistence & Privilege

always:false and no instructions to modify other skills or global agent settings. The skill operates by making API calls; it does not request persistent elevated privileges in the manifest.

What to consider before installing

This skill uploads your video files and related metadata to https://mega-api-prod.nemovideo.ai and will use either your NEMO_TOKEN or an anonymously acquired token it fetches for you. If your videos contain sensitive or proprietary content, do not use a cloud service you don't trust. Clarify the config path discrepancy (~/.config/nemovideo/ appears in SKILL.md frontmatter but not in registry metadata). Review the nemo service’s privacy/terms and confirm where uploaded files are stored and how long they persist. If you prefer local-only subtitle generation, do not install; otherwise accept that the agent will read files you give it and transmit them to an external API. If you plan to supply an existing NEMO_TOKEN, ensure it has appropriate scopes and revoke it if you later stop using the skill.

Getting Started

Ready when you are. Drop your video files here or describe what you want to make.

Try saying:

• "add a 3-minute YouTube tutorial video into a 1080p MP4"
• "generate subtitles in English and sync them to the speech automatically"
• "adding subtitles to videos without paid software 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.

Video Subtitle Generator Free — 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 generate subtitles in English and sync them to the speech automatically — 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 video subtitle generator free, 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.

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

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

Header	Value
X-Skill-Source	video-subtitle-generator-free
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 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

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

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.

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)

Tips and Tricks

The backend processes faster when you're specific. Instead of "make it look better", try "generate subtitles in English and sync them to the speech automatically" — 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 → "generate subtitles in English and sync them to the speech automatically" → 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.