Ai Video Generator Free Edit

Skip the learning curve of professional editing software. Describe what you want — trim the pauses, add transitions, and generate a title card — and get edit...

Security Scan

The skill's requirements and runtime instructions are internally consistent with a cloud-based AI video-editing service, but a few minor/procedural oddities and the lack of publisher provenance merit caution.

Purpose & Capability

The skill is an AI video editor and declares a single primary credential (NEMO_TOKEN) used for API authorization; the listed API endpoints and workflows (session creation, upload, render, export) match that purpose. One small mismatch: the metadata declares a config path (~/.config/nemovideo/) that isn’t clearly used in the SKILL.md instructions (the skill already relies on NEMO_TOKEN), which is unnecessary but not critical.

Instruction Scope

The SKILL.md gives explicit network interactions (token acquisition, session creation, multipart file uploads, SSE) which are expected for a cloud rendering pipeline. It also asks the agent to read this file's YAML frontmatter for attribution and to detect an install path to set an X-Skill-Platform header — these filesystem checks are peripheral to editing functionality and broaden what the agent will inspect at runtime (install-location detection and reading local skill metadata). The instructions also implicitly require uploading user video files to an external API (expected but privacy-sensitive).

Install Mechanism

No install spec or third-party downloads are declared (instruction-only), so the skill does not drop code or run an installer — this is the lowest-risk install posture.

Credentials

Only one credential (NEMO_TOKEN) is required, which is proportional for an API-backed editor. The metadata's configPaths (~/.config/nemovideo/) is declared but not justified within runtime steps (possible redundancy). The skill will also generate an anonymous token if NEMO_TOKEN is absent, meaning it can make outbound authentication requests on its own.

Persistence & Privilege

The skill is not marked always:true, does not request system-wide config changes in its instructions, and does not ask to modify other skills. It operates per-request and uses ephemeral session tokens.

Assessment

This skill appears to do what it says (cloud video editing), but consider the following before installing: - Using the skill will upload your video files to https://mega-api-prod.nemovideo.ai — do not send sensitive or private footage unless you trust that endpoint and its privacy policies. - The skill will use NEMO_TOKEN if present or obtain an anonymous token automatically; if you provide NEMO_TOKEN, treat it as a real credential and only supply a token you trust for this service. - The skill reads local metadata/install-path info for attribution headers; if you have policy concerns about revealing where skills are installed, note this behavior. - Publisher provenance is missing (no homepage and unknown source). If you need stronger assurance, ask the publisher for a privacy policy, source code, or a known homepage and verify the API domain and ownership before use. - Confidence is medium because this evaluation is based solely on an instruction-only SKILL.md without publisher/site details; additional information about the publisher, domain ownership, or a published privacy/security policy would raise confidence.

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"

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.

AI Video Generator Free Edit — Generate and Edit Videos Free

This tool takes your raw video clips 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 trim the pauses, add transitions, and generate a title card — the backend processes it in about 30-90 seconds and hands you a 1080p MP4.

Tip: shorter clips under 60 seconds process significantly faster and give cleaner AI results.

Matching Input to Actions

User prompts referencing ai video generator free edit, 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.

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

• X-Skill-Source: ai-video-generator-free-edit
• X-Skill-Version: from frontmatter version
• X-Skill-Platform: detect from install path (~/.clawhub/ → clawhub, ~/.cursor/skills/ → cursor, else 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 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 platforms and devices.

Common Workflows

Quick edit: Upload → "trim the pauses, add transitions, and generate a title card" → Download MP4. Takes 30-90 seconds 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.