Ai Subtitle Bangla

Skip the learning curve of professional editing software. Describe what you want — generate Bangla subtitles for my video automatically — and get Bangla capt...

Security Scan

The skill's requirements and runtime instructions are generally consistent with a cloud video subtitle service, but there are a few small metadata/instruction inconsistencies you should be aware of before installing.

Purpose & Capability

The name/description (generate Bangla subtitles) match the declared requirement (NEMO_TOKEN) and the SKILL.md which calls a remote nemovideo.ai API. Minor inconsistency: the registry metadata listed no required config paths, but the SKILL.md frontmatter metadata references a config path (~/.config/nemovideo/). This mismatch is unexplained but could be benign (e.g., optional local config).

Instruction Scope

Instructions stay within the scope of a remote-rendering subtitle service (creating sessions, uploading videos, SSE chat, polling exports). They instruct generating an anonymous token if no NEMO_TOKEN exists, saving session_id, and including attribution headers. Potentially concerning ambiguity: the SKILL.md asks to auto-detect X-Skill-Platform from an install path and references a local config path — this could require the agent to inspect install/config locations on the host. The spec does not explicitly instruct reading arbitrary user files, but the mention of a config path and install path detection creates a non-zero chance the agent may probe the filesystem for that information.

Install Mechanism

Instruction-only skill with no install spec and no code files — lowest-risk install mechanism. Nothing will be downloaded or written by an installer as part of the skill package itself.

Credentials

Only a single credential (NEMO_TOKEN) is required, which is proportional to a cloud API service. The earlier-noted frontmatter reference to ~/.config/nemovideo/ suggests the skill might look for or persist a token/config there; that should be confirmed. No unrelated credentials are requested.

Persistence & Privilege

always:false and no instructions to modify other skills or system-wide settings. Autonomous invocation is allowed (default) but not combined with other high-risk factors.

Assessment

This skill appears to do what it says: call nemovideo.ai endpoints to upload videos and render Bangla subtitles, and it only requires one token (NEMO_TOKEN). Before installing, confirm you trust the endpoint (https://mega-api-prod.nemovideo.ai) and understand what the NEMO_TOKEN allows (upload, render, view credits). Ask the publisher to clarify the discrepancy about ~/.config/nemovideo/ (is it optional local config? will the agent read files there?), and how the anonymous token is stored/rotated if created on your behalf. Avoid providing long-lived secrets you don't trust; if you let the skill generate an anonymous token, treat it as temporary and verify its scope/expiry. If you need stronger assurance, request a privacy/terms URL or a code repo/homepage from the publisher before use.

Getting Started

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

Try saying:

• "add my video files"
• "export 1080p MP4"
• "generate Bangla subtitles for my video"

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.

AI Subtitle Bangla — Generate Bangla Subtitles Automatically

Send me your 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 3-minute Bengali YouTube video, type "generate Bangla subtitles for my video automatically", and you'll get a 1080p MP4 back in roughly 1-2 minutes. All rendering happens server-side.

Worth noting: shorter clips under 5 minutes produce the most accurate Bangla subtitle sync.

Matching Input to Actions

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

All calls go to https://mega-api-prod.nemovideo.ai. The main endpoints:

1. Session — POST /api/tasks/me/with-session/nemo_agent with {"task_name":"project","language":"<lang>"}. Gives you a session_id.
2. Chat (SSE) — POST /run_sse with session_id and your message in new_message.parts[0].text. Set Accept: text/event-stream. Up to 15 min.
3. Upload — POST /api/upload-video/nemo_agent/me/<sid> — multipart file or JSON with URLs.
4. Credits — GET /api/credits/balance/simple — returns available, frozen, total.
5. State — GET /api/state/nemo_agent/me/<sid>/latest — current draft and media info.
6. Export — POST /api/render/proxy/lambda with render ID and draft JSON. Poll GET /api/render/proxy/lambda/<id> every 30s for completed status and download URL.

Formats: 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:

Header	Value
X-Skill-Source	ai-subtitle-bangla
X-Skill-Version	frontmatter version
X-Skill-Platform	auto-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.

Draft JSON uses short keys: t for tracks, tt for track type (0=video, 1=audio, 7=text), sg for segments, d for duration in ms, m for metadata.

Example timeline summary:

Timeline (3 tracks): 1. Video: city timelapse (0-10s) 2. BGM: Lo-fi (0-10s, 35%) 3. Title: "Urban Dreams" (0-3s)

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

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.

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

Common Workflows

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

Tips and Tricks

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