Srt Generator

generate video or audio files into downloadable SRT files with this skill. Works with MP4, MOV, AVI, WAV files up to 500MB. YouTubers, podcasters, video edit...

Security Scan

The skill's declared requirements and runtime instructions are coherent with a cloud-based subtitle/video-rendering service: it uses a single service token, uploads media to a remote API, and returns rendered media/SRT files.

Purpose & Capability

Name/description (SRT generation from video/audio) match the instructions: API endpoints, upload, render, export, and credit checks all relate to a cloud render/subtitle pipeline. No unrelated credentials or binaries are requested.

Instruction Scope

Instructions are detailed and focused on the Nemovideo backend. They include steps to check for NEMO_TOKEN, create an anonymous token if missing, create sessions, upload files, stream SSE messages, poll renders, and return download URLs. The skill also reads its YAML frontmatter for attribution and inspects install path to set an X-Skill-Platform header — these are reasonable for attribution but do require access to the skill file/path.

Install Mechanism

No install spec and no code files — instruction-only skill. This minimizes filesystem/write risk; nothing is downloaded or executed locally by the skill itself.

Credentials

Only NEMO_TOKEN is declared as required, which is proportional for a cloud service. One minor inconsistency: SKILL.md documents an automatic anonymous-token flow if NEMO_TOKEN is absent, while registry metadata lists NEMO_TOKEN as required. This is plausible (skill can accept a pre-set token or obtain a short-lived anonymous one) but should be noted.

Persistence & Privilege

Skill is not always-enabled and does not request special platform privileges. There is no instruction to modify other skills or system-wide settings. It does instruct keeping session_id and tokens for operation (expected for remote sessions).

Assessment

This skill is coherent with a cloud subtitle/rendering service, but you should consider privacy and provenance before use: it uploads whatever video/audio you provide to https://mega-api-prod.nemovideo.ai — do NOT upload sensitive or confidential content unless you trust the service and its policies. The skill can auto-create a short-lived anonymous NEMO_TOKEN (100 free credits, 7-day expiry) if you don't supply one; if you do provide a token, consider using a scoped/limited token and removing it from your environment after use. Note the small metadata discrepancies (SKILL.md can obtain tokens automatically while the registry marks NEMO_TOKEN required; YAML frontmatter/config-path reading is used only for attribution). If you need stronger assurance, ask the publisher for a privacy policy, request an official homepage/owner verification, or test with non-sensitive sample files first.

Getting Started

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

Try saying:

• "generate a 10-minute interview video in MP4 format into a 1080p MP4"
• "generate an SRT subtitle file for my video in English"
• "generating SRT subtitle files from video or audio recordings for YouTubers, podcasters, video editors"

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.

SRT Generator — Generate Subtitles from Video

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

A quick example: upload a 10-minute interview video in MP4 format, type "generate an SRT subtitle file for my video in English", and you'll get a 1080p MP4 back in roughly 30-90 seconds. All rendering happens server-side.

Worth noting: cleaner audio with less background noise produces more accurate SRT output.

Matching Input to Actions

User prompts referencing srt generator, 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.

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

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

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

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.

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

Translating GUI Instructions

The backend responds as if there's a visual interface. Map its instructions to API calls:

• "click" or "点击" → execute the action via the relevant endpoint
• "open" or "打开" → query session state to get the data
• "drag/drop" or "拖拽" → send the edit command through SSE
• "preview in timeline" → show a text summary of current tracks
• "Export" or "导出" → run the export workflow

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.

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)

Common Workflows

Quick edit: Upload → "generate an SRT subtitle file for my video in English" → 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.

Tips and Tricks

The backend processes faster when you're specific. Instead of "make it look better", try "generate an SRT subtitle file for my video in English" — concrete instructions get better results.

Max file size is 500MB. Stick to MP4, MOV, AVI, WAV for the smoothest experience.

Export as MP4 for widest compatibility when burning subtitles into the final video.