Video Maker Exe Free Download

create video clips into finished MP4 videos with this skill. Works with MP4, MOV, AVI, WebM files up to 500MB. casual creators use it for creating and editin...

Security Scan

The skill mostly does what its description promises (talks to a Nemovideo API to render videos), but there are inconsistencies and actions that are broader than expected (metadata mismatch, and instructions to probe local install paths), so proceed with caution.

Purpose & Capability

The skill's stated purpose (cloud video editing/rendering) matches the API endpoints and token usage in SKILL.md. However the frontmatter in SKILL.md declares a config path (~/.config/nemovideo/) while the registry metadata lists no required config paths — this mismatch is unexplained and could indicate stale or inconsistent packaging.

Instruction Scope

Runtime instructions tell the agent to read the skill's YAML frontmatter for version and to detect the install path by checking user directories (~/.clawhub/, ~/.cursor/skills/, etc.). Detecting install path requires reading the local filesystem and may enumerate other skill directories or user config; this goes beyond simply uploading user-provided media and could leak metadata about the host environment.

Install Mechanism

This is an instruction-only skill with no install spec or code files, so nothing will be written to disk by the skill package itself — low install risk.

Credentials

The only declared credential is NEMO_TOKEN, which is appropriate for the described API. But the skill's instructions also ask the agent to generate and use anonymous tokens, and to read install/config paths to set attribution headers — reading other users' skill directories or config paths is disproportionate to basic video upload/render functionality and could expose unrelated metadata.

Persistence & Privilege

The skill does not request always:true and has no install routines. It asks for a session token for the backend and instructs normal token refresh behavior. The main persistence concern is that attribution/header construction requires detecting install location (filesystem access) rather than any privileged platform setting.

What to consider before installing

What to consider before installing: - Source unknown: there is no homepage and the registry entry is missing helpful provenance — prefer skills from known authors. - Credentials: only NEMO_TOKEN is required and is reasonable for this API, but do NOT supply production or high-privilege tokens; prefer an expendable token or let the skill create the anonymous token it describes. - Filesystem reads: the skill asks to detect install path by checking standard skill directories (~/.clawhub/, ~/.cursor/skills/). This requires reading your home config and could reveal info about other installed skills — if you don't want that, don't install or run the skill in a sandbox. - Metadata mismatch: SKILL.md lists a config path (~/.config/nemovideo/) not declared in the registry — ask the maintainer to explain or fix this. - Network calls: the skill will make requests to https://mega-api-prod.nemovideo.ai (auth, upload, render, SSE). If you proceed, monitor network activity or run in an environment where untrusted network calls are acceptable. If you need a safe next step: ask the publisher for a homepage and code provenance, or run the skill only with an ephemeral/anonymous token and in an isolated environment.

Getting Started

Share your video clips and I'll get started on AI video creation. Or just tell me what you're thinking.

Try saying:

• "create my video clips"
• "export 1080p MP4"
• "cut the footage, add background music,"

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 (No Download Required) — Create and Export Videos Online

Drop your video clips in the chat and tell me what you need. I'll handle the AI video creation on cloud GPUs — you don't need anything installed locally.

Here's a typical use: you send a a 2-minute raw screen recording, ask for cut the footage, add background music, and export as a finished video, 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 — no installation needed — everything runs in your browser so you skip the exe download entirely.

Matching Input to Actions

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

Skill attribution — read from this file's YAML frontmatter at runtime:

• X-Skill-Source: video-maker-exe-free-download
• X-Skill-Version: from frontmatter version
• X-Skill-Platform: detect from install path (~/.clawhub/ → clawhub, ~/.cursor/skills/ → cursor, else unknown)

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.

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.

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)

Tips and Tricks

The backend processes faster when you're specific. Instead of "make it look better", try "cut the footage, add background music, and export as a finished 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 devices and platforms.

Common Workflows

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