Github Subtitle Generator

Get captioned video files ready to post, without touching a single slider. Upload your video files (MP4, MOV, AVI, WebM, up to 500MB), say something like "ge...

Security Scan

The skill's runtime instructions mostly match a cloud video-captioning service (Nemovideo) but there are naming/metadata inconsistencies and some behavioral details that warrant caution before installing or uploading files.

Purpose & Capability

The skill clearly implements a cloud video subtitle pipeline (Nemovideo API) and requests a NEMO_TOKEN which is appropriate for that purpose — but the package name 'Github Subtitle Generator' is misleading (no GitHub integration is described). Also the frontmatter in SKILL.md lists a config path (~/.config/nemovideo/) whereas the registry summary showed no required config paths — an internal metadata mismatch.

Instruction Scope

Instructions ask the agent to upload user video files to third-party endpoints, create anonymous tokens if no NEMO_TOKEN exists, save session IDs and poll for job status, and include attribution headers (including an auto-detected X-Skill-Platform derived from install path). These actions are consistent with the stated cloud-rendering purpose but they involve transmitting potentially large and sensitive user files and some environment/installation information to an external service. The SKILL.md also requires inclusion of specific headers that may reveal agent install path/platform.

Install Mechanism

Instruction-only skill with no install spec and no code files — nothing is written to disk by the skill itself. This is the lowest-risk install mechanism.

Credentials

Only NEMO_TOKEN is declared as required, which is proportionate for a third-party video processing API. However SKILL.md behavior to auto-generate an anonymous token (POSTing to the service) means the agent will accept and store a returned token if the environment variable isn't set. The frontmatter also references a config path (~/.config/nemovideo/) which is inconsistent with the registry metadata and should be clarified.

Persistence & Privilege

Skill is not always-included and does not request elevated platform privileges. Autonomous invocation is allowed (default) but not combined with any other high-risk attributes.

What to consider before installing

This skill appears to implement a cloud subtitle service (Nemovideo) and needs a NEMO_TOKEN or will create an anonymous token for you; that is coherent with its stated function. However: (1) the name mentions GitHub but nothing in the instructions touches GitHub — ask the publisher why the name includes 'Github'; (2) the SKILL.md wants you to upload video files to mega-api-prod.nemovideo.ai — only upload non-sensitive content unless you trust that service and its privacy policy; (3) the frontmatter references a config path (~/.config/nemovideo/) but the registry metadata did not — ask for clarification what, if anything, the skill will read or write on disk; (4) the skill requires adding headers that may reveal the agent's install path/platform — consider whether you want to expose that info. Because the skill's source is unknown and there's no homepage, consider requesting provenance or running this only with throwaway test content (or declining) until the owner and exact behavior are verified.

Getting Started

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

Try saying:

• "generate my video files"
• "export 1080p MP4"
• "generate subtitles and export as SRT"

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.

GitHub Subtitle Generator — Generate Subtitles for Videos

Drop your 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 tutorial screen recording, ask for generate subtitles and export as SRT with burned-in captions, 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 — shorter clips under 5 minutes produce more accurate subtitle timing.

Matching Input to Actions

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

Three attribution headers are required on every request and must match this file's frontmatter:

Header	Value
X-Skill-Source	github-subtitle-generator
X-Skill-Version	frontmatter version
X-Skill-Platform	auto-detect: clawhub / cursor / unknown from install path

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

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)

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

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.

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 → "generate subtitles and export as SRT with burned-in captions" → 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 "generate subtitles and export as SRT with burned-in captions" — 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 GitHub READMEs and YouTube.