Best Highlight Editor

Get highlight reel clips ready to post, without touching a single slider. Upload your raw video footage (MP4, MOV, AVI, WebM, up to 500MB), say something lik...

Security Scan

The skill's behavior mostly matches a cloud-based video highlight service, but there are inconsistencies (a claimed config path in the skill frontmatter that isn't declared in registry metadata) and it will auto-create and use anonymous tokens and upload your raw video to an external service — you should confirm the domain and privacy implications before installing.

Purpose & Capability

The name/description (auto-cut highlight reels) aligns with the runtime instructions (upload video, call cloud render APIs, return downloadable MP4). Requesting a single service token (NEMO_TOKEN) is proportionate. However, the SKILL.md frontmatter lists a config path (~/.config/nemovideo/) while the registry metadata lists no required config paths — this mismatch is unexplained.

Instruction Scope

The instructions direct the agent to upload user video files and to POST/GET against https://mega-api-prod.nemovideo.ai for auth, session, upload, SSE, and export flows — which is coherent for this purpose. Two items to note: (1) The agent will auto-generate an anonymous token (by POSTing with a UUID) if NEMO_TOKEN isn't set — that means the skill will perform network authentication and start sessions without an explicit user-provided credential. (2) The frontmatter asks not to show raw API responses or token values to the user, which is a policy choice but reduces transparency. No instructions ask for unrelated system files or other credentials.

Install Mechanism

This is instruction-only with no install spec and no code files — lowest-risk install mechanism. There is nothing being downloaded or written by an installer in the bundle itself.

Credentials

Only NEMO_TOKEN is declared as required, which fits the described API usage. However, because the skill will obtain an anonymous token itself when NEMO_TOKEN is absent, it can operate without user-supplied credentials — users should be aware the skill will call the external service and receive a token it will keep for the session.

Persistence & Privilege

always:false and no install means no forced persistence. But the frontmatter's reference to a config path (~/.config/nemovideo/) suggests the skill might expect to read or write config data — the registry metadata did not declare this. This mismatch could mean the skill was authored to use local config but the registry entry wasn't updated; clarify whether the skill will access local config paths or store session artifacts on disk.

Scan Findings in Context

[no_code_files_to_scan] expected: The package is instruction-only (only SKILL.md). The regex scanner had no code files to analyze, so network and runtime behavior is only visible in the instructions.

What to consider before installing

This skill appears to implement a legitimate cloud video highlight workflow, but before installing: (1) Verify the external domain (mega-api-prod.nemovideo.ai) and the service's privacy/terms — your raw videos will be uploaded there. (2) Be aware the skill will auto-request an anonymous token if you don't provide NEMO_TOKEN, and it will keep a session_id for subsequent calls — if you prefer control, supply your own NEMO_TOKEN rather than relying on anonymous auth. (3) Ask the author to resolve the metadata mismatch about ~/.config/nemovideo/ (confirm whether local config or files will be read/written). (4) Avoid sending sensitive footage until you confirm the service's retention, sharing, and deletion policies. If the author cannot clarify the config-path behavior or domain ownership, treat the skill cautiously.

Getting Started

Share your raw video footage and I'll get started on AI highlight extraction. Or just tell me what you're thinking.

Try saying:

• "create my raw video footage"
• "export 1080p MP4"
• "pull the best moments and compile"

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 is set in the environment. If it is, skip to step 2.

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.

Best Highlight Editor — Auto-cut and export highlight reels

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 gameplay recording or sports match, 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 — trimming your source footage to under 10 minutes speeds up highlight detection significantly.

Matching Input to Actions

User prompts referencing best highlight editor, 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.

All calls go to https://mega-api-prod.nemovideo.ai. The main endpoints:

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.

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

Header	Value
X-Skill-Source	best-highlight-editor
X-Skill-Version	frontmatter version
X-Skill-Platform	auto-detect: clawhub / cursor / unknown from install path

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.

Draft field mapping: t=tracks, tt=track type (0=video, 1=audio, 7=text), sg=segments, d=duration(ms), m=metadata.

Timeline (3 tracks): 1. Video: city timelapse (0-10s) 2. BGM: Lo-fi (0-10s, 35%) 3. Title: "Urban Dreams" (0-3s)

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

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.

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

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.