Getting Started

Got raw video footage to work with? Send it over and tell me what you need — I'll take care of the AI highlight extraction.

Try saying:

• "create a 2-hour sports game recording into a 1080p MP4"
• "pull the best moments and compile them into a 60-second highlight reel"
• "generating short highlight reels from long video recordings for sports creators, event videographers, content marketers"

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.

Highlight Maker — Extract and Export Video Highlights

Drop your raw video footage in the chat and tell me what you need. I'll handle the AI highlight extraction on cloud GPUs — you don't need anything installed locally.

Here's a typical use: you send a a 2-hour sports game recording, ask for pull the best moments and compile them into a 60-second highlight reel, and about 1-2 minutes later you've got a MP4 file ready to download. The whole thing runs at 1080p by default.

One thing worth knowing — shorter source videos produce faster and more accurate highlight detection.

Matching Input to Actions

User prompts referencing highlight maker, 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 calls go to

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

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.

Skill attribution — read from this file's YAML frontmatter at runtime:

• X-Skill-Source

  :

  highlight-maker

• X-Skill-Version

  : from frontmatter

  version

• X-Skill-Platform

  : detect from install path (

  ~/.clawhub/

  →

  clawhub

  ,

  ~/.cursor/skills/

  →

  cursor

  , else

  unknown

  )

Include

Authorization: Bearer <NEMO_TOKEN>

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)

Backend Response Translation

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

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.

Error Handling

?bind=<id>

<id>

Tips and Tricks

The backend processes faster when you're specific. Instead of "make it look better", try "pull the best moments and compile them into a 60-second highlight reel" — 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 social platforms.

Common Workflows

Quick edit: Upload → "pull the best moments and compile them into a 60-second highlight reel" → Download MP4. Takes 1-2 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.