Movie Maker Video Editor Free

edit raw video clips into polished edited videos with this skill. Works with MP4, MOV, AVI, WebM files up to 500MB. casual creators and students use it for e...

Security Scan

The skill's runtime instructions are coherent with a cloud video-editing service (it only needs a NEMO_TOKEN and uses a nemovideo API), but there are small metadata inconsistencies and no publisher/homepage—so proceed with caution before providing credentials or uploading files.

Purpose & Capability

The skill name and description match the instructions: it posts video uploads, starts render jobs, polls state and returns download URLs from mega-api-prod.nemovideo.ai. Requiring a single NEMO_TOKEN is proportionate for a remote rendering service. Note: the SKILL.md frontmatter lists a config path (~/.config/nemovideo/) while the registry metadata reported no required config paths — a minor inconsistency in declared capabilities.

Instruction Scope

SKILL.md confines runtime actions to authenticating (using NEMO_TOKEN or obtaining an anonymous token from the service), creating sessions, uploading user-provided files, sending SSE/editor messages, and polling render endpoints. It does not instruct reading arbitrary local files or other unrelated environment variables. It does, however, require uploading user media to an external service — expected for the stated purpose but a privacy consideration.

Install Mechanism

This is an instruction-only skill with no install spec and no code files, so nothing is written to disk or downloaded by the skill itself. That lowers installation risk.

Credentials

Only a single credential (NEMO_TOKEN) is declared as required/primary, which is appropriate for a hosted API. The SKILL.md also describes generating or using an anonymous token when none is present. The earlier registry summary showed no config paths, but SKILL.md frontmatter mentions ~/.config/nemovideo/ — this mismatch should be clarified. Also consider that providing NEMO_TOKEN or uploading media gives the external service access to user files.

Persistence & Privilege

The skill is not always-enabled and uses the platform-default ability to be invoked autonomously. It does not request system-wide privileges or modify other skills' configurations in the provided instructions.

What to consider before installing

This skill appears to implement a cloud video-editing integration and only needs a NEMO_TOKEN to operate, which is broadly consistent with its purpose. However: (1) the skill has no homepage or published source — that reduces trust; (2) SKILL.md mentions a local config path (~/.config/nemovideo/) that the registry metadata did not list — ask the publisher to clarify whether the skill will read or write that path; (3) uploading video/audio sends data to mega-api-prod.nemovideo.ai — do not upload sensitive or private footage unless you trust that service's privacy policy; (4) prefer using an anonymous or short-lived token (the skill supports obtaining one) rather than reusing a long-lived credential; and (5) if you must use a permanent NEMO_TOKEN, verify the token's scope and revoke it after testing. If you want higher assurance, request a publisher homepage, privacy/retention policy, and confirmation of whether any local config files will be accessed.

Getting Started

Ready when you are. Drop your raw video clips here or describe what you want to make.

Try saying:

• "edit a 2-minute phone-recorded clip into a 1080p MP4"
• "trim the footage, add transitions, and export as a clean MP4"
• "editing raw clips into finished videos without paid software for casual creators and students"

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.

Movie Maker Video Editor Free — Edit and Export Finished Videos

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

Say you have a 2-minute phone-recorded clip 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 movie maker video editor free, 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.

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

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

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.

Backend Response Translation

The backend assumes a GUI exists. Translate these into API actions:

Backend says	You do
"click [button]" / "点击"	Execute via API
"open [panel]" / "打开"	Query session state
"drag/drop" / "拖拽"	Send edit via SSE
"preview in timeline"	Show track summary
"Export button" / "导出"	Execute 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)

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.

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 devices and platforms.