Ai Subtitle Generator Free

Turn a 3-minute YouTube tutorial video into 1080p captioned video files just by typing what you need. Whether it's adding subtitles to videos for free or qui...

Security Scan

The skill’s claimed purpose (remote subtitle/rendering) matches most of its instructions and the single requested credential (NEMO_TOKEN), but there are small inconsistencies and some behaviors you should explicitly understand before installing (file uploads to a third‑party service, metadata disagreement about config paths, and implicit filesystem probing to determine install path).

Purpose & Capability

The skill advertises server-side subtitle generation and the SKILL.md shows APIs to upload videos, create sessions, and request renders — this aligns with the stated purpose. The required credential (NEMO_TOKEN) is appropriate for access to the described API. However, the SKILL.md frontmatter lists a config path (~/.config/nemovideo/) while the registry metadata earlier reported no required config paths — an internal inconsistency worth clarifying.

Instruction Scope

Runtime instructions explicitly direct the agent to upload user video files and to POST/GET to mega-api-prod.nemovideo.ai endpoints (session creation, upload, SSE chat, render polling). That is expected for this function, but it does mean user media and derived metadata are transmitted off‑device to a third‑party service. The SKILL.md also prescribes deriving an X-Skill-Platform header by inspecting install paths (e.g., ~/.clawhub/ or ~/.cursor/skills/) — that implies the agent might read the filesystem to detect install location, which is not strictly necessary to provide core functionality and should be explained/justified.

Install Mechanism

Instruction-only skill with no install spec or code files — lowest install risk. No downloads or extracted archives are specified.

Credentials

Only NEMO_TOKEN is declared as required (primary credential), which matches the described API usage. The frontmatter also references a config path (~/.config/nemovideo/) that would grant access to local config if the agent reads it — the top-level registry summary listed no required config paths, so that discrepancy should be resolved. The skill advises generating an anonymous token if none is present (reasonable), and it instructs not to print tokens.

Persistence & Privilege

No always:true, no install-time persistence requested, and the skill does not claim to modify other skills or system-wide settings. Autonomous invocation is allowed (platform default) but not a separate concern here.

What to consider before installing

Before installing, understand this will upload your videos (and likely metadata) to mega-api-prod.nemovideo.ai for server-side processing — if your content is sensitive, do not proceed without checking the service's privacy/security terms. Confirm whether you trust the Nemo service and whether you prefer to use an anonymous, short‑lived token (the skill documents how to obtain one). Ask the publisher to resolve the metadata inconsistency about config paths (SKILL.md frontmatter lists ~/.config/nemovideo/ but registry data lists none) and to explain why the agent must detect the install path (that may require reading your home directory). If you want higher assurance, request a hosted homepage, source repository, or code samples so you can verify exactly what data is sent and how tokens are stored/used.

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"
• "generate subtitles in English and add"

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.

AI Subtitle Generator Free — Generate and Embed Video Subtitles

Send me your video files and describe the result you want. The AI subtitle generation runs on remote GPU nodes — nothing to install on your machine.

A quick example: upload a 3-minute YouTube tutorial video, type "generate subtitles in English and add them to my video", and you'll get a 1080p MP4 back in roughly 30-60 seconds. All rendering happens server-side.

Worth noting: shorter clips under 5 minutes generate subtitles noticeably faster.

Matching Input to Actions

User prompts referencing ai 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.

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-generator-free, 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).

Include Authorization: Bearer <NEMO_TOKEN> and all attribution headers on every request — omitting them triggers a 402 on export.

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

Common Workflows

Quick edit: Upload → "generate subtitles in English and add them 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 "generate subtitles in English and add them 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.