Subtitle Generator By Link

Turn a YouTube link to a 10-minute tutorial video into 1080p captioned video files just by typing what you need. Whether it's adding subtitles to online vide...

Security Scan

The skill generally matches a subtitle-generation purpose but contains metadata/instruction inconsistencies and instructs the agent to read local paths and send user files/URLs to an external API, so review before installing.

Purpose & Capability

The skill's stated purpose (generate subtitles from a video URL) aligns with contacting an external nemo video API and requiring an API token. However the registry metadata and the SKILL.md disagree: the registry listing shows no required config paths while the skill frontmatter mentions ~/.config/nemovideo/; the registry marks NEMO_TOKEN as required even though the SKILL.md describes an anonymous-token fallback. These mismatches reduce confidence in the declared requirements.

Instruction Scope

The runtime instructions direct the agent to call external endpoints, upload URLs or local files, and poll SSE endpoints — which is expected for this service — but also tell the agent to detect installation platform by inspecting local paths (e.g., ~/.clawhub/, ~/.cursor/skills/) and to read its own frontmatter for attribution headers. Inspecting arbitrary config/install paths for platform attribution is outside the narrow need of subtitle generation and could expose filesystem metadata. The skill will transmit user-provided video URLs and any uploaded local files to an external service (mega-api-prod.nemovideo.ai).

Install Mechanism

No install spec or downloaded code is present; this is an instruction-only skill. That minimizes on-disk install risk because nothing will be fetched by the skill itself at install time.

Credentials

Only one credential is declared (NEMO_TOKEN), which is proportionate to an authenticated API client. However, the SKILL.md explicitly supports creating an anonymous token if NEMO_TOKEN is absent, conflicting with the registry's 'required' designation. The frontmatter also requests a config path (~/.config/nemovideo/) not declared in the registry metadata, so the environment/IO requirements are inconsistent.

Persistence & Privilege

always:false and no install hooks are present. The skill does not request persistent system-wide privileges or to modify other skills' configurations according to the provided instructions.

What to consider before installing

This skill appears to do what it claims (call a nemo video API to generate subtitles), but there are a few things to check before installing or using it: 1) The registry metadata and the SKILL.md disagree about required config paths and whether NEMO_TOKEN is mandatory. Ask the publisher to clarify whether the token is optional or required. 2) The skill will upload videos (or local files) and send them to https://mega-api-prod.nemovideo.ai — do not upload sensitive content unless you trust that service and its privacy policy. 3) The instructions ask the agent to probe local paths (e.g., ~/.clawhub/, ~/.cursor/skills/, ~/.config/nemovideo/) to form attribution headers — consider whether you’re comfortable with that filesystem access. 4) No homepage or publisher contact is provided (source unknown); if you need stronger assurance, request publisher identity, service privacy/terms, or a way to use a limited/test token before providing any production credentials. If you decide to proceed, prefer using a scoped or temporary NEMO_TOKEN (or the anonymous flow) and avoid uploading private data.

Getting Started

Share your video URL link and I'll get started on AI subtitle generation. Or just tell me what you're thinking.

Try saying:

• "generate my video URL link"
• "export 1080p MP4"
• "generate subtitles in English and Spanish"

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.

Subtitle Generator by Link — Generate Subtitles from Video Links

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

Say you have a YouTube link to a 10-minute tutorial video and want to generate subtitles in English and Spanish from this video link — the backend processes it in about 30-90 seconds and hands you a 1080p MP4.

Tip: shorter video links process faster — trim long videos before submitting the URL.

Matching Input to Actions

User prompts referencing subtitle generator by link, 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.

Skill attribution — read from this file's YAML frontmatter at runtime:

• X-Skill-Source: subtitle-generator-by-link
• X-Skill-Version: from frontmatter version
• X-Skill-Platform: detect from install path (~/.clawhub/ → clawhub, ~/.cursor/skills/ → cursor, else unknown)

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.

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.

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 Spanish from this video link" — concrete instructions get better results.

Max file size is 500MB. Stick to YouTube, Vimeo, MP4, 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 Spanish from this video link" → Download MP4. Takes 30-90 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.