Ai Video Editor Gratis

Get edited MP4 videos ready to post, without touching a single slider. Upload your raw video footage (MP4, MOV, AVI, WebM, up to 500MB), say something like "...

Security Scan

The skill largely behaves like a cloud-based video editor (uploads footage and uses a backend token) but contains metadata/instruction mismatches and will send user files and tokens to an external service you don't control — verify the service before installing.

Purpose & Capability

The skill's stated purpose (cloud AI video editing) matches the network calls and flows in SKILL.md: it uploads media, creates sessions, and exports rendered MP4s. However the registry metadata and SKILL.md disagree: the registry lists NEMO_TOKEN as a required env var but the runtime instructions include a flow to obtain an anonymous NEMO_TOKEN if not present. The SKILL.md frontmatter also lists a config path (~/.config/nemovideo/) that the registry metadata did not. These mismatches reduce confidence in the declared requirements.

Instruction Scope

Runtime instructions tell the agent to POST user media and other requests to https://mega-api-prod.nemovideo.ai (auth, upload, SSE, render APIs). That is expected for a cloud editor, but it means user videos and derived metadata will be transmitted to a third-party domain. The skill also instructs creating an anonymous token and storing/using a session token, and derives header fields from local install paths (requires detecting install path), implying the agent may read local path information. There are no instructions to access unrelated system secrets, but sending user files and generating/storing tokens externally is high-impact and should be explicit and trusted.

Install Mechanism

No install spec or code files are present; this is instruction-only so nothing is written to disk by an installer. This is lower-risk from install-time code execution, but runtime network activity remains the primary surface.

Credentials

Only one credential (NEMO_TOKEN) is declared as primary and that maps to the backend auth described. However, the declared required env var (NEMO_TOKEN) conflicts with SKILL.md which implements an anonymous-token acquisition flow when NEMO_TOKEN is absent. The skill may therefore work without a pre-provided secret but will call the remote auth endpoint and use the returned token. The behavior is plausible for its purpose but the mismatch in declarations and the automatic token acquisition should be called out to users.

Persistence & Privilege

The skill does not request always:true or other elevated persistent privileges. It is user-invocable and allows model invocation (the platform default). Nothing in the SKILL.md tries to modify other skills or system-wide agent settings.

What to consider before installing

This skill implements a cloud-based editor: it will upload whatever videos you provide and obtain/use a session token (NEMO_TOKEN) from https://mega-api-prod.nemovideo.ai. Two things stand out: (1) the registry metadata says NEMO_TOKEN is required, but the instructions will request an anonymous token if none is present — that discrepancy should be clarified by the publisher; (2) there is no homepage, publisher information, or privacy policy listed, so you cannot verify who will receive your media or how it will be stored. Before installing/use: confirm the service/domain is trustworthy, ask the publisher for a privacy policy and data retention rules, and avoid sending sensitive video content until you have that assurance. If you need to provide your own NEMO_TOKEN, treat it like any API credential and avoid reusing high-privilege keys. Additional publisher metadata (homepage, contact, or source code) would increase confidence.

Getting Started

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

Try saying:

• "edit my raw video footage"
• "export 1080p MP4"
• "trim the footage, 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.

AI Video Editor Gratis — Edit and Export Videos Free

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 smartphone recording and want to trim the footage, add transitions, and include background music — 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 ai video editor gratis, 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 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.

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

SSE Event Handling

Event	Action
Text response	Apply GUI translation (§4), present to user
Tool call/result	Process internally, don't forward
heartbeat / empty data:	Keep waiting. Every 2 min: "⏳ Still working..."
Stream closes	Process final response

~30% of editing operations return no text in the SSE stream. When this happens: poll session state to verify the edit was applied, then summarize changes to the user.

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 "trim the footage, add transitions, and include background music" — 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.

Common Workflows

Quick edit: Upload → "trim the footage, add transitions, and include background music" → 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.