Movie Maker Microsoft Free Download

Get polished MP4 videos ready to post, without touching a single slider. Upload your video clips (MP4, MOV, AVI, WMV, up to 500MB), say something like "trim...

Security Scan

The skill claims to be a 'Movie Maker Microsoft Free Download' but actually routes uploads and rendering to a third‑party nemovideo.ai cloud service and will automatically obtain/use an anonymous token — this name/behavior mismatch and the automatic external uploads warrant caution.

Purpose & Capability

The skill name implies a Microsoft/Windows Movie Maker download, but the instructions implement a cloud-based video editing pipeline hosted at mega-api-prod.nemovideo.ai. Requiring only NEMO_TOKEN fits the actual backend, but the name is misleading and could cause users to think they're getting an offline Microsoft product when files are uploaded to a third party.

Instruction Scope

Runtime instructions direct the agent to upload user video files and session metadata to nemovideo.ai, create/refresh anonymous tokens automatically, store session_id, and include custom headers derived from local install paths. Uploading user media to an external service is expected for a cloud editor, but the instructions also imply the agent may detect install paths (to set X-Skill-Platform) and will auto-create credentials if NEMO_TOKEN is absent — both increase privacy/telemetry exposure and should be explicit to users.

Install Mechanism

Instruction-only skill with no install spec or downloads; nothing is written to disk by an installer. This is the lowest install risk.

Credentials

Only NEMO_TOKEN (primary credential) and an optional config path (~/.config/nemovideo/) are declared, which is proportional to a service that requires an API token. However the skill will auto-generate and use an anonymous token if none is supplied — users should not supply unrelated secrets to NEMO_TOKEN and should understand that the token authorizes uploads/exports on their behalf.

Persistence & Privilege

always is false and the skill is user-invocable; it does not request persistent platform privileges. Autonomous invocation is allowed (normal) and not by itself a red flag, but combined with automatic network uploads it increases impact if misused.

What to consider before installing

This skill will upload your videos and session data to mega-api-prod.nemovideo.ai and will automatically obtain or reuse an anonymous API token (NEMO_TOKEN) if you don't provide one. The skill name mentions 'Microsoft' and 'Free Download' but does not interact with Microsoft services — it is a cloud editor on nemovideo.ai. Before installing or using: 1) Confirm you trust nemovideo.ai and review its privacy/terms, because your videos will be transmitted to and processed by that third party. 2) Do not set NEMO_TOKEN equal to credentials from other services. 3) Test with non-sensitive video first. 4) If you expect an offline Microsoft Movie Maker installer, do not use this skill — ask the author for clarification or a legitimate homepage/source. 5) If you need lower telemetry, ask whether the skill can avoid sending environment or install-path-derived headers (X-Skill-Platform) or refuse to auto-create tokens.

Getting Started

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

Try saying:

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

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.

Movie Maker Microsoft Free Download — Edit and Export Videos Online

Send me your video clips and describe the result you want. The AI video editing runs on remote GPU nodes — nothing to install on your machine.

A quick example: upload a 2-minute home video clip, type "trim the footage, add transitions, and export as a finished video", and you'll get a 1080p MP4 back in roughly 1-2 minutes. All rendering happens server-side.

Worth noting: shorter clips under 3 minutes process significantly faster.

Matching Input to Actions

User prompts referencing movie maker microsoft free download, 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.

Headers are derived from this file's YAML frontmatter. X-Skill-Source is movie-maker-microsoft-free-download, 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).

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

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

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 footage, add transitions, and export as a finished video" — concrete instructions get better results.

Max file size is 500MB. Stick to MP4, MOV, AVI, WMV for the smoothest experience.

Export as MP4 for widest compatibility across devices and platforms.

Common Workflows

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