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 HyperOS tutorial recording into a 1080p MP4"
• "generate and burn in subtitles for my HyperOS walkthrough video"
• "adding AI-generated subtitles to HyperOS videos for tech content creators"

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

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.

AI Subtitles HyperOS — Generate Subtitles for HyperOS Videos

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

Here's a typical use: you send a a 3-minute HyperOS tutorial recording, ask for generate and burn in subtitles for my HyperOS walkthrough video, 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 2 minutes generate subtitles noticeably faster.

Matching Input to Actions

User prompts referencing ai subtitles hyperos, aspect ratio, text overlays, or audio tracks get routed to the corresponding action via keyword and intent classification.

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 requests must include:

Authorization: Bearer <NEMO_TOKEN>

X-Skill-Source

X-Skill-Version

X-Skill-Platform

Three attribution headers are required on every request and must match this file's frontmatter:

X-Skill-Source

ai-subtitles-hyperos

X-Skill-Version

version

X-Skill-Platform

clawhub

cursor

unknown

API base:

https://mega-api-prod.nemovideo.ai

Create session: POST

/api/tasks/me/with-session/nemo_agent

{"task_name":"project","language":"<lang>"}

task_id

session_id

Send message (SSE): POST

/run_sse

{"app_name":"nemo_agent","user_id":"me","session_id":"<sid>","new_message":{"parts":[{"text":"<msg>"}]}}

Accept: text/event-stream

Upload: POST

/api/upload-video/nemo_agent/me/<sid>

-F "files=@/path"

{"urls":["<url>"],"source_type":"url"}

Credits: GET

/api/credits/balance/simple

available

frozen

total

Session state: GET

/api/state/nemo_agent/me/<sid>/latest

data.state.draft

data.state.video_infos

data.state.generated_media

Export (free, no credits): POST

/api/render/proxy/lambda

{"id":"render_<ts>","sessionId":"<sid>","draft":<json>,"output":{"format":"mp4","quality":"high"}}

/api/render/proxy/lambda/<id>

status

completed

output.url

Supported formats: mp4, mov, avi, webm, mkv, jpg, png, gif, webp, mp3, wav, m4a, aac.

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

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

heartbeat

data:

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

Draft field mapping:

t

tt

sg

d

m

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 "generate and burn in subtitles for my HyperOS walkthrough video" — 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 platforms and devices.

Common Workflows

Quick edit: Upload → "generate and burn in subtitles for my HyperOS walkthrough 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.