Video Movie Maker Free Download

Turn a 2-minute raw phone recording into 1080p finished movie files just by typing what you need. Whether it's turning raw clips into a complete edited movie...

Security Scan

The skill's declared purpose (cloud AI video editing) aligns with its runtime instructions (calling nemovideo.ai APIs and requiring a NEMO_TOKEN); there are minor metadata inconsistencies and no install step, but nothing indicates the skill is trying to do unrelated or excessive things.

Purpose & Capability

Name/description match the instructions: the SKILL.md describes uploading video, creating a session, calling render endpoints, and returning download URLs. Requesting a single NEMO_TOKEN credential is consistent with calling a third‑party video-processing API.

Instruction Scope

Instructions focus on the external API (session creation, SSE, upload, render). They tell the agent to read NEMO_TOKEN (declared) or obtain an anonymous token from the API. They also ask to infer a 'platform' from install path and reference a config path in the frontmatter (~/.config/nemovideo/), which is slightly inconsistent with the registry metadata. There are no instructions to read unrelated secrets, other apps' configs, or to exfiltrate arbitrary data, but the skill does require uploading user video files to an external service (expected for this purpose).

Install Mechanism

This is instruction-only with no install step and no code files, so nothing is written to disk by an installer. That lowers the surface area; there are no download URLs or package installs to review.

Credentials

Only one environment variable (NEMO_TOKEN) is declared and used, which is proportionate to a service-backed video processing workflow. The SKILL.md also documents how to obtain a short-lived anonymous token, so continuous access to a persistent secret is not strictly required. The minor inconsistency: frontmatter lists a config path (~/.config/nemovideo/) while the top-level registry said no required config paths.

Persistence & Privilege

always:false (not force-included) and there is no install activity or instructions to modify other skills or system-wide configs. The skill does not request persistent elevated privileges.

Assessment

This skill appears to do what it says: it will upload your clips to a nemovideo.ai backend and use a NEMO_TOKEN (or an anonymous token it obtains) to render edits and return a download URL. Before installing/using it, consider: (1) The source and homepage are unknown — verify the service domain (mega-api-prod.nemovideo.ai) and the provider's reputation before uploading sensitive videos. (2) Understand that any video you send will leave your device and be processed remotely; do not upload private/confidential footage you wouldn't want stored or seen by a third party. (3) The only secret requested is NEMO_TOKEN, which is reasonable, but watch for token leakage in logs and avoid pasting persistent credentials if you can use the anonymous token flow. (4) The SKILL.md frontmatter references a config path (~/.config/nemovideo/) that the registry metadata did not; that inconsistency is minor but worth confirming with the publisher. If you need higher assurance, ask the publisher for a homepage, privacy policy, or official SDK/docs and/or test with non-sensitive sample clips first.

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:

• "create my video clips"
• "export 1080p MP4"
• "cut the best moments, add background"

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 Movie Maker Free Download — Create and Export Edited Movies

Drop your 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 raw phone recording, ask for cut the best moments, add background music, and export as a shareable movie, 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 60 seconds process significantly faster and give cleaner results.

Matching Input to Actions

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

Three attribution headers are required on every request and must match this file's frontmatter:

Header	Value
X-Skill-Source	video-movie-maker-free-download
X-Skill-Version	frontmatter version
X-Skill-Platform	auto-detect: clawhub / cursor / unknown from install path

Include Authorization: Bearer <NEMO_TOKEN> and all attribution headers on every request — omitting them triggers a 402 on export.

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

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

Common Workflows

Quick edit: Upload → "cut the best moments, add background music, and export as a shareable movie" → 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.

Tips and Tricks

The backend processes faster when you're specific. Instead of "make it look better", try "cut the best moments, add background music, and export as a shareable movie" — 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 phones, TVs, and social platforms.