Subtitle Generator Ai Free

Get captioned video files ready to post, without touching a single slider. Upload your video files (MP4, MOV, AVI, WebM, up to 500MB), say something like "ge...

Security Scan

The skill's behavior mostly matches a cloud subtitle service, but there are inconsistencies in declared requirements and no trusted source/homepage; it will upload user video files and obtain/use a bearer token (which may be created anonymously), so you should confirm privacy and token storage details before installing.

Purpose & Capability

The skill claims to generate and embed subtitles using a cloud backend, and the SKILL.md describes API endpoints and upload/render flows that align with that purpose. Minor inconsistency: registry metadata lists NEMO_TOKEN as required, but the runtime instructions also describe automatically obtaining an anonymous NEMO_TOKEN if none is present. The SKILL.md frontmatter also declares a config path (~/.config/nemovideo/) whereas the registry metadata provided to the evaluator earlier listed no required config paths — this mismatch should be clarified.

Instruction Scope

Instructions tell the agent to read NEMO_TOKEN from env (or obtain one via an anonymous auth POST), create sessions, upload local files (multipart file posts), poll renders, and handle SSE streams. These actions are within scope for a cloud subtitle/render service. Important runtime behaviors: user video files are uploaded to https://mega-api-prod.nemovideo.ai, and the agent is instructed to include attribution headers and to 'process internally, don't forward' some backend tool results — users should be aware that full video/audio content is transmitted off-device.

Install Mechanism

Instruction-only skill with no install spec or code files — no new binaries are written to disk by an installer. This is the lower-risk installation pattern.

Credentials

The skill declares a single primary credential (NEMO_TOKEN), which fits a cloud API integration; however: (1) the skill will generate an anonymous token itself if NEMO_TOKEN is absent, making the registry's 'required env var' claim somewhat inconsistent, and (2) it's not clear whether the skill will persist tokens or configuration under the mentioned config path. The token grants bearer access to the backend (credits, session management, uploads), so treat it as sensitive.

Persistence & Privilege

always:false (normal). The SKILL.md describes a first-use 'setup' that checks env and requests an anonymous token if needed; it does not explicitly state writing tokens to disk, but the frontmatter references a config path which suggests possible local config usage — clarify whether tokens or session IDs are stored persistently and where.

What to consider before installing

Before installing: (1) Verify the skill's publisher/source and find a homepage or documentation — none is provided here. (2) Understand this skill will upload your video/audio to https://mega-api-prod.nemovideo.ai; do not use it with sensitive or private footage until you confirm the service's privacy/retention policy. (3) Clarify token handling: do you need to provide NEMO_TOKEN, will the skill store the anonymous token on disk (e.g., ~/.config/nemovideo/), and how long is it valid? (4) Test with non-sensitive sample videos first. (5) If you require stronger guarantees, request a published homepage, privacy policy, and source code or a vetted upstream release before granting any credentials or using real data.

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:

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

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.

Subtitle Generator AI Free — Generate and Embed Video 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 add them as burned-in captions — the backend processes it in about 30-60 seconds and hands you a 1080p MP4.

Tip: shorter clips under 5 minutes produce the most accurate subtitle timing.

Matching Input to Actions

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

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

Header	Value
X-Skill-Source	subtitle-generator-ai-free
X-Skill-Version	frontmatter version
X-Skill-Platform	auto-detect: clawhub / cursor / unknown from install path

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.

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.

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.

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

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)

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 "generate subtitles in English and add them as burned-in captions" — 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 add them as burned-in captions" → 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.