Best Video Editor Free

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

Security Scan

The skill's stated purpose (cloud video editing) aligns with its instructions, but there are inconsistencies around required credentials and config paths and it will automatically obtain and use tokens and upload user video to an external service — you should confirm those behaviors before installing.

Purpose & Capability

The skill claims to provide cloud-based AI video editing and all runtime instructions target a nemo video backend (session creation, upload, render, SSE). That capability is coherent with the name/description. However, the SKILL.md frontmatter lists a config path (~/.config/nemovideo/) while the registry metadata shown earlier lists no required config paths — this mismatch should be clarified.

Instruction Scope

Runtime instructions will check for NEMO_TOKEN and, if not present, generate an anonymous token by POSTing to https://mega-api-prod.nemovideo.ai and then use that token for all session/upload/render calls. The instructions direct the agent to upload user video files to a remote service and to keep an active session. They do not instruct reading unrelated system files, but they do require network uploads of potentially sensitive user videos and automatic token acquisition; both are material behaviors users should know about.

Install Mechanism

This is an instruction-only skill with no install spec and no code files — it does not write binaries or download archives during install, which reduces installation risk.

Credentials

The only declared environment variable is NEMO_TOKEN (which is sensible for a cloud API). But registry metadata says NEMO_TOKEN is required while the SKILL.md explicitly describes a fallback path that auto-creates an anonymous NEMO_TOKEN if the env var is missing. That inconsistency (required vs auto-generated) is concerning because it affects whether the skill will attempt network calls and create tokens without an explicit user-provided credential. Also the frontmatter's configPaths (implying access to ~/.config/nemovideo/) are not listed in the registry summary — clarify whether the skill will read/write local config files or store tokens there.

Persistence & Privilege

The skill is not always-enabled and uses normal autonomous invocation settings. However, the frontmatter mentions a config path under the user's home directory; if the skill writes tokens or session state to ~/.config/nemovideo/ that gives it persistent presence on disk. The registry listing did not show required config paths, so confirm whether the skill will create or modify files in the user's home directory.

What to consider before installing

This skill will upload your video files to a third-party cloud (mega-api-prod.nemovideo.ai) and will either use a provided NEMO_TOKEN or automatically request an anonymous token for you. Before installing: (1) Confirm you trust nemovideo.ai and its privacy/retention policies for uploaded videos; (2) Ask the publisher to clarify where anonymous tokens are stored (in-memory vs ~/.config/nemovideo/), and whether the skill will write files to your home directory; (3) If you prefer control, provide your own NEMO_TOKEN rather than relying on anonymous token generation; (4) Do not use this skill for highly sensitive or private videos until you verify the service and storage practices. The metadata/registry mismatches (required config paths and token behavior) should be resolved by the author before you proceed.

Getting Started

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

Try saying:

• "edit my raw video clips"
• "export 1080p MP4"
• "trim the pauses, add transitions, and"

Quick Start Setup

This skill connects to a cloud processing backend. On first use, set up the connection automatically and let the user know ("Connecting...").

Token check: Look for NEMO_TOKEN in the environment. If found, skip to session creation. Otherwise:

• Generate a UUID as client identifier
• POST https://mega-api-prod.nemovideo.ai/api/auth/anonymous-token with X-Client-Id header
• Extract data.token from the response — this is your NEMO_TOKEN (100 free credits, 7-day expiry)

Session: POST https://mega-api-prod.nemovideo.ai/api/tasks/me/with-session/nemo_agent with Bearer auth and body {"task_name":"project"}. Keep the returned session_id for all operations.

Let the user know with a brief "Ready!" when setup is complete. Don't expose tokens or raw API output.

Best Video Editor Free — Edit and Export Polished Videos

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

A quick example: upload a 2-minute unedited phone recording, type "trim the pauses, add transitions, and export as a clean MP4", and you'll get a 1080p MP4 back in roughly 1-2 minutes. All rendering happens server-side.

Worth noting: shorter clips under 60 seconds process significantly faster.

Matching Input to Actions

User prompts referencing best video editor free, 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-video-editor-free
X-Skill-Version	frontmatter version
X-Skill-Platform	auto-detect: clawhub / cursor / unknown from install path

Include Authorization: Bearer <NEMO_TOKEN> and all attribution headers on every request — omitting them triggers a 402 on export.

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 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

Common Workflows

Quick edit: Upload → "trim the pauses, add transitions, and export as a clean MP4" → 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 "trim the pauses, add transitions, and export as a clean MP4" — 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 and devices.