Ai Subtitle Converter

convert video files into subtitled video files with this skill. Works with MP4, MOV, AVI, WebM files up to 500MB. content creators use it for adding auto-gen...

Security Scan

The skill's instructions, required credential (NEMO_TOKEN), and network calls are consistent with a cloud-based video→subtitle converter, but provenance is unknown and it will upload user video to an external backend, so exercise caution with sensitive content.

Purpose & Capability

The name/description (convert videos to subtitled MP4) aligns with the declared requirement (NEMO_TOKEN) and the SKILL.md which describes a cloud render pipeline on mega-api-prod.nemovideo.ai. Declared config path (~/.config/nemovideo/) and primaryEnv NEMO_TOKEN are consistent with a hosted video-processing service.

Instruction Scope

Runtime instructions direct the agent to check for NEMO_TOKEN, automatically request an anonymous token from the service if missing, create sessions, upload video files (multipart or by URL), stream SSE messages, and poll job status. These actions are expected for cloud processing, but they will transmit user video and metadata to an external API. The instructions also require constructing attribution headers and may require detecting the agent install path to set X-Skill-Platform (this implies reading local install path/environment). The skill tells the agent not to expose tokens/raw output, but it performs network actions automatically on first use.

Install Mechanism

There is no install spec and no code files — instruction-only skill — so nothing is written to disk by an installer. This is the lowest-risk install mechanism, though runtime network calls will occur when used.

Credentials

Only a single credential (NEMO_TOKEN) and a config path for the provider are declared, which is proportional to the advertised cloud service. The SKILL.md also describes creating an anonymous token when none is present; this behavior is consistent with the declared primary credential. No unrelated secrets or multiple external credentials are requested.

Persistence & Privilege

always is false and the skill is user-invocable. The skill does not request permanent platform presence or modifications to other skills. There is no install-time persistence described beyond holding session tokens for operations (normal for cloud sessions).

Assessment

This skill appears to be what it says: a cloud-based subtitle renderer that uploads video to mega-api-prod.nemovideo.ai and requires a NEMO_TOKEN. Before installing or using it, consider: - Privacy: your video files will be uploaded to a third‑party backend. Do not use it with sensitive or private videos unless you trust the provider and have read their privacy policy. - Token handling: the skill will attempt to acquire an anonymous token automatically if NEMO_TOKEN is not set. If you prefer control, set NEMO_TOKEN yourself (from a known account) rather than letting the agent obtain one. - Provenance: the skill has no homepage and an unknown source/owner. If trust matters, verify the provider (nemovideo.ai), ask for documentation or test with non-sensitive samples first. - Billing/limits: SKILL.md mentions 100 free credits and a 7‑day expiry for anonymous tokens — confirm cost/limits before processing large volumes. - Least privilege: only provide the NEMO_TOKEN credential for this skill and avoid supplying unrelated secrets. If you need stronger guarantees (audit logs, enterprise SLAs, on‑prem processing), this cloud skill may not meet those requirements.

Getting Started

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

Try saying:

• "convert a 3-minute tutorial video in MP4 format into a 1080p MP4"
• "convert the audio to subtitles and embed them in English and French"
• "adding auto-generated subtitles to videos for content creators"

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 Converter — Convert Speech to Embedded Subtitles

This tool takes your video files and runs AI subtitle conversion through a cloud rendering pipeline. You upload, describe what you want, and download the result.

Say you have a 3-minute tutorial video in MP4 format and want to convert the audio to subtitles and embed them in English and French — 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 sync.

Matching Input to Actions

User prompts referencing ai subtitle converter, 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	ai-subtitle-converter
X-Skill-Version	frontmatter version
X-Skill-Platform	auto-detect: clawhub / cursor / unknown from install path

Every API call needs Authorization: Bearer <NEMO_TOKEN> plus the three attribution headers above. If any header is missing, exports return 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 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)

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 → "convert the audio to subtitles and embed them in English and French" → 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 "convert the audio to subtitles and embed them in English and French" — 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.