Video Editor Free For Windows

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

Security Scan

The skill's requirements and runtime instructions are internally consistent with a cloud-based video editing service: it requires a service token, uploads user video files to the service, and uses that service's REST/SSE endpoints — nothing in the package suggests functionality beyond that.

Purpose & Capability

The skill is presented as a cloud-based video editor for Windows but does not require any Windows-only binaries or OS restrictions, which is reasonable because editing runs on a remote API. The declared primary credential (NEMO_TOKEN) is appropriate for a cloud API. Minor inconsistency: the SKILL.md frontmatter lists a config path (~/.config/nemovideo/) while the registry metadata shown above lists no required config paths.

Instruction Scope

The SKILL.md instructs the agent to upload user-supplied video/audio/image files to https://mega-api-prod.nemovideo.ai and to stream SSE responses. Uploading user media and polling render status are expected for this purpose. The instructions also tell the agent to auto-obtain an anonymous token if NEMO_TOKEN is not present and to store session_id for subsequent requests. The skill asks the agent to derive attribution headers from the skill's YAML frontmatter and detect install path for X-Skill-Platform, which implies the agent will read its install path/metadata — this is plausible but worth noting. There are no instructions to read unrelated system files or additional environment secrets.

Install Mechanism

Instruction-only skill with no install spec or code files — nothing is written to disk by an installer. This is the lowest-risk install model.

Credentials

Only one credential is declared (NEMO_TOKEN), which is proportionate for a remote editing API. However, the SKILL.md both treats NEMO_TOKEN as required and also provides a flow to auto-generate an anonymous token if it's absent; this dual behavior is inconsistent but explainable (it prefers an existing token but can create a short-lived anonymous one). The frontmatter's config path entry is out-of-sync with the registry metadata and should be clarified.

Persistence & Privilege

The skill is not always-enabled and does not request elevated system privileges. It will store session_id (and may retain the anonymous token for the session period) for interacting with the remote API; that is normal for a service client. Autonomous invocation is allowed by default (platform behavior) but this skill does not request persistent system-wide changes.

Assessment

This skill sends any media you provide to an external service (mega-api-prod.nemovideo.ai) and requires a service token (NEMO_TOKEN). That is expected for a cloud video editor, but consider privacy before uploading sensitive videos. The skill can create a short-lived anonymous token (100 free credits, 7 days) if you don't supply NEMO_TOKEN — if you prefer control, set your own token instead of allowing auto-generation. There's a minor metadata mismatch (a config path appears in the skill frontmatter but not in the registry metadata) — you may want to confirm what, if anything, the skill writes to ~/.config/nemovideo/. If you do not trust the nemovideo.ai service or are unsure about its privacy/retention policy, do not upload confidential videos. Otherwise the skill appears coherent with its stated purpose.

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 2-minute screen recording or phone video into a 1080p MP4"
• "trim the clip, add transitions, and export a clean final video"
• "editing and trimming video clips without paid software for Windows PC users"

First-Time Connection

When a user first opens this skill, connect to the processing backend automatically. Briefly let them know (e.g. "Setting up...").

Authentication: Check if NEMO_TOKEN is set in the environment. If it is, skip to step 2.

1. Obtain a free token: Generate a random UUID as client identifier. POST to https://mega-api-prod.nemovideo.ai/api/auth/anonymous-token with header X-Client-Id set to that UUID. The response data.token is your NEMO_TOKEN — 100 free credits, valid 7 days.
2. Create a session: POST to https://mega-api-prod.nemovideo.ai/api/tasks/me/with-session/nemo_agent with Authorization: Bearer <token>, Content-Type: application/json, and body {"task_name":"project","language":"<detected>"}. Store the returned session_id for all subsequent requests.

Keep setup communication brief. Don't display raw API responses or token values to the user.

Video Editor Free for Windows — Edit and Export Videos Online

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 2-minute screen recording or phone video, ask for trim the clip, add transitions, and export a clean final video, 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 3 minutes process significantly faster.

Matching Input to Actions

User prompts referencing video editor free for windows, 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.

Base URL: https://mega-api-prod.nemovideo.ai

Endpoint	Method	Purpose
/api/tasks/me/with-session/nemo_agent	POST	Start a new editing session. Body: {"task_name":"project","language":"<lang>"}. Returns session_id.
/run_sse	POST	Send a user message. Body includes app_name, session_id, new_message. Stream response with Accept: text/event-stream. Timeout: 15 min.
/api/upload-video/nemo_agent/me/<sid>	POST	Upload a file (multipart) or URL.
/api/credits/balance/simple	GET	Check remaining credits (available, frozen, total).
/api/state/nemo_agent/me/<sid>/latest	GET	Fetch current timeline state (draft, video_infos, generated_media).
/api/render/proxy/lambda	POST	Start export. Body: {"id":"render_<ts>","sessionId":"<sid>","draft":<json>,"output":{"format":"mp4","quality":"high"}}. Poll status every 30s.

Accepted file types: mp4, mov, avi, webm, mkv, jpg, png, gif, webp, mp3, wav, m4a, aac.

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

Every API call needs Authorization: Bearer <NEMO_TOKEN> plus the three attribution headers above. If any header is missing, exports return 402.

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

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.

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

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)

Tips and Tricks

The backend processes faster when you're specific. Instead of "make it look better", try "trim the clip, add transitions, and export a clean final video" — 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 Windows media players and platforms.

Common Workflows

Quick edit: Upload → "trim the clip, add transitions, and export a clean final video" → 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.