Subtitle Editor

v1.0.0

Skip the learning curve of professional editing software. Describe what you want — add subtitles in English and Spanish with white text and black outline — a...

0· 71·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 francemichaell-15/subtitle-editor.

Previewing Install & Setup.
Prompt PreviewInstall & Setup
Install the skill "Subtitle Editor" (francemichaell-15/subtitle-editor) from ClawHub.
Skill page: https://clawhub.ai/francemichaell-15/subtitle-editor
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 subtitle-editor

ClawHub CLI

Package manager switcher

npx clawhub@latest install subtitle-editor
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
Purpose & Capability
The skill advertises server-side subtitle editing/export and only requires a service token (NEMO_TOKEN) and API calls to a nemovideo.ai backend — these are appropriate for a remote-rendering subtitle service. Note: the SKILL.md frontmatter includes a config path (~/.config/nemovideo/) in its metadata, but the registry metadata shown earlier listed no required config paths; this discrepancy should be clarified but does not itself imply malicious intent.
Instruction Scope
Instructions direct the agent to obtain/use NEMO_TOKEN, create sessions, upload user video files, post SSE messages, and poll for render results — all expected. The doc asks the agent to auto-detect an install path to set X-Skill-Platform which could require inspecting the agent's install location; that's outside the core subtitle task and worth validating (the platform header is an attribution requirement, not a functional necessity). The instructions also tell the agent to persist a session_id/token for the session lifecycle; storing session identifiers is reasonable but confirm where/how they are stored.
Install Mechanism
No install spec and no code files (instruction-only). That minimizes filesystem changes and reduces supply-chain risk.
Credentials
Only a single credential (NEMO_TOKEN) is declared as required and is proportionate to calling the remote API. The frontmatter metadata also references a config path (~/.config/nemovideo/) which was not listed in the registry requirements — this mismatch should be reconciled. No unrelated credentials or system secrets are requested.
Persistence & Privilege
always is false (normal). The skill asks to save session identifiers and to reuse NEMO_TOKEN; this is expected for session-based remote services and does not request elevated or persistent platform privileges.
Assessment
This skill appears to be what it says: a thin wrapper that uploads videos to a nemo-video backend for server-side subtitle editing and rendering. Before installing, confirm: (1) you are comfortable uploading the videos (privacy/retention of content and any PII in audio/transcripts); (2) the API domain (mega-api-prod.nemovideo.ai) is trustworthy for your data; (3) where session tokens and session_id will be stored by your agent (avoid leaking tokens to logs); and (4) reconcile the small metadata mismatch (the SKILL.md frontmatter mentions ~/.config/nemovideo/). Do not provide other unrelated credentials. If you need stronger privacy, avoid uploading sensitive videos to third-party renderers.

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

Runtime requirements

💬 Clawdis
EnvNEMO_TOKEN
Primary envNEMO_TOKEN
latestvk972jge6bmp950nvtc8pj6m5h985d34t
71downloads
0stars
1versions
Updated 5d ago
v1.0.0
MIT-0

Getting Started

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

Try saying:

  • "add my video files"
  • "export 1080p MP4"
  • "add subtitles in English and Spanish"

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.

Subtitle Editor — Add Captions and Export Videos

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

A quick example: upload a 3-minute YouTube tutorial video, type "add subtitles in English and Spanish with white text and black outline", 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.

Matching Input to Actions

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

Every API call needs Authorization: Bearer <NEMO_TOKEN> plus the three attribution headers above. If any header is missing, exports return 402.

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

HeaderValue
X-Skill-Sourcesubtitle-editor
X-Skill-Versionfrontmatter version
X-Skill-Platformauto-detect: clawhub / cursor / unknown from install path

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

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

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

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.

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)

Common Workflows

Quick edit: Upload → "add subtitles in English and Spanish with white text and black outline" → 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 "add subtitles in English and Spanish with white text and black outline" — 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.

Comments

Loading comments...