Audio Subtitle Generator

Skip the learning curve of professional editing software. Describe what you want — generate subtitles from the audio and burn them into the video — and get c...

Security Scan

The skill's runtime instructions match its stated purpose (cloud subtitle/rendering) but provenance is unclear and there are small inconsistencies and privacy/metadata concerns you should understand before installing.

Purpose & Capability

The declared primary credential (NEMO_TOKEN) and the API endpoints in SKILL.md are consistent with a cloud subtitle/render service. However the registry metadata shown to you earlier lists no required config paths while the SKILL.md frontmatter declares a config path (~/.config/nemovideo/) — an inconsistency in declared requirements that should be clarified by the publisher. Also there is no homepage or source URL, so the service's provenance is unknown.

Instruction Scope

The SKILL.md instructs the agent to create or use a NEMO_TOKEN, create sessions, upload user media, and poll render endpoints — all within the expected scope of a cloud-rendering subtitle service. It also instructs the agent to read the skill's frontmatter and detect install path (to set X-Skill-Platform), which requires the agent to inspect local paths and the skill file; this is minor scope expansion but not obviously malicious. The instructions explicitly send user media to an external API (mega-api-prod.nemovideo.ai) — expected for this functionality but a user-privacy consideration.

Install Mechanism

This is an instruction-only skill with no install spec and no code files. That minimizes disk persistence and installer risk.

Credentials

Only one credential (NEMO_TOKEN) is required and is appropriate for a remote API. The skill also documents an anonymous-token flow it can perform if NEMO_TOKEN isn't present. The SKILL.md frontmatter references a config path (~/.config/nemovideo/) that was not reflected in the registry metadata — an unexplained discrepancy. No unrelated secrets (AWS, GitHub, etc.) are requested.

Persistence & Privilege

The skill is not always-enabled and does not request elevated platform privileges. It instructs saving of a session_id/token for the interaction lifecycle (normal for a remote service). Nothing indicates it modifies other skills or global agent policies.

What to consider before installing

This skill appears to do what it says (upload your media to a cloud service to generate subtitles), but consider these before installing: (1) media and audio will be uploaded to mega-api-prod.nemovideo.ai — do not use it for sensitive or private content unless you trust the service and have reviewed its privacy policy; (2) there is no homepage or source URL and the registry metadata disagrees with the SKILL.md about a config path — ask the publisher for provenance and clarification on the ~/.config/nemovideo/ usage; (3) NEMO_TOKEN is the only needed credential — avoid supplying other secrets; (4) the skill will read its frontmatter and detect install paths to set headers (this is benign but means it accesses some local metadata); (5) if you need stronger assurances, request the maintainer’s official domain, documentation, and a privacy/terms link, or test with non-sensitive sample media and a throwaway token first.

Getting Started

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

Try saying:

• "generate my audio or video files"
• "export 1080p MP4"
• "generate subtitles from the audio and"

Automatic Setup

On first interaction, connect to the processing API before doing anything else. Show a brief status like "Setting things up...".

Token: If NEMO_TOKEN environment variable is already set, use it and skip to Session below.

Free token: Generate a UUID as client identifier, then POST to https://mega-api-prod.nemovideo.ai/api/auth/anonymous-token with header X-Client-Id: <uuid>. The response field data.token becomes your NEMO_TOKEN (100 credits, 7-day expiry).

Session: POST to https://mega-api-prod.nemovideo.ai/api/tasks/me/with-session/nemo_agent with Bearer auth and body {"task_name":"project"}. Save session_id from the response.

Confirm to the user you're connected and ready. Don't print tokens or raw JSON.

Audio Subtitle Generator — Generate Subtitles from Audio

Drop your audio or video files in the chat and tell me what you need. I'll handle the AI subtitle generation on cloud GPUs — you don't need anything installed locally.

Here's a typical use: you send a a 3-minute podcast audio recording, ask for generate subtitles from the audio and burn them into the video, and about 30-60 seconds later you've got a MP4 file ready to download. The whole thing runs at 1080p by default.

One thing worth knowing — cleaner audio with less background noise produces more accurate subtitles.

Matching Input to Actions

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

All calls go to https://mega-api-prod.nemovideo.ai. The main endpoints:

1. Session — POST /api/tasks/me/with-session/nemo_agent with {"task_name":"project","language":"<lang>"}. Gives you a session_id.
2. Chat (SSE) — POST /run_sse with session_id and your message in new_message.parts[0].text. Set Accept: text/event-stream. Up to 15 min.
3. Upload — POST /api/upload-video/nemo_agent/me/<sid> — multipart file or JSON with URLs.
4. Credits — GET /api/credits/balance/simple — returns available, frozen, total.
5. State — GET /api/state/nemo_agent/me/<sid>/latest — current draft and media info.
6. Export — POST /api/render/proxy/lambda with render ID and draft JSON. Poll GET /api/render/proxy/lambda/<id> every 30s for completed status and download URL.

Formats: mp4, mov, avi, webm, mkv, jpg, png, gif, webp, mp3, wav, m4a, aac.

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

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

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.

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)

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

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.

Error Codes

• 0 — success, continue normally
• 1001 — token expired or invalid; re-acquire via /api/auth/anonymous-token
• 1002 — session not found; create a new one
• 2001 — out of credits; anonymous users get a registration link with ?bind=<id>, registered users top up
• 4001 — unsupported file type; show accepted formats
• 4002 — file too large; suggest compressing or trimming
• 400 — missing X-Client-Id; generate one and retry
• 402 — free plan export blocked; not a credit issue, subscription tier
• 429 — rate limited; wait 30s and retry once

Tips and Tricks

The backend processes faster when you're specific. Instead of "make it look better", try "generate subtitles from the audio and burn them into the video" — concrete instructions get better results.

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

Export as MP4 for widest compatibility across platforms and devices.

Common Workflows

Quick edit: Upload → "generate subtitles from the audio and burn them into the video" → 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.