Video Maker Editor Free Download

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

Security Scan

The skill's declared purpose (cloud video editing) mostly matches its runtime instructions, but there are inconsistencies and a few concerning behaviors (hidden backend activity, an undeclared config path, and automatic use of any NEMO_TOKEN in the environment) that merit caution before installing or providing credentials.

Purpose & Capability

The skill's name/description (online video editing, MP4 exports) aligns with the network endpoints and APIs used in SKILL.md. The only declared secret (NEMO_TOKEN) is appropriate for a hosted rendering service. However, the SKILL.md frontmatter lists a config path (~/.config/nemovideo/) that is not reflected in the registry metadata, which is an inconsistency.

Instruction Scope

Instructions require contacting an external API (mega-api-prod.nemovideo.ai), uploading user video files, creating sessions, polling render status, and including attribution headers. The SKILL.md explicitly instructs the agent to "Keep the technical details out of the chat," which hides network/auth activity from the user and reduces transparency. It also directs the agent to use any NEMO_TOKEN found in the environment without prompting, which could cause a pre-existing token to be used unexpectedly.

Install Mechanism

This is an instruction-only skill with no install spec and no code files, so nothing is written to disk. That lowers install-time risk.

Credentials

Only a single env var (NEMO_TOKEN) is declared as required, which is proportionate for a remote API. That said, SKILL.md frontmatter references a config path (~/.config/nemovideo/) not reflected in the registry entry, and the skill will use any NEMO_TOKEN present silently. If you have other tokens or credentials in your environment, there's a risk of unintended use. The skill also asks to auto-detect platform from install path, which may require reading agent install metadata or paths.

Persistence & Privilege

always:false and no install means the skill does not request permanent elevated presence. The skill can be invoked autonomously (default), which is normal — combine that with the fact it will make network calls using a provided environment token and hide technical details, and you should be cautious about allowing autonomous invocation with your real NEMO_TOKEN.

What to consider before installing

This skill appears to implement a remote video-editing service and needs a NEMO_TOKEN to call its API. Before installing or providing a token: 1) Verify the service domain and developer (ask for a homepage, privacy policy, or source code) since the skill's source is unknown. 2) Prefer using an anonymous token (the skill supports generating one) rather than a long-lived personal token in your environment. 3) Be aware uploads will send your video files to an external server — check privacy/retention policies. 4) Ask the author why the frontmatter lists ~/.config/nemovideo/ while registry metadata lists no config paths, and why the skill should "keep technical details out of the chat" (that hides backend activity). 5) If you have sensitive tokens in your environment, avoid installing or run the skill in an isolated environment where those tokens are not present. If the developer cannot satisfactorily explain the inconsistencies and the data handling, treat the skill as untrusted.

Getting Started

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

Try saying:

• "edit a 2-minute raw phone recording into a 1080p MP4"
• "trim the footage, add background music, and export as MP4"
• "editing and exporting videos without installing 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.

Video Maker Editor 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 raw phone recording, type "trim the footage, add background music, and export as MP4", 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 in the browser.

Matching Input to Actions

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

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	video-maker-editor-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.

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

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 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 background music, and export as 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.

Common Workflows

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