Free Video Editor Windows

v1.0.0

edit raw video clips into edited MP4 clips with this skill. Works with MP4, MOV, AVI, WebM files up to 500MB. Windows users and casual creators use it for tr...

0· 87·0 current·0 all-time

Install

OpenClaw Prompt Flow

Install with OpenClaw

Best for remote or guided setup. Copy the exact prompt, then paste it into OpenClaw for dsewell-583h0/free-video-editor-windows.

Previewing Install & Setup.
Prompt PreviewInstall & Setup
Install the skill "Free Video Editor Windows" (dsewell-583h0/free-video-editor-windows) from ClawHub.
Skill page: https://clawhub.ai/dsewell-583h0/free-video-editor-windows
Keep the work scoped to this skill only.
After install, inspect the skill metadata and help me finish setup.
Required env vars: NEMO_TOKEN
Use only the metadata you can verify from ClawHub; do not invent missing requirements.
Ask before making any broader environment changes.

Command Line

CLI Commands

Use the direct CLI path if you want to install manually and keep every step visible.

OpenClaw CLI

Bare skill slug

openclaw skills install free-video-editor-windows

ClawHub CLI

Package manager switcher

npx clawhub@latest install free-video-editor-windows
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
medium confidence
Purpose & Capability
The skill name and description describe a cloud video editor and the SKILL.md instructs the agent to call a nemo-video backend API for uploads, renders, status, and exports — this is coherent. Minor mismatch: the SKILL.md frontmatter lists a config path (~/.config/nemovideo/) while the registry metadata reported no required config paths. The label 'Windows' in the name is marketing-only; the instructions are platform-agnostic.
Instruction Scope
The instructions are explicit about network calls, uploads (multipart or URL), SSE, polling, and using NEMO_TOKEN; these are expected for a cloud editor. Potential scope-to-watch: the spec asks the agent to 'auto-detect' X-Skill-Platform from an install path (which could require inspecting environment/install paths) and instructs multipart uploads using file paths — the agent will need to access uploaded file paths. There is no instruction to read unrelated system credentials or files.
Install Mechanism
No install spec or code is provided (instruction-only). This minimizes on-disk risk; nothing is downloaded or executed by an installer in the skill bundle.
Credentials
Only one declared credential (NEMO_TOKEN / primaryEnv) is required by the skill, which is proportionate for an API-backed service. The SKILL.md also references a config directory (~/.config/nemovideo/) in frontmatter; the registry metadata did not list any config paths — this inconsistency should be clarified. The skill will create an anonymous token if NEMO_TOKEN is absent, which means it will call an external auth endpoint to obtain a token.
Persistence & Privilege
The skill is not marked 'always' and uses default autonomous invocation settings. It does not request system-wide persistent privileges, and there's no install-time modification of other skills declared in the manifest.
Assessment
This skill appears to be a straightforward wrapper for a nemo-video cloud editing API and needs a single token (NEMO_TOKEN) to operate; if you do not provide a token it will obtain an anonymous token from https://mega-api-prod.nemovideo.ai before uploading files. Before installing or using it: 1) Confirm you trust the nemo-video backend domain (uploads and rendered videos are sent to that external service). 2) If privacy is a concern, avoid uploading sensitive or proprietary footage since files will leave your machine. 3) Ask the publisher to clarify the config-path discrepancy (~/.config/nemovideo/ appears in the SKILL.md but not in registry metadata) and how X-Skill-Platform auto-detection works (it may require inspecting an install path). 4) Prefer supplying your own NEMO_TOKEN if you want tighter control over account access and retention. If any of these points are unacceptable or unanswered, test with non-sensitive sample files first or do not use the skill.

Like a lobster shell, security has layers — review code before you run it.

Runtime requirements

🎬 Clawdis
EnvNEMO_TOKEN
Primary envNEMO_TOKEN
latestvk975h34dmskrtx40r6ddsntvc584pk6r
87downloads
0stars
1versions
Updated 2w ago
v1.0.0
MIT-0

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 3-minute screen recording or phone video into a 1080p MP4"
  • "trim the footage, add transitions, and export as MP4"
  • "trimming and polishing raw footage without installing software for Windows users and casual creators"

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.

Free Video Editor 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 3-minute screen recording or phone video, ask for trim the footage, add transitions, and export as MP4, 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 2 minutes process significantly faster.

Matching Input to Actions

User prompts referencing free video editor windows, aspect ratio, text overlays, or audio tracks get routed to the corresponding action via keyword and intent classification.

User says...ActionSkip 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:

HeaderValue
X-Skill-Sourcefree-video-editor-windows
X-Skill-Versionfrontmatter version
X-Skill-Platformauto-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

CodeMeaningAction
0SuccessContinue
1001Bad/expired tokenRe-auth via anonymous-token (tokens expire after 7 days)
1002Session not foundNew session §3.0
2001No creditsAnonymous: show registration URL with ?bind=<id> (get <id> from create-session or state response when needed). Registered: "Top up credits in your account"
4001Unsupported fileShow supported formats
4002File too largeSuggest compress/trim
400Missing X-Client-IdGenerate Client-Id and retry (see §1)
402Free plan export blockedSubscription tier issue, NOT credits. "Register or upgrade your plan to unlock export."
429Rate limit (1 token/client/7 days)Retry in 30s once

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.

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 footage, add transitions, and export as 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 Windows media players and platforms.

Common Workflows

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

Comments

Loading comments...