Free Bilibili Ai Subtitle

generate Bilibili video files into subtitled video files with this skill. Works with MP4, FLV, AVI, WebM files up to 500MB. Bilibili viewers and content crea...

Security Scan

The skill's declared purpose (AI subtitle generation) mostly matches its runtime instructions, but there are inconsistencies and a few behaviors (auto-requesting tokens, reading install paths, an undeclared config path) that warrant caution before installing or using it with sensitive files or secrets.

Purpose & Capability

The name and description match the actions described (upload video, request cloud render, return MP4). Requesting a NEMO_TOKEN credential is coherent for a cloud service. However, SKILL.md frontmatter lists a config path (~/.config/nemovideo/) whereas the registry metadata reported no required config paths — this mismatch is unexplained. The skill also instructs the agent to detect an install path on disk to populate X-Skill-Platform, which implies filesystem access beyond what was declared.

Instruction Scope

Instructions perform network calls to https://mega-api-prod.nemovideo.ai (session creation, uploads, SSE), will auto-create an anonymous token if NEMO_TOKEN is not set (POST /api/auth/anonymous-token), and instruct the agent to upload local files via multipart (files=@/path). They also direct detecting install path patterns (~/.clawhub/, ~/.cursor/skills/) and reading the skill's YAML frontmatter at runtime. Reading installation paths or arbitrary filesystem locations is not declared in registry requirements and could expose information about the user's environment. The skill claims not to expose tokens, but it necessarily transmits bearer tokens to the remote API.

Install Mechanism

No install spec or additional binaries are required; this is an instruction-only skill, which limits on-disk changes. No remote downloads or archive extraction are specified.

Credentials

Only a single credential (NEMO_TOKEN) is declared as required and is used as the primary credential, which is proportionate to a cloud-rendering service. The SKILL.md will also obtain and use an anonymous token when NEMO_TOKEN is missing. The frontmatter's reference to a config path (~/.config/nemovideo/) is not reflected in the registry requirements and is a minor inconsistency.

Persistence & Privilege

The skill does not request always:true and does not ask to modify other skills or system-wide settings. It keeps per-session session_id values for job management (expected for remote rendering) but does not declare elevated privileges.

What to consider before installing

Before using this skill: 1) Know that your video files and a bearer token will be sent to https://mega-api-prod.nemovideo.ai — do not upload sensitive or private videos to an unknown third party. 2) The skill will create an anonymous token automatically if you don't provide NEMO_TOKEN; consider providing a disposable token if you want control over access and expiry. 3) The SKILL.md expects to detect install paths on your filesystem (~/.clawhub, ~/.cursor) and references a config directory (~/.config/nemovideo/) not listed in the registry metadata — ask the publisher why the skill needs to read those paths. 4) Verify the legitimacy of the nemovideo domain/service before putting your data or permanent credentials at risk. 5) If you need stronger guarantees, request a skill from a known publisher, or prefer an explicit manual workflow where you upload to a vetted service rather than allowing the agent to obtain tokens and upload files automatically.

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 English subtitles for this Bilibili"

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.

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

Drop your Bilibili 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 10-minute Bilibili video in Chinese, ask for generate English subtitles for this Bilibili 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 video segments produce more accurate subtitle timing.

Matching Input to Actions

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

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

• X-Skill-Source: free-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 <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

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.

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)

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

Tips and Tricks

The backend processes faster when you're specific. Instead of "make it look better", try "generate English subtitles for this 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 and other platforms.

Common Workflows

Quick edit: Upload → "generate English subtitles for this 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.