Movie Maker Effects Free Download

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

Security Scan

The skill's required credentials and runtime instructions match its stated purpose (cloud video effects via the nemo video API), but a few metadata/information gaps and the unknown source reduce confidence.

Purpose & Capability

The skill is a cloud video-effects front-end and only requests a NEMO_TOKEN (the service auth token) and describes API calls to nemovideo.ai; that credential is proportionate to the described functionality.

Instruction Scope

Instructions are focused on uploading video, creating sessions, streaming SSE edits, polling export status, and downloading results. They also ask the agent to derive headers from the SKILL.md YAML frontmatter and detect installation path to set X-Skill-Platform, which implies the agent may read its own metadata / path — expected but worth noting as file-system introspection beyond just sending network requests.

Install Mechanism

No install spec or code is present (instruction-only), so nothing is fetched or written by an installer. This is the lowest install risk.

Credentials

Only NEMO_TOKEN is required, which matches the API usage. However SKILL.md metadata also references a config path (~/.config/nemovideo/) while the registry metadata lists no required config paths — this inconsistency should be clarified. The skill also provides a fallback anonymous-token flow that can mint short-lived tokens, which is reasonable for anonymous usage.

Persistence & Privilege

The skill is not force-included (always: false) and uses session IDs for job state; it instructs saving session_id but does not request persistent elevated privileges or modify other skills. Autonomous invocation is allowed by default (normal).

Assessment

This skill appears coherent: it will upload videos and use a NEMO_TOKEN to call nemo video APIs and return processed files. Before installing, confirm the nemovideo.ai domain and the token source are trustworthy (don't put high-privilege or unrelated credentials into NEMO_TOKEN). Be aware that you will be uploading video/audio to an external cloud service — verify privacy, retention, and deletion policies for sensitive content. Ask the author/source for clarification about the small metadata inconsistency (the SKILL.md mentions ~/.config/nemovideo/ while the registry metadata lists no config paths) and confirm where files are stored and how long tokens/sessions persist. If you can't verify the service operator, avoid uploading sensitive media or reuse of privileged tokens.

Getting Started

Send me your video clips and I'll handle the AI effects application. Or just describe what you're after.

Try saying:

• "add a 2-minute birthday video clip into a 1080p MP4"
• "add cinematic transitions, color grading, and motion effects to my video"
• "adding visual effects and transitions to home or social media videos for casual video creators"

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.

Movie Maker Effects Free Download — Apply Effects and Export Videos

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

Say you have a 2-minute birthday video clip and want to add cinematic transitions, color grading, and motion effects to my video — the backend processes it in about 30-60 seconds and hands you a 1080p MP4.

Tip: shorter clips under 60 seconds process effects faster and give you more room to experiment.

Matching Input to Actions

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

All calls go to https://mega-api-prod.nemovideo.ai. The main endpoints:

1. Session — POST /api/tasks/me/with-session/nemo_agent with {"task_name":"project","language":"<lang>"}. Gives you a session_id.
2. Chat (SSE) — POST /run_sse with session_id and your message in new_message.parts[0].text. Set Accept: text/event-stream. Up to 15 min.
3. Upload — POST /api/upload-video/nemo_agent/me/<sid> — multipart file or JSON with URLs.
4. Credits — GET /api/credits/balance/simple — returns available, frozen, total.
5. State — GET /api/state/nemo_agent/me/<sid>/latest — current draft and media info.
6. Export — POST /api/render/proxy/lambda with render ID and draft JSON. Poll GET /api/render/proxy/lambda/<id> every 30s for completed status and download URL.

Formats: mp4, mov, avi, webm, mkv, jpg, png, gif, webp, mp3, wav, m4a, aac.

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

Every API call needs Authorization: Bearer <NEMO_TOKEN> plus the three attribution headers above. If any header is missing, exports return 402.

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)

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.

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

Common Workflows

Quick edit: Upload → "add cinematic transitions, color grading, and motion effects to my video" → Download MP4. Takes 30-60 seconds 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 "add cinematic transitions, color grading, and motion effects to my video" — 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 platforms and devices.