Subtitles Free

Skip the learning curve of professional editing software. Describe what you want — remove the subtitles from this video and give me a clean version — and get...

Security Scan

The skill's behavior mostly matches its subtitle-removal purpose, but there are inconsistencies and privacy surprises (network uploads to a third-party API, a required token that the skill can also generate, and mismatched metadata) you should understand before installing.

Purpose & Capability

The name/description match the runtime instructions: the skill uploads videos to a remote service and asks that service to remove burned-in subtitles. That capability reasonably requires an API token and network access. However, the SKILL.md YAML includes a config path (~/.config/nemovideo/) while the registry metadata lists no required config paths — this mismatch is unexplained and could indicate sloppy packaging or that the skill may read a local config for tokens.

Instruction Scope

The SKILL.md stays within the stated purpose: create a session, upload video files, request renders, poll status, and return download URLs. It does not instruct the agent to read arbitrary unrelated files or secrets. It does, however, instruct the agent to upload users' video files to a third-party endpoint (https://mega-api-prod.nemovideo.ai) — expected for this feature but a significant privacy consideration.

Install Mechanism

This is an instruction-only skill with no install spec and no bundled code — lowest install risk. Nothing is downloaded or written by a packaged installer.

Credentials

The skill declares a single primary credential (NEMO_TOKEN), which fits an API-backed service. But SKILL.md also documents an anonymous-token fallback (POST to /api/auth/anonymous-token), meaning the skill can operate without the user's token. Requiring NEMO_TOKEN in registry metadata while providing a public anonymous path is inconsistent. The YAML's mention of a config path (~/.config/nemovideo/) also suggests the skill may try to read local stored credentials — that is not reflected in the registry's 'required config paths' field.

Persistence & Privilege

The skill does not request 'always: true' and does not attempt to modify other skills or system-wide settings. It can be invoked autonomously (default), which increases blast radius if you install it and allow autonomous runs. Also note: uploads and render jobs are server-side and may persist on the remote service (orphaned jobs if you close the client), which is a privacy/retention concern rather than a technical privilege escalation.

What to consider before installing

This skill legitimately uploads your videos to a third-party service to remove subtitles — if that is acceptable, it appears generally coherent. Before installing: (1) Confirm you trust the remote host (https://mega-api-prod.nemovideo.ai) and review its privacy/retention terms; uploaded videos will leave your device. (2) Be cautious about providing a persistent NEMO_TOKEN; if you prefer, let the skill use the anonymous starter token or create a limited-scope token. (3) Ask the publisher to clarify the mismatch about config paths and why the registry marks NEMO_TOKEN required when the skill can obtain an anonymous token. (4) Test first with non-sensitive/sample videos. If you require strict confidentiality, do not upload private content to this skill.

Getting Started

Send me your video files and I'll handle the subtitle removal. Or just describe what you're after.

Try saying:

• "remove a 3-minute YouTube video with hardcoded captions into a 1080p MP4"
• "remove the subtitles from this video and give me a clean version"
• "removing hardcoded subtitles from videos for video editors, content repurposers, marketers"

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.

Subtitles Free — Remove Subtitles From Videos

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

A quick example: upload a 3-minute YouTube video with hardcoded captions, type "remove the subtitles from this video and give me a clean version", and you'll get a 1080p MP4 back in roughly 30-60 seconds. All rendering happens server-side.

Worth noting: works best when subtitles appear on a plain or low-detail background area.

Matching Input to Actions

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

Headers are derived from this file's YAML frontmatter. X-Skill-Source is subtitles-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.

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 → "remove the subtitles from this video and give me a clean version" → 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 "remove the subtitles from this video and give me a clean version" — 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.