Movie Maker Free Export

Skip the learning curve of professional editing software. Describe what you want — trim the clips, add background music, and export as MP4 for free — and get...

Security Scan

The skill's declared purpose (cloud video editing) mostly matches its network calls, but there are inconsistent and unexplained pieces (required NEMO_TOKEN vs. auto-generated anonymous token, declared config path not used, and no provenance/homepage) that warrant caution before installing or using it.

Purpose & Capability

The described capability (remote AI video editing and exporting) aligns with the API endpoints and upload/export workflow in SKILL.md and the single credential (NEMO_TOKEN). However the manifest declares a required env var (NEMO_TOKEN) while the instructions also include an anonymous-token flow to mint a token if none is present — this mismatch is unexplained and unnecessary for a strictly coherent manifest. The frontmatter also lists a config path (~/.config/nemovideo/) that the runtime instructions never reference.

Instruction Scope

The runtime instructions stay within the expected scope for a cloud video-editing skill: they describe authenticating, creating a session, uploading files, SSE for edits, polling an export endpoint, and returning a download URL. They do not instruct reading arbitrary local files or other unrelated environment variables. The only slight scope creep is the expectation to 'auto-detect' X-Skill-Platform from an install path (implies reading an install path), though no explicit filesystem reads are described.

Install Mechanism

This is an instruction-only skill with no install spec and no code files, so nothing will be written to disk by default. That lowers installation risk compared to remote downloads or packages.

Credentials

Only one credential (NEMO_TOKEN) is declared, which is appropriate for an API-backed service. But the SKILL.md both checks for NEMO_TOKEN and also instructs generating an anonymous token via the backend if the env var is absent — this contradicts the manifest's 'required env var' claim. The manifest's listed config path (~/.config/nemovideo/) is not used in the instructions; its presence increases the surface area for potential unexpected access if implemented.

Persistence & Privilege

The skill does not request always:true and is user-invocable. The instructions say to store session_id and token for subsequent requests, which is normal for session workflows. There is no instruction to modify other skills or system-wide settings.

What to consider before installing

This skill appears to do what it says (upload videos to a remote AI-rendering service and return downloadable MP4s), but there are a few red flags you should consider before installing or using it: - Provenance: There is no homepage, documentation, or clear publisher identity. Ask for the service's privacy policy, terms of service, and who operates mega-api-prod.nemovideo.ai before trusting uploads. - Token handling: The manifest requires NEMO_TOKEN but the runtime instructions will mint an anonymous token if none is present. Decide whether you want the agent to automatically create and store tokens for you. If you prefer control, provision your own NEMO_TOKEN and verify what permissions it grants and how long tokens are retained. - Data privacy: Using this skill uploads potentially sensitive video files (up to 500MB) to a third-party server. Confirm retention/deletion policy and whether content is used for model training. - Config path / platform detection: The manifest lists a config path that the instructions don’t use; verify the implementation will not read arbitrary files like ~/.config/nemovideo/ or agent install paths unless you explicitly allow it. If you need higher assurance: request the skill's source or official homepage, a description of where tokens and session data are stored, and a privacy/security statement from the publisher. If you don't get satisfactory answers, prefer reputable alternatives or local editing tools.

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:

• "export my video clips"
• "export 1080p MP4"
• "trim the clips, add background music,"

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 Free Export — Edit and Export Videos Free

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 family video recorded on a smartphone, type "trim the clips, add background music, and export as MP4 for free", 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 export significantly faster.

Matching Input to Actions

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

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

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

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.

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)

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.

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 → "trim the clips, add background music, and export as MP4 for free" → 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 clips, add background music, and export as MP4 for free" — 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 all devices and platforms.