Best Video Editor Software

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

Security Scan

The skill is internally consistent: it describes a cloud video-editing service and only requires a single service token and network calls to that service — nothing in the instructions requests unrelated credentials or local privileges.

Purpose & Capability

The skill's name/description match the actions in SKILL.md: uploading video files and invoking a remote AI editing API. Requesting a NEMO_TOKEN (the service auth) is proportionate. Minor metadata inconsistency: the YAML frontmatter (in-file metadata) references a config path (~/.config/nemovideo/) while the registry metadata lists no required config paths; this is likely benign but inconsistent.

Instruction Scope

Instructions explicitly send user video files and control messages to https://mega-api-prod.nemovideo.ai (session creation, SSE, uploads, exports). This is expected for a cloud editing service but means user data (videos) will be transmitted to that external service. The instructions also ask the agent to read the skill's YAML frontmatter and to detect install path for an X-Skill-Platform header; those operations imply reading some local metadata/paths (or at least constructing header values) but do not request arbitrary system files or unrelated credentials.

Install Mechanism

There is no install spec and no code shipped with the skill (instruction-only), so nothing will be written or executed locally by an installer. This is the lowest-risk install posture.

Credentials

Only a single service credential (NEMO_TOKEN) is required and is explicitly used to authorize API calls; the instructions also permit acquiring an anonymous temporary token via a public API if NEMO_TOKEN is absent. There are no unrelated SECRET/TOKEN/PASSWORD environment variables requested. Note again the small mismatch where in-file metadata mentions a config path that could be read if present.

Persistence & Privilege

The skill does not request persistent/always-on inclusion, does not modify other skills, and has no install-time hooks. It does not ask to write global agent config or escalate privileges.

Assessment

This skill will upload your video files and related edit requests to an external cloud service (mega-api-prod.nemovideo.ai). That is expected for a cloud video editor, but you should: (1) avoid uploading sensitive/personal videos unless you trust the service and have checked its privacy/retention policy; (2) be aware that if you set NEMO_TOKEN in your environment the skill will use it — only provide tokens you intend to give this service and consider using limited-scope or revocable tokens; (3) note the small metadata inconsistency (config path referenced inside the skill) — it likely only affects header construction and not broad filesystem access, but you can deny access to local config if you want; (4) if you see the skill later request unrelated credentials, local filesystem reads outside its stated config path, or an install script that downloads arbitrary code, do not install and re-check. Confidence would be reduced if the skill later added an installer, downloaded code from an untrusted URL, or requested additional unrelated environment variables.

Getting Started

Got raw video clips to work with? Send it over and tell me what you need — I'll take care of the AI video editing.

Try saying:

• "edit a 3-minute unedited screen recording into a 1080p MP4"
• "trim the pauses, add transitions, and export a clean final cut"
• "editing raw footage into a finished video without manual timeline work for YouTubers, content creators, 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.

Best Video Editor Software — Edit and Export Finished Videos

Drop your raw video clips in the chat and tell me what you need. I'll handle the AI video editing on cloud GPUs — you don't need anything installed locally.

Here's a typical use: you send a a 3-minute unedited screen recording, ask for trim the pauses, add transitions, and export a clean final cut, 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 clips under 2 minutes process significantly faster and give more precise AI cuts.

Matching Input to Actions

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

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

• X-Skill-Source: best-video-editor-software
• X-Skill-Version: from frontmatter version
• X-Skill-Platform: detect from install path (~/.clawhub/ → clawhub, ~/.cursor/skills/ → cursor, else unknown)

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.

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.

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.

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)

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

Tips and Tricks

The backend processes faster when you're specific. Instead of "make it look better", try "trim 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 with H.264 codec for the widest compatibility across platforms.

Common Workflows

Quick edit: Upload → "trim 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.