Review Editor

Get polished review clips ready to post, without touching a single slider. Upload your recorded video footage (MP4, MOV, AVI, WebM, up to 500MB), say somethi...

Security Scan

The skill's requirements and runtime instructions align with its stated purpose (remote AI video editing) and request only a single service token and a small config path; nothing requested appears unrelated or excessive.

Purpose & Capability

The skill is a remote review-video editor and only requires a service token (NEMO_TOKEN) and a config directory (~/.config/nemovideo/) which is coherent with calling a remote nemovideo.ai API and storing session state. No unrelated cloud or system credentials are requested.

Instruction Scope

SKILL.md instructs the agent to connect to the nemovideo backend, upload user video files, create/refresh anonymous tokens if NEMO_TOKEN is absent, create and reuse sessions, poll render status, and return a download URL. It does not instruct reading arbitrary local files or other environment variables. It does instruct reading the skill's own frontmatter and detecting install path for attribution — reasonable for header metadata.

Install Mechanism

Instruction-only skill with no install spec or external downloads; this minimizes disk-write and supply-chain risk.

Credentials

Only NEMO_TOKEN is required (primary credential) and a single config path is declared. Generating an anonymous token via the service when no token is present is consistent with a seamless UX. The number and type of credentials are proportionate to the described functionality.

Persistence & Privilege

The skill is not force-included (always:false) and does not request elevated system privileges or modification of other skills. It will store session identifiers/tokens for use with the remote API (expected behavior for a remote editing service).

Assessment

What to consider before installing: - This skill uploads your video files to a remote service (mega-api-prod.nemovideo.ai) for processing. Do not upload sensitive or private footage unless you trust that service and have reviewed its privacy/security terms. - If you do not set NEMO_TOKEN, the skill will automatically request an anonymous token from the service (100 free credits, expires in ~7 days). That token is a bearer credential and can be used to access the service while valid — treat it like a password. If you prefer control, create and set your own NEMO_TOKEN instead of allowing automatic anonymous-token creation. - The skill may persist session state (session_id, possibly tokens) under the declared config path (~/.config/nemovideo/). If you are concerned about leftover credentials, check and clear that directory after use. - This is an instruction-only skill (no local code install), so the main risk is network activity and data sharing with the remote API rather than local code execution. Verify you trust the nemovideo.ai endpoint before uploading content. - No scan findings were present (no code to analyze), but absence of findings only means there is no local code to scan; it does not replace reviewing the service's trustworthiness.

Getting Started

Share your recorded video footage and I'll get started on AI review editing. Or just tell me what you're thinking.

Try saying:

• "edit my recorded video footage"
• "export 1080p MP4"
• "cut filler moments, add text overlays"

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.

Review Editor — Edit and Export Review Videos

Send me your recorded video footage and describe the result you want. The AI review editing runs on remote GPU nodes — nothing to install on your machine.

A quick example: upload a 3-minute product unboxing video, type "cut filler moments, add text overlays highlighting key points, and smooth transitions between scenes", and you'll get a 1080p MP4 back in roughly 1-2 minutes. All rendering happens server-side.

Worth noting: keeping your review under 5 minutes speeds up processing and keeps viewer retention higher.

Matching Input to Actions

User prompts referencing review 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.

Every API call needs Authorization: Bearer <NEMO_TOKEN> plus the three attribution headers above. If any header is missing, exports return 402.

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

• X-Skill-Source: review-editor
• X-Skill-Version: from frontmatter version
• X-Skill-Platform: detect from install path (~/.clawhub/ → clawhub, ~/.cursor/skills/ → cursor, else 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

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.

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 "cut filler moments, add text overlays highlighting key points, and smooth transitions between scenes" — 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 YouTube, Instagram, and TikTok.

Common Workflows

Quick edit: Upload → "cut filler moments, add text overlays highlighting key points, and smooth transitions between scenes" → 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.