Video Editor Best

Skip the learning curve of professional editing software. Describe what you want — cut the pauses, add transitions, and export a clean final cut — and get po...

Security Scan

Instruction-only skill that talks to a cloud video-editing API and only requires a single API token; overall coherent with its stated purpose but verify token use and file uploads because your videos are sent to an external service.

Purpose & Capability

The skill's name/description (AI video editing) aligns with the runtime instructions: it calls a NemoVideo backend, uploads video files, creates render jobs, polls for results, and returns a download URL. The single required environment variable (NEMO_TOKEN) is consistent with authenticating to that API.

Instruction Scope

Instructions stay within the domain of remote video editing (session creation, SSE messaging, uploads, render/export). The SKILL.md also instructs generating an anonymous token if NEMO_TOKEN is missing and deriving attribution headers from the skill's YAML frontmatter and install path; this requires the agent to read its own metadata and (optionally) detect an install path. That behavior is explainable but worth noting since it causes on-the-fly token acquisition and header construction.

Install Mechanism

No install spec or downloadable code is included (instruction-only). This minimizes risk from arbitrary code downloads or on-disk install steps.

Credentials

Only NEMO_TOKEN is required, which is reasonable for an API-based video editor. However the SKILL.md frontmatter also mentions a config path (~/.config/nemovideo/) for metadata, but the registry metadata shown earlier listed no required configPaths — this mismatch is inconsistent and should be clarified. Also be aware that providing NEMO_TOKEN (or accepting an anonymous token) grants the backend access to any uploads you send.

Persistence & Privilege

The skill does not request always:true or other elevated persistence. It does describe session lifecycle and notes that jobs may orphan if you close the client, but it does not ask to modify other skills or system-wide settings.

Assessment

This skill appears to do what it says: it uploads your video to a NemoVideo cloud API, asks for (or creates) an API token, and returns edited exports. Before installing or invoking it, consider: (1) Any video you upload will go to an external service — don't upload sensitive/private footage unless you trust the provider and their privacy policy. (2) NEMO_TOKEN grants the skill access to your account/credits — only use tokens you control; if you let the skill request an anonymous token, that token has temporary credits and limited lifetime. (3) The SKILL.md references a config path (~/.config/nemovideo/) even though the registry metadata did not — ask the author to clarify whether the skill will read or write files there. (4) If you need higher assurance, request the developer's homepage or documentation, and confirm the exact storage/retention policy for uploaded media and tokens before sending private videos.

Getting Started

Send me your raw video footage and I'll handle the AI video editing. Or just describe what you're after.

Try saying:

• "edit a 2-minute unedited screen recording into a 1080p MP4"
• "cut the pauses, add transitions, and export a clean final cut"
• "trimming and polishing raw footage into a finished video for content creators and marketers"

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.

Video Editor Best — Edit and Export Polished Videos

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

Say you have a 2-minute unedited screen recording and want to cut the pauses, add transitions, and export a clean final cut — the backend processes it in about 1-2 minutes and hands you a 1080p MP4.

Tip: shorter clips under 60 seconds process significantly faster.

Matching Input to Actions

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

Headers are derived from this file's YAML frontmatter. X-Skill-Source is video-editor-best, 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 Codes

• 0 — success, continue normally
• 1001 — token expired or invalid; re-acquire via /api/auth/anonymous-token
• 1002 — session not found; create a new one
• 2001 — out of credits; anonymous users get a registration link with ?bind=<id>, registered users top up
• 4001 — unsupported file type; show accepted formats
• 4002 — file too large; suggest compressing or trimming
• 400 — missing X-Client-Id; generate one and retry
• 402 — free plan export blocked; not a credit issue, subscription tier
• 429 — rate limited; wait 30s and retry 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)

Common Workflows

Quick edit: Upload → "cut the pauses, add transitions, and export a clean final cut" → 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.

Tips and Tricks

The backend processes faster when you're specific. Instead of "make it look better", try "cut the pauses, add transitions, and export a clean final cut" — 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 platforms.