Ai Video Editor Generator Free

Get edited video clips 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's claims, required credential (NEMO_TOKEN), and runtime instructions are coherent for a cloud-based AI video editing service; nothing requested appears unrelated to the stated purpose.

Purpose & Capability

Name/description (AI video editing) aligns with the single required credential (NEMO_TOKEN), the declared config path (~/.config/nemovideo/), and the API endpoints the SKILL.md instructs the agent to call. No unrelated credentials or binaries are requested.

Instruction Scope

Instructions drive all traffic to the nemo video backend and describe session creation, SSE messaging, uploads, and exports — all consistent with the purpose. Two points to note: (1) the doc shows upload via multipart '-F "files=@/path"', which implies the agent may need access to local file paths to perform uploads (expected for an uploader, but it does mean the agent could attempt to read files you point to); (2) it requires constructing an X-Skill-Platform value by auto-detecting an install path, which may require reading agent install/runtime paths (minor footprint). The skill explicitly says not to expose tokens or raw API output.

Install Mechanism

No install spec or code files are present (instruction-only), so nothing will be written to disk by an installer. This is the lowest-risk install mechanism.

Credentials

Only NEMO_TOKEN is required (and declared as primary). The SKILL.md documents an anonymous-token flow to obtain an ephemeral token if none is present, and a config path where credentials may be stored — this is proportionate to a cloud editing service. There are no unrelated SECRET/TOKEN requirements.

Persistence & Privilege

always:false and normal autonomous invocation are set. The skill describes creating and reusing a session token and may persist tokens under the declared config path — this is expected and limited in scope. It does not request system-wide or other-skills configuration changes.

Assessment

This skill appears to do what it says: it uploads video to an external nemo video backend, creates sessions, and returns edited files. Before installing or using it, consider these practical safety points: - Videos leave your machine: do not upload sensitive or private footage you wouldn't want stored or processed by an external service. Check nemo's privacy/retention policy before sharing confidential content. - Token behavior: the skill looks for NEMO_TOKEN or will obtain an anonymous token via an API call and may persist it under ~/.config/nemovideo/. If you prefer, create a dedicated/limited account or use a throwaway token. - Local file access: the instructions show uploading via local file paths; the agent will need access only to files you explicitly provide, but be cautious about granting access to arbitrary filesystem locations. - Headers and metadata: the skill auto-adds attribution headers and may try to detect an install path for X-Skill-Platform — ask what exact path info is used if you are concerned about leaking local path details. - External service trust: the skill depends entirely on mega-api-prod.nemovideo.ai. Verify you trust that domain/service before sending content. If any of the above is unacceptable, do not install or avoid uploading sensitive files; otherwise the skill is internally consistent for its stated purpose.

Getting Started

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

Try saying:

• "edit my raw video footage"
• "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.

AI Video Editor Generator Free — Edit and Generate Videos Free

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

Here's a typical use: you send a a 2-minute unedited screen recording, ask for trim the pauses, add transitions, and generate a title card, 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 60 seconds process significantly faster and give cleaner AI results.

Matching Input to Actions

User prompts referencing ai video editor generator 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.

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

Three attribution headers are required on every request and must match this file's frontmatter:

Header	Value
X-Skill-Source	ai-video-editor-generator-free
X-Skill-Version	frontmatter version
X-Skill-Platform	auto-detect: clawhub / cursor / unknown from install path

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

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

Common Workflows

Quick edit: Upload → "trim the pauses, add transitions, and generate a title card" → 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 generate a title card" — 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 all platforms and devices.