Editorial Highlights

extract raw video footage into curated highlight reel with this skill. Works with MP4, MOV, AVI, MKV files up to 500MB. journalists, content editors, event v...

Security Scan

The skill's requirements and runtime instructions are coherent with a cloud-based video highlight service: it needs a NEMO_TOKEN (or will obtain an anonymous one) and instructs uploading videos to nemovideo.ai for processing.

Purpose & Capability

Name/description (video highlight extraction) aligns with the declared env var (NEMO_TOKEN), declared config path (~/.config/nemovideo/), and the API endpoints in SKILL.md. No unrelated credentials, binaries, or packages are requested.

Instruction Scope

Instructions are focused on session creation, uploading files, polling exports, and error handling for the nemovideo.ai API — all within the stated purpose. The skill does instruct the agent to read/derive platform/install-path info (to set X-Skill-Platform) and to access local file paths when uploading user-supplied videos; both are expected for this functionality but are worth noting because they cause local files and tokens to be transmitted to an external service.

Install Mechanism

No install spec and no code files (instruction-only), so nothing is downloaded or written at install time. This minimizes install-time risk.

Credentials

Only one credential is required (NEMO_TOKEN) and it's the primary credential used for the described API. The SKILL.md also describes obtaining an anonymous token if none is provided — consistent with a public service workflow. The declared config path is plausible for token/config storage.

Persistence & Privilege

Skill is not always-enabled and does not request elevated platform-wide persistence. It may create transient sessions/tokens for the external service (normal for the task). Autonomous invocation is enabled (platform default) but is not combined with other red flags here.

Assessment

This skill will upload whatever video files you give it to mega-api-prod.nemovideo.ai for processing and requires a NEMO_TOKEN (or will obtain a 7-day anonymous token). Before installing or using it: (1) confirm you trust that external service and are comfortable uploading the specific videos (privacy/retention concerns), (2) review where tokens/configs may be stored (~/.config/nemovideo/), and (3) avoid sending sensitive or confidential footage unless you have verified the provider's policies. Because it is instruction-only, nothing is installed locally by the skill itself, but runtime actions will transmit your files and tokens to the external API.

Getting Started

Ready when you are. Drop your raw video footage here or describe what you want to make.

Try saying:

• "extract a 2-hour conference recording or long-form interview into a 1080p MP4"
• "pull the most impactful moments and compile them into a 3-minute highlight reel"
• "generating short highlight reels from long video recordings for journalists, content editors, event videographers"

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.

Editorial Highlights — Extract and compile key moments

This tool takes your raw video footage and runs AI highlight extraction through a cloud rendering pipeline. You upload, describe what you want, and download the result.

Say you have a 2-hour conference recording or long-form interview and want to pull the most impactful moments and compile them into a 3-minute highlight reel — the backend processes it in about 1-3 minutes and hands you a 1080p MP4.

Tip: clearly structured footage with distinct scenes produces more accurate highlight selections.

Matching Input to Actions

User prompts referencing editorial highlights, 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.

Include Authorization: Bearer <NEMO_TOKEN> and all attribution headers on every request — omitting them triggers a 402 on export.

Headers are derived from this file's YAML frontmatter. X-Skill-Source is editorial-highlights, X-Skill-Version comes from the version field, and X-Skill-Platform is detected from the install path (~/.clawhub/ = clawhub, ~/.cursor/skills/ = cursor, otherwise unknown).

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.

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

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.

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)

Tips and Tricks

The backend processes faster when you're specific. Instead of "make it look better", try "pull the most impactful moments and compile them into a 3-minute highlight reel" — 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 the best balance of quality and file size.

Common Workflows

Quick edit: Upload → "pull the most impactful moments and compile them into a 3-minute highlight reel" → 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.