Turn a 2-hour movie file in MP4 format into 1080p subtitled video files just by typing what you need. Whether it's adding subtitles to movies and long-form v...
---
name: movie-subtitle
version: "1.0.0"
displayName: "Movie Subtitle β Generate and Embed Movie Subtitles"
description: >
Turn a 2-hour movie file in MP4 format into 1080p subtitled video files just by typing what you need. Whether it's adding subtitles to movies and long-form videos or quick social content, drop your video files and describe the result you want. No timeline dragging, no export settings β 1-3 minutes from upload to download.
metadata: {"openclaw": {"emoji": "π¬", "requires": {"env": ["NEMO_TOKEN"], "configPaths": ["~/.config/nemovideo/"]}, "primaryEnv": "NEMO_TOKEN", "variant": "short_prompts"}}
---
## Getting Started
> Share your video files and I'll get started on subtitle generation. Or just tell me what you're thinking.
**Try saying:**
- "add my video files"
- "export 1080p MP4"
- "add subtitles in English and French"
### Getting Connected
Before handling any user request, establish a connection to the backend API. Show a brief status like "Connecting...".
**If `NEMO_TOKEN` is in the environment**, use it directly and create a session. Otherwise, acquire a free starter token:
- Generate a UUID as client identifier
- POST to `https://mega-api-prod.nemovideo.ai/api/auth/anonymous-token` with the `X-Client-Id` header
- The response includes a `token` with 100 free credits valid for 7 days β use it as NEMO_TOKEN
**Then create a session** by POSTing to `https://mega-api-prod.nemovideo.ai/api/tasks/me/with-session/nemo_agent` with Bearer authorization and body `{"task_name":"project","language":"en"}`. The `session_id` in the response is needed for all following requests.
Tell the user you're ready. Keep the technical details out of the chat.
# Movie Subtitle β Generate and Embed Movie Subtitles
Send me your video files and describe the result you want. The subtitle generation runs on remote GPU nodes β nothing to install on your machine.
A quick example: upload a 2-hour movie file in MP4 format, type "add subtitles in English and French to my movie", and you'll get a 1080p MP4 back in roughly 1-3 minutes. All rendering happens server-side.
Worth noting: splitting long movies into scenes speeds up subtitle processing.
## Matching Input to Actions
User prompts referencing movie 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`: `movie-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.
### Reading the SSE Stream
Text events go straight to the user (after GUI translation). Tool calls stay internal. Heartbeats and empty `data:` lines mean the backend is still working β show "β³ Still working..." every 2 minutes.
About 30% of edit operations close the stream without any text. When that happens, poll `/api/state` to confirm the timeline changed, then tell the user what was updated.
### 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 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)
```
### 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 β "add subtitles in English and French to my movie" β Download MP4. Takes 1-3 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 "add subtitles in English and French to my movie" β concrete instructions get better results.
Max file size is 500MB. Stick to MP4, MOV, AVI, MKV for the smoothest experience.
Export as MP4 with H.264 codec for widest device compatibility.
don't have the plugin yet? install it then click "run inline in claude" again.