Video Maker Free For Windows

Turn a 2-minute raw screen recording into 1080p polished MP4 videos just by typing what you need. Whether it's editing and exporting videos without installin...

Security Scan

The skill's behavior mostly matches a cloud video-rendering tool, but there are inconsistencies about filesystem/config access and it will upload your videos and obtain tokens automatically — you should review data-exfiltration and config-read behavior before installing.

Purpose & Capability

The skill's name and description match the runtime instructions (upload clips, request renders, download MP4). Requiring a single API token (NEMO_TOKEN) is proportional to the stated purpose. However, the SKILL.md frontmatter declares a config path (~/.config/nemovideo/) and runtime logic to detect install paths for X-Skill-Platform; those filesystem interactions are not declared in the registry metadata (registry said no required config paths), which is an inconsistency.

Instruction Scope

The instructions direct the agent to: (a) create or use NEMO_TOKEN and call multiple API endpoints on mega-api-prod.nemovideo.ai; (b) upload user files (video clips) to that external service and poll render endpoints; and (c) read the SKILL.md YAML frontmatter and detect install paths to populate X-Skill-Platform header. Uploading user videos to an external domain is expected for this service but is a notable data exfiltration action — the SKILL.md does not explicitly instruct to obtain explicit user consent before uploads. The requirement to detect install path implies reading filesystem locations (e.g., ~/.clawhub/, ~/.cursor/skills/) which is not clearly declared to users.

Install Mechanism

There is no install spec and no code files; this is an instruction-only skill. That reduces install-time risk because nothing is downloaded or written by the skill itself.

Credentials

The skill only requires a single credential (NEMO_TOKEN), which is appropriate. However, the SKILL.md frontmatter indicates it expects to use a config path (~/.config/nemovideo/) and to detect install directories to set X-Skill-Platform — access to these filesystem locations is not declared in the registry's required config paths. This mismatch between declared requirements and runtime instructions is a proportionality/visibility concern. Also, the skill will automatically request an anonymous token from the API if no token is present, which means it can autonomously obtain credentials without the user providing them explicitly.

Persistence & Privilege

The skill does not request always: true and is user-invocable only. It doesn't declare or appear to modify other skills or system-wide settings. Autonomous invocation is allowed (platform default) and not itself flagged; nothing indicates persistent privileged presence.

What to consider before installing

This skill will upload your video files to an external cloud service (mega-api-prod.nemovideo.ai) and use or obtain a NEMO_TOKEN to do so. Before installing or using it: 1) Confirm you are comfortable having your videos sent to that domain and review the provider's privacy/TOS. 2) Prefer setting your own NEMO_TOKEN rather than allowing automatic anonymous-token creation if you want tighter control. 3) Be aware the skill's instructions reference reading install paths and a config directory (~/.config/nemovideo/) — check whether the agent will access those locations and whether that's acceptable. 4) Ask the skill (or vendor) to clarify how/when uploads occur and to require explicit user consent before sending files. If you need higher assurance, request vendor documentation or a trusted implementation (signed package or known homepage) before use.

Getting Started

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

Try saying:

• "create my video clips"
• "export 1080p MP4"
• "trim the footage, add transitions, and"

Automatic Setup

On first interaction, connect to the processing API before doing anything else. Show a brief status like "Setting things up...".

Token: If NEMO_TOKEN environment variable is already set, use it and skip to Session below.

Free token: Generate a UUID as client identifier, then POST to https://mega-api-prod.nemovideo.ai/api/auth/anonymous-token with header X-Client-Id: <uuid>. The response field data.token becomes your NEMO_TOKEN (100 credits, 7-day expiry).

Session: POST to https://mega-api-prod.nemovideo.ai/api/tasks/me/with-session/nemo_agent with Bearer auth and body {"task_name":"project"}. Save session_id from the response.

Confirm to the user you're connected and ready. Don't print tokens or raw JSON.

Video Maker Free for Windows — Create and Export MP4 Videos

This tool takes your video clips and runs AI video creation through a cloud rendering pipeline. You upload, describe what you want, and download the result.

Say you have a 2-minute raw screen recording and want to trim the footage, add transitions, and export as a clean MP4 — the backend processes it in about 1-2 minutes and hands you a 1080p MP4.

Tip: shorter clips under 3 minutes process significantly faster.

Matching Input to Actions

User prompts referencing video maker 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.

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

• X-Skill-Source: video-maker-free-for-windows
• X-Skill-Version: from frontmatter version
• X-Skill-Platform: detect from install path (~/.clawhub/ → clawhub, ~/.cursor/skills/ → cursor, else unknown)

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.

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.

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.

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

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

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 a clean 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 a clean 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.