Auto Subtitle Extension

v1.0.0

Skip the learning curve of professional editing software. Describe what you want — extend and auto-generate subtitles for the full video in English — and get...

0· 40·0 current·0 all-time

Install

OpenClaw Prompt Flow

Install with OpenClaw

Best for remote or guided setup. Copy the exact prompt, then paste it into OpenClaw for vynbosserman65/auto-subtitle-extension.

Previewing Install & Setup.
Prompt PreviewInstall & Setup
Install the skill "Auto Subtitle Extension" (vynbosserman65/auto-subtitle-extension) from ClawHub.
Skill page: https://clawhub.ai/vynbosserman65/auto-subtitle-extension
Keep the work scoped to this skill only.
After install, inspect the skill metadata and help me finish setup.
Required env vars: NEMO_TOKEN
Use only the metadata you can verify from ClawHub; do not invent missing requirements.
Ask before making any broader environment changes.

Command Line

CLI Commands

Use the direct CLI path if you want to install manually and keep every step visible.

OpenClaw CLI

Bare skill slug

openclaw skills install auto-subtitle-extension

ClawHub CLI

Package manager switcher

npx clawhub@latest install auto-subtitle-extension
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
medium confidence
Purpose & Capability
Name/description (auto-generate and extend subtitles) match the instructions: uploading video files, creating a session, sending SSE messages, and requesting exports from a remote render API. The required NEMO_TOKEN credential is appropriate for a cloud backend that needs authentication.
Instruction Scope
SKILL.md explicitly instructs the agent to upload user video files and to send API requests (session creation, SSE, upload, export) to mega-api-prod.nemovideo.ai — this is expected for a cloud-rendering subtitle service. It also instructs generation of an anonymous token if NEMO_TOKEN is absent. The file references and network calls are within the stated purpose, but the skill will transmit entire video files to a third-party server (expected but privacy-relevant). The frontmatter requests a config path / install-path detection for the X-Skill-Platform header; registry metadata said no config paths earlier, which is an internal inconsistency to be aware of.
Install Mechanism
Instruction-only skill with no install spec and no code files — lowest install risk. Nothing is downloaded or written to disk by an installer.
Credentials
Only NEMO_TOKEN is declared as required, which is proportionate: the backend needs a token to authenticate requests. The SKILL.md also supports obtaining an anonymous token by calling the service's anonymous-token endpoint when no env var is present. That behavior is reasonable but means the skill can operate without a user-managed secret by creating short-lived anonymous credentials.
Persistence & Privilege
always is false and there is no install-time persistence. The skill asks the backend to create sessions and returns session IDs for job management — expected for a remote processing workflow. It does not request system-wide or cross-skill config changes.
Assessment
This skill is internally consistent for a cloud subtitle/rendering service, but it will upload your video files to https://mega-api-prod.nemovideo.ai and use a bearer token (NEMO_TOKEN) for requests. If you provide your own NEMO_TOKEN you are granting that service access under your account; if you do not provide one the skill will request an anonymous token from the provider and still upload files. Before installing or using: (1) confirm you trust the nemovideo.ai domain and understand their privacy/retention policy for uploaded videos, (2) avoid sending sensitive or private footage unless you accept that it will leave your device, (3) if you prefer, create a limited/throwaway service token rather than using a long-lived account token, and (4) note the small metadata inconsistency about configPaths (harmless but worth verifying with the skill author if you need guarantees about local path access).

Like a lobster shell, security has layers — review code before you run it.

Runtime requirements

📝 Clawdis
EnvNEMO_TOKEN
Primary envNEMO_TOKEN
latestvk979h2gezm9gsf85pgd71eznmx85jd4b
40downloads
0stars
1versions
Updated 1d ago
v1.0.0
MIT-0

Getting Started

Send me your video clips and I'll handle the automatic subtitle generation. Or just describe what you're after.

Try saying:

  • "add a 3-minute interview recorded on a smartphone into a 1080p MP4"
  • "extend and auto-generate subtitles for the full video in English"
  • "automatically generating and extending subtitles across full-length videos for YouTubers, content creators, educators"

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.

Auto Subtitle Extension — Generate and Extend Video Subtitles

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

A quick example: upload a 3-minute interview recorded on a smartphone, type "extend and auto-generate subtitles for the full video in English", and you'll get a 1080p MP4 back in roughly 30-60 seconds. All rendering happens server-side.

Worth noting: shorter clips under 5 minutes process significantly faster and with higher caption accuracy.

Matching Input to Actions

User prompts referencing auto subtitle extension, aspect ratio, text overlays, or audio tracks get routed to the corresponding action via keyword and intent classification.

User says...ActionSkip 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.

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

HeaderValue
X-Skill-Sourceauto-subtitle-extension
X-Skill-Versionfrontmatter version
X-Skill-Platformauto-detect: clawhub / cursor / unknown from install path

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.

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

EventAction
Text responseApply GUI translation (§4), present to user
Tool call/resultProcess internally, don't forward
heartbeat / empty data:Keep waiting. Every 2 min: "⏳ Still working..."
Stream closesProcess 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 saysYou 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

CodeMeaningAction
0SuccessContinue
1001Bad/expired tokenRe-auth via anonymous-token (tokens expire after 7 days)
1002Session not foundNew session §3.0
2001No creditsAnonymous: show registration URL with ?bind=<id> (get <id> from create-session or state response when needed). Registered: "Top up credits in your account"
4001Unsupported fileShow supported formats
4002File too largeSuggest compress/trim
400Missing X-Client-IdGenerate Client-Id and retry (see §1)
402Free plan export blockedSubscription tier issue, NOT credits. "Register or upgrade your plan to unlock export."
429Rate limit (1 token/client/7 days)Retry in 30s once

Common Workflows

Quick edit: Upload → "extend and auto-generate subtitles for the full video in English" → 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 "extend and auto-generate subtitles for the full video in English" — 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 platforms and devices.

Comments

Loading comments...