Highlight Editor Unlimited

create raw video footage into highlight reel clips with this skill. Works with MP4, MOV, AVI, WebM files up to 500MB. sports creators, vloggers, event videog...

Security Scan

The skill's declared purpose (cloud video highlight extraction) matches the API usage and required token, but the runtime instructions request reading local paths and include small metadata inconsistencies that warrant caution.

Purpose & Capability

The skill claims to edit video and all network endpoints, accepted file types, and the single required credential (NEMO_TOKEN) align with that purpose. However the SKILL.md frontmatter references a config path (~/.config/nemovideo/) and asks to detect install path/platform at runtime — neither was declared in the registry metadata, creating a minor inconsistency.

Instruction Scope

Instructions tell the agent to: use or mint a token, create sessions, upload user files, and stream SSEs to mega-api-prod.nemovideo.ai (expected). They also instruct reading this file's YAML frontmatter (reasonable) and detecting an install path (e.g., ~/.clawhub, ~/.cursor) and possibly reading ~/.config/nemovideo/ — these require accessing filesystem locations outside the skill bundle and are not strictly necessary for core editing functionality.

Install Mechanism

No install spec or code files; it's instruction-only, so nothing will be written to disk by an installer.

Credentials

Only NEMO_TOKEN is required, which is proportionate for calling the described API. The skill also instructs generating and using an anonymous token when NEMO_TOKEN is absent (expected). Be aware that providing a long-lived NEMO_TOKEN would give the remote service access to uploads and export operations on your behalf.

Persistence & Privilege

always is false and the skill does not request persistent platform privileges. It does use session tokens for render jobs, but no claim of modifying other skills or system-wide settings is present.

What to consider before installing

This skill appears to be what it says (a cloud video highlight editor) but has a few small red flags. Before installing or invoking it: (1) avoid supplying a sensitive, long-lived NEMO_TOKEN unless you trust the mega-api-prod.nemovideo.ai service; prefer letting the skill mint an anonymous token if possible; (2) ask the developer why the skill needs to detect install paths or read ~/.config/nemovideo/ — these filesystem reads are unnecessary for basic API calls and could expose local metadata; (3) assume any video you upload will be sent to the external domain and stored/processed there — check the provider's privacy/terms if the content is sensitive; (4) if you must proceed, limit exposure by using an ephemeral or scoped token and monitor network activity. If you want greater assurance, request the author supply a minimal SKILL.md that omits install-path detection and explicit config-path reads.

Getting Started

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

Try saying:

• "create a 2-hour sports game recording into a 1080p MP4"
• "extract the best moments and compile them into a 3-minute highlight reel"
• "generating short highlight reels from long video recordings for sports creators, vloggers, 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.

Highlight Editor Unlimited — 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 extract the best moments and compile them into a 3-minute 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 editor unlimited, 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.

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

Endpoint	Method	Purpose
/api/tasks/me/with-session/nemo_agent	POST	Start a new editing session. Body: {"task_name":"project","language":"<lang>"}. Returns session_id.
/run_sse	POST	Send a user message. Body includes app_name, session_id, new_message. Stream response with Accept: text/event-stream. Timeout: 15 min.
/api/upload-video/nemo_agent/me/<sid>	POST	Upload a file (multipart) or URL.
/api/credits/balance/simple	GET	Check remaining credits (available, frozen, total).
/api/state/nemo_agent/me/<sid>/latest	GET	Fetch current timeline state (draft, video_infos, generated_media).
/api/render/proxy/lambda	POST	Start export. Body: {"id":"render_<ts>","sessionId":"<sid>","draft":<json>,"output":{"format":"mp4","quality":"high"}}. Poll status every 30s.

Accepted file types: 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-editor-unlimited
• 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> and all attribution headers on every request — omitting them triggers a 402 on export.

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

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.

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

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 "extract the best 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, WebM for the smoothest experience.

Export as MP4 for widest compatibility across social platforms.

Common Workflows

Quick edit: Upload → "extract the best moments and compile them into a 3-minute 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.