Best Bilibili Ai Subtitle

---

name: best-bilibili-ai-subtitle version: "1.0.0" displayName: "Best Bilibili AI Subtitle — Auto-generate subtitles for Bilibili videos" description: > Skip the learning curve of professional editing software. Describe what you want — generate accurate Chinese and English subtitles for my Bilibili video automatically — and get subtitled Bilibili videos back in 1-2 minutes. Upload MP4, FLV, AVI, WebM files up to 500MB, and the AI handles AI subtitle generation automatically. Ideal for Bilibili creators who need accurate auto-captions for Chinese and multilingual Bilibili content. metadata: {"openclaw": {"emoji": "🎬", "requires": {"env": ["NEMO_TOKEN"], "configPaths": ["~/.config/nemovideo/"]}, "primaryEnv": "NEMO_TOKEN", "variant": "short_prompts"}}

---

Getting Started

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

Try saying:

"generate my Bilibili video files"

"export 1080p MP4"

"generate accurate Chinese and English subtitles"

Getting Connected

Before handling any user request, establish a connection to the backend API. Show a brief status like "Connecting...".

If NEMO_TOKEN is in the environment, use it directly and create a session. Otherwise, acquire a free starter token:

Generate a UUID as client identifier

POST to https://mega-api-prod.nemovideo.ai/api/auth/anonymous-token with the X-Client-Id header

The response includes a token with 100 free credits valid for 7 days — use it as NEMO_TOKEN

Then create a session by POSTing to https://mega-api-prod.nemovideo.ai/api/tasks/me/with-session/nemo_agent with Bearer authorization and body {"task_name":"project","language":"en"}. The session_id in the response is needed for all following requests.

Tell the user you're ready. Keep the technical details out of the chat.

Best Bilibili AI Subtitle — Auto-generate subtitles for Bilibili videos

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

A quick example: upload a 10-minute Bilibili gaming video in Chinese, type "generate accurate Chinese and English subtitles for my Bilibili video automatically", and you'll get a 1080p MP4 back in roughly 1-2 minutes. All rendering happens server-side.

Worth noting: shorter video segments under 5 minutes produce the most accurate subtitle sync.

Matching Input to Actions

User prompts referencing best bilibili ai subtitle, 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.

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

| Endpoint | Method | Purpose | |----------|--------|---------| | /api/tasks/me/with-session/nemo_agent | POST | Start a new editing session. Body: {"task_name":"project","language":""}. Returns session_id. | | /run_sse | POST | Send 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/ | POST | Upload a file (multipart) or URL. | | /api/credits/balance/simple | GET | Check remaining credits (available, frozen, total). | | /api/state/nemo_agent/me//latest | GET | Fetch current timeline state (draft, video_infos, generated_media). | | /api/render/proxy/lambda | POST | Start export. Body: {"id":"render_","sessionId":"","draft":,"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.

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

X-Skill-Source: best-bilibili-ai-subtitle

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 , X-Skill-Source, X-Skill-Version, X-Skill-Platform. Missing attribution headers will cause export to fail with 402.

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=, 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

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.

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

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 "generate accurate Chinese and English subtitles for my Bilibili video automatically" — concrete instructions get better results.

Max file size is 500MB. Stick to MP4, FLV, AVI, WebM for the smoothest experience.

Export as MP4 for widest compatibility with Bilibili's upload requirements.

Common Workflows

Quick edit: Upload → "generate accurate Chinese and English subtitles for my Bilibili 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.

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

Try saying:

"generate my Bilibili video files"

"export 1080p MP4"

"generate accurate Chinese and English subtitles"

Getting Connected

Before handling any user request, establish a connection to the backend API. Show a brief status like "Connecting...".

If NEMO_TOKEN is in the environment, use it directly and create a session. Otherwise, acquire a free starter token:

Generate a UUID as client identifier

POST to https://mega-api-prod.nemovideo.ai/api/auth/anonymous-token with the X-Client-Id header

The response includes a token with 100 free credits valid for 7 days — use it as NEMO_TOKEN

Then create a session by POSTing to https://mega-api-prod.nemovideo.ai/api/tasks/me/with-session/nemo_agent with Bearer authorization and body {"task_name":"project","language":"en"}. The session_id in the response is needed for all following requests.

Tell the user you're ready. Keep the technical details out of the chat.

Best Bilibili AI Subtitle — Auto-generate subtitles for Bilibili videos

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

A quick example: upload a 10-minute Bilibili gaming video in Chinese, type "generate accurate Chinese and English subtitles for my Bilibili video automatically", and you'll get a 1080p MP4 back in roughly 1-2 minutes. All rendering happens server-side.

Worth noting: shorter video segments under 5 minutes produce the most accurate subtitle sync.