Video Chinese

v1.0.0

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

0· 34·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 mory128/video-chinese.

Previewing Install & Setup.
Prompt PreviewInstall & Setup
Install the skill "Video Chinese" (mory128/video-chinese) from ClawHub.
Skill page: https://clawhub.ai/mory128/video-chinese
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 video-chinese

ClawHub CLI

Package manager switcher

npx clawhub@latest install video-chinese
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
medium confidence
Purpose & Capability
Name/description claim: add Chinese subtitles to videos. Declared requirement: NEMO_TOKEN and a nemovideo config path. SKILL.md calls the nemovideo API endpoints for uploads, session creation, SSE, render/export — these are coherent and proportionate to the purpose.
Instruction Scope
Instructions limit activity to authenticating, creating sessions, uploading video files, streaming SSE, polling state, and starting renders — all expected. The doc asks the agent to 'auto-detect' an install path to set X-Skill-Platform and to persist session_id/token; those imply filesystem or agent-state access (where to store session_id is not specified). Also instructs generating anonymous tokens and using them — which will cause uploads of user videos to an external service. No instructions request unrelated system files or unrelated credentials.
Install Mechanism
Instruction-only skill with no install specification and no code files. Nothing is written to disk by an installer from within the skill bundle itself, which minimizes local install risk.
Credentials
Only a single credential (NEMO_TOKEN) is required and it's the expected credential for the described cloud API. The metadata also references a plausible config path (~/.config/nemovideo/) for session/config storage; both are proportionate to a cloud video processing service.
Persistence & Privilege
always:false (default) and model invocation not disabled — standard. The skill does not request permanent system-wide privileges or modify other skills. It does instruct saving session tokens/state for job tracking, which is normal for this workflow.
Assessment
This skill appears to do what it says: upload your video to the nemovideo cloud to generate Chinese subtitles. Before installing/using it, consider: (1) you will be uploading your video files and session tokens to https://mega-api-prod.nemovideo.ai — verify you trust that domain and service and review its privacy/retention policy; (2) NEMO_TOKEN grants access to the service—use a limited account or rotate the token if possible; (3) anonymous-token generation is supported (temporary, 7-day tokens), but that still uploads data to the provider; (4) the skill has no install scripts (it won’t drop binaries locally), but it implies storing session state — check where your agent stores that; (5) don’t send sensitive or private video content unless you confirm the service’s handling and storage terms. If you want higher assurance, ask the publisher for a homepage/owner contact, or test with non-sensitive sample videos first.

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

Runtime requirements

🀄 Clawdis
EnvNEMO_TOKEN
Primary envNEMO_TOKEN
latestvk97cvynr4ng76veeqv5x2v32sx85mey8
34downloads
0stars
1versions
Updated 13h ago
v1.0.0
MIT-0

Getting Started

Got video files to work with? Send it over and tell me what you need — I'll take care of the Chinese subtitle generation.

Try saying:

  • "add a 3-minute tutorial video in English into a 1080p MP4"
  • "add Chinese subtitles to my video automatically"
  • "adding Chinese subtitles to videos for Chinese-speaking audiences for content creators and marketers"

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.

Video Chinese — Add Chinese Subtitles to Videos

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

Here's a typical use: you send a a 3-minute tutorial video in English, ask for add Chinese subtitles to my video automatically, and about 1-2 minutes 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 generate Chinese subtitles significantly faster.

Matching Input to Actions

User prompts referencing video chinese, 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.

Base URL: https://mega-api-prod.nemovideo.ai

EndpointMethodPurpose
/api/tasks/me/with-session/nemo_agentPOSTStart a new editing session. Body: {"task_name":"project","language":"<lang>"}. Returns session_id.
/run_ssePOSTSend a user message. Body includes app_name, session_id, new_message. Stream response with Accept: text/event-stream. Timeout: 15 min.
/api/upload-video/nemo_agent/me/<sid>POSTUpload a file (multipart) or URL.
/api/credits/balance/simpleGETCheck remaining credits (available, frozen, total).
/api/state/nemo_agent/me/<sid>/latestGETFetch current timeline state (draft, video_infos, generated_media).
/api/render/proxy/lambdaPOSTStart export. Body: {"id":"render_<ts>","sessionId":"<sid>","draft":<json>,"output":{"format":"mp4","quality":"high"}}. Poll status every 30s.

Accepted file types: 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:

HeaderValue
X-Skill-Sourcevideo-chinese
X-Skill-Versionfrontmatter version
X-Skill-Platformauto-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.

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

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)

Tips and Tricks

The backend processes faster when you're specific. Instead of "make it look better", try "add Chinese subtitles to my video automatically" — 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 Chinese video platforms like Bilibili and WeChat.

Common Workflows

Quick edit: Upload → "add Chinese subtitles to my video automatically" → Download MP4. Takes 1-2 minutes 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.

Comments

Loading comments...