Subtitle Davinci

Skip the learning curve of professional editing software. Describe what you want — add burned-in subtitles to my DaVinci Resolve video in English — and get c...

Security Scan

The skill's requirements and runtime instructions are coherent with a cloud subtitle/rendering service: it needs a NEMO_TOKEN and will upload files to nemovideo.ai for remote processing.

Purpose & Capability

Name/description (add burned-in subtitles via remote render) match the declared credential (NEMO_TOKEN) and the API endpoints in SKILL.md. The declared config path (~/.config/nemovideo/) and primaryEnv (NEMO_TOKEN) are consistent with a client for a remote video-processing service.

Instruction Scope

The SKILL.md instructs the agent to automatically obtain an anonymous token (POST to /api/auth/anonymous-token) if NEMO_TOKEN is not present, create sessions, upload user videos, and poll render endpoints — all expected for this service. It will perform network I/O and upload user-provided media to mega-api-prod.nemovideo.ai. One minor scope note: the skill requires adding an X-Skill-Platform header by auto-detecting install path (could reveal environment/install path info). Otherwise the instructions do not request unrelated system files or extra credentials.

Install Mechanism

This is an instruction-only skill with no install spec and no code files — nothing is written to disk by the skill itself beyond whatever session/state the agent stores. Lowest install risk.

Credentials

Only one credential is required (NEMO_TOKEN), which is appropriate for a third‑party API. Metadata lists a config path (~/.config/nemovideo/) that the SKILL.md does not explicitly instruct reading; this is plausible but slightly inconsistent. No unrelated secrets or multiple service credentials are requested.

Persistence & Privilege

always:false and no install hooks. The skill can be invoked autonomously (platform default), which is expected for skills. It does not request system-wide modifications or other skills' configs.

Assessment

This skill will upload any video files you provide to mega-api-prod.nemovideo.ai and use a NEMO_TOKEN (it can create a short-lived anonymous token automatically if you don't provide one). Before installing or using it, consider: - Do you trust nemovideo.ai with the videos you plan to upload? Uploaded media (and any audio/transcripts) will leave your machine. Avoid sending private/confidential footage. - If you have an account token, treat NEMO_TOKEN like a password — do not reuse a high‑privilege token you use elsewhere. Prefer a throwaway/limited token if possible. - The skill auto-creates tokens and sessions without extra prompts (on first open), and it adds attribution headers including an X-Skill-Platform header that may reveal install path info. If that concerns you, provide a token yourself or avoid the skill. - There is no homepage or public documentation linked in the registry metadata; you may want to verify the service’s privacy, retention, and billing policies before uploading large or sensitive files. If you’re comfortable with those privacy considerations and trust the service, the skill appears coherent for its stated purpose. If not, do not install or provide NEMO_TOKEN / do not upload sensitive media.

Getting Started

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

Try saying:

• "add a 3-minute DaVinci Resolve export into a 1080p MP4"
• "add burned-in subtitles to my DaVinci Resolve video in English"
• "adding subtitles to DaVinci Resolve edited videos for video editors and YouTubers"

First-Time Connection

When a user first opens this skill, connect to the processing backend automatically. Briefly let them know (e.g. "Setting up...").

Authentication: Check if NEMO_TOKEN is set in the environment. If it is, skip to step 2.

1. Obtain a free token: Generate a random UUID as client identifier. POST to https://mega-api-prod.nemovideo.ai/api/auth/anonymous-token with header X-Client-Id set to that UUID. The response data.token is your NEMO_TOKEN — 100 free credits, valid 7 days.
2. Create a session: POST to https://mega-api-prod.nemovideo.ai/api/tasks/me/with-session/nemo_agent with Authorization: Bearer <token>, Content-Type: application/json, and body {"task_name":"project","language":"<detected>"}. Store the returned session_id for all subsequent requests.

Keep setup communication brief. Don't display raw API responses or token values to the user.

Subtitle DaVinci — Add Subtitles to DaVinci Videos

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 DaVinci Resolve export, type "add burned-in subtitles to my DaVinci Resolve video in English", and you'll get a 1080p MP4 back in roughly 30-60 seconds. All rendering happens server-side.

Worth noting: export your DaVinci Resolve project as MP4 before uploading for fastest processing.

Matching Input to Actions

User prompts referencing subtitle davinci, 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":"<lang>"}. 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/<sid>	POST	Upload a file (multipart) or URL.
/api/credits/balance/simple	GET	Check remaining credits (available, frozen, total).
/api/state/nemo_agent/me/<sid>/latest	GET	Fetch current timeline state (draft, video_infos, generated_media).
/api/render/proxy/lambda	POST	Start 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:

Header	Value
X-Skill-Source	subtitle-davinci
X-Skill-Version	frontmatter version
X-Skill-Platform	auto-detect: clawhub / cursor / unknown from install path

Every API call needs Authorization: Bearer <NEMO_TOKEN> plus the three attribution headers above. If any header is missing, exports return 402.

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

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)

Tips and Tricks

The backend processes faster when you're specific. Instead of "make it look better", try "add burned-in subtitles to my DaVinci Resolve video in English" — concrete instructions get better results.

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

Export from DaVinci Resolve using H.264 MP4 for best compatibility with this tool.

Common Workflows

Quick edit: Upload → "add burned-in subtitles to my DaVinci Resolve video in English" → 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.