Add Subtitle To Video Imovie

Turn a 3-minute iMovie exported video clip into 1080p captioned video files just by typing what you need. Whether it's adding subtitles to iMovie videos or q...

Security Scan

The skill's instructions mostly match a cloud-based subtitle workflow, but there are provenance and metadata inconsistencies plus privacy implications (uploads to an external, unverified service) that warrant caution.

Purpose & Capability

The name and description claim cloud subtitle rendering for iMovie exports and the SKILL.md details API endpoints and workflows that align with that purpose. However the project has no source/homepage and the backend domain (mega-api-prod.nemovideo.ai) is unverified in the registry metadata, which reduces trust in provenance.

Instruction Scope

Runtime instructions are explicit and confined to the stated task: check/use NEMO_TOKEN, optionally obtain an anonymous token, create a session, upload videos, use SSE for edits, and request renders. This requires uploading user video content and metadata to a third-party cloud service (privacy/consent implications). The instructions also require constructing attribution headers and auto-detecting an install platform — minor local environment probing but not excessive.

Install Mechanism

Instruction-only skill with no install spec or code files; nothing is written to disk by an installer step. This is the lowest-risk install mechanism.

Credentials

The only declared credential is NEMO_TOKEN (primaryEnv), which is appropriate for a cloud API. However the SKILL.md frontmatter mentions a config path (~/.config/nemovideo/) while the registry metadata lists no required config paths — this mismatch is inconsistent and suggests the skill may read local config files not declared in the registry. Also the skill will create/obtain an anonymous token if no NEMO_TOKEN is present, which means it may store/handle tokens at runtime.

Persistence & Privilege

always:false and no install hooks are declared. The skill does not request system-wide persistence or modification of other skills. It will, however, create sessions and hold session IDs/tokens for the rendering workflow (runtime state), which is expected for this task.

What to consider before installing

This skill forwards uploaded videos and metadata to an external cloud API (mega-api-prod.nemovideo.ai) for processing and uses a bearer token (NEMO_TOKEN). Before installing: 1) Confirm the service/source (there's no homepage or repo listed). 2) Understand that any video you upload will leave your device and may be stored or processed on that provider's infrastructure. 3) Note the frontmatter mentions a local config path (~/.config/nemovideo/) but the registry did not declare it — ask the publisher whether the skill will read/write local config files or cached tokens. 4) If you want to proceed, prefer providing a limited-scope token or using the anonymous token option; avoid uploading sensitive content. 5) If you need higher assurance, request publisher provenance, privacy policy, and a documented behavior for token storage/rotation.

Getting Started

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

Try saying:

• "add a 3-minute iMovie exported video clip into a 1080p MP4"
• "add subtitles to my video in English"
• "adding subtitles to iMovie videos for iMovie users"

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.

Add Subtitle to Video iMovie — Add Captions to iMovie Videos

Drop your video clips in the chat and tell me what you need. I'll handle the subtitle generation on cloud GPUs — you don't need anything installed locally.

Here's a typical use: you send a a 3-minute iMovie exported video clip, ask for add subtitles to my video in English, and about 30-60 seconds later you've got a MP4 file ready to download. The whole thing runs at 1080p by default.

One thing worth knowing — shorter clips under 5 minutes generate subtitles fastest.

Matching Input to Actions

User prompts referencing add subtitle to video imovie, 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	add-subtitle-to-video-imovie
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.

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)

Backend Response Translation

The backend assumes a GUI exists. Translate these into API actions:

Backend says	You do
"click [button]" / "点击"	Execute via API
"open [panel]" / "打开"	Query session state
"drag/drop" / "拖拽"	Send edit via SSE
"preview in timeline"	Show track summary
"Export button" / "导出"	Execute 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 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 "add subtitles to my video in English" — concrete instructions get better results.

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

Export from iMovie as MP4 before uploading for best compatibility.

Common Workflows

Quick edit: Upload → "add subtitles to my 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.