Ai Subtitle Davinci Resolve

add video clips into captioned video files with this skill. Works with MP4, MOV, AVI, MKV files up to 500MB. video editors and YouTubers use it for adding AI...

Security Scan

The skill's requested credential, API endpoints, and runtime instructions are coherent with a cloud-based subtitle/rendering service, but the skill has no source/homepage and will upload user video to a third-party API (privacy risk).

Purpose & Capability

Name/description (AI subtitles for DaVinci Resolve exports) map to the declared requirement (NEMO_TOKEN) and the SKILL.md API calls (upload, render, export). There are no unrelated credentials or unexplained binaries requested.

Instruction Scope

Instructions direct the agent to upload user video files and interact with a remote rendering API at mega-api-prod.nemovideo.ai — this is expected for a cloud subtitle service, but it means user data (videos) will be transmitted off-device. The SKILL.md also instructs deriving headers (e.g., X-Skill-Platform) by detecting an install path, which implies reading runtime environment details; that is plausible but worth noting.

Install Mechanism

No install spec or code is present (instruction-only), so nothing new will be written to disk by an installer. This minimizes install-time risk.

Credentials

Only a single service credential (NEMO_TOKEN) is required and it is used directly for the documented API calls. The skill can also acquire an ephemeral anonymous token from the listed API if the env var is absent — behavior consistent with the stated cloud backend.

Persistence & Privilege

always is false and there are no instructions to modify other skills or global agent config. The skill keeps session_id in-memory for operations, which is normal for a session-based API.

Assessment

This skill appears to do what it claims (cloud subtitle/rendering) and asks only for the service token it needs, but it will upload your videos to an external domain (mega-api-prod.nemovideo.ai). Before installing/use: (1) confirm the service/provider and review any privacy/data-retention policy (no homepage/source provided here), (2) test with non-sensitive videos first, (3) avoid supplying unrelated credentials, (4) be aware the skill can auto-acquire an anonymous token (100 free credits, 7-day expiry) and will include Authorization headers on every request, and (5) ask the publisher for source code or a homepage if you need stronger assurance about where your data goes or how long it is retained.

Getting Started

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

Try saying:

• "add my video clips"
• "export 1080p MP4"
• "generate and burn in English subtitles"

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.

AI Subtitle DaVinci Resolve — Generate Subtitles for Resolve Videos

Send me your video clips 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 DaVinci Resolve export in MP4, type "generate and burn in English subtitles for my DaVinci Resolve video", and you'll get a 1080p MP4 back in roughly 30-60 seconds. All rendering happens server-side.

Worth noting: export your timeline from DaVinci Resolve first, then upload here for instant AI captions.

Matching Input to Actions

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

Headers are derived from this file's YAML frontmatter. X-Skill-Source is ai-subtitle-davinci-resolve, X-Skill-Version comes from the version field, and X-Skill-Platform is detected from the install path (~/.clawhub/ = clawhub, ~/.cursor/skills/ = cursor, otherwise unknown).

Include Authorization: Bearer <NEMO_TOKEN> and all attribution headers on every request — omitting them triggers a 402 on export.

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

Tips and Tricks

The backend processes faster when you're specific. Instead of "make it look better", try "generate and burn in English subtitles for my DaVinci Resolve video" — concrete instructions get better results.

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

Export from DaVinci Resolve as H.264 MP4 for fastest upload and processing.

Common Workflows

Quick edit: Upload → "generate and burn in English subtitles for my DaVinci Resolve video" → 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.