Best Video Maker Free App

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

Security Scan

The skill's instructions generally match a cloud video-rendering service (it needs a service token and calls a remote API), but metadata and a few runtime details don't line up and warrant caution before installing.

Purpose & Capability

Name/description claim a cloud video-rendering service; requiring a single service token (NEMO_TOKEN) and making REST calls to nemovideo.ai is coherent. However the metadata also declares a config path (~/.config/nemovideo/) that the SKILL.md never references — this mismatch is unexplained and may request access to local config unnecessarily.

Instruction Scope

SKILL.md gives explicit API calls (auth, session creation, SSE, upload, render/polling) and file upload instructions which are consistent with the stated purpose. It also instructs automated anonymous-token acquisition (POST to mega-api-prod.nemovideo.ai) and to include the returned token in requests. The doc asks to 'auto-detect' platform from install path — which implies reading the agent's environment/install path. The instructions do not ask for unrelated file reads, but the platform-detection and metadata configPaths create ambiguity about what local data may be accessed.

Install Mechanism

Instruction-only skill with no install spec and no code files — nothing will be written to disk by an installer. That is lower risk from an install perspective.

Credentials

Only NEMO_TOKEN is required, which is appropriate for a cloud-rendering integration. However the metadata's required configPaths (~/.config/nemovideo/) is not justified by the SKILL.md and potentially broadens access to local config. Also the skill will create or request an anonymous token if none is present, which means it will make outbound network requests and handle tokens; users should consider whether to provide an existing NEMO_TOKEN (which may grant access to account data/billing) or rely on the anonymous token flow.

Persistence & Privilege

always is false and there is no on-disk installation. The skill will create session tokens and keep session_id in runtime memory for the job lifecycle — expected for this use case. Autonomous invocation is allowed (platform default); combined with network access and token usage this increases blast radius if the skill were malicious, but autonomous invocation alone is not disqualifying.

What to consider before installing

This skill largely behaves like a normal cloud video-renderer, but exercise caution because the package source is unknown and metadata asks for a local config path that the instructions don't explain. Before installing: 1) Verify the nemovideo.ai endpoint and the publisher (the skill has no homepage/source info). 2) Prefer using the anonymous-token flow rather than providing a real NEMO_TOKEN tied to your account; if you must provide a token, treat it like sensitive credentials. 3) Ask the developer why ~/.config/nemovideo/ is declared and what would be read or written there. 4) Test with non-sensitive dummy tokens and short, non-private clips first. 5) Check the service's privacy/billing terms (uploads may be stored/processed remotely). If you cannot verify the endpoint or the publisher, consider not installing or running the skill in a restricted environment.

Getting Started

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

Try saying:

• "create three 30-second phone clips into a 1080p MP4"
• "combine my clips, add background music and text overlays, and export as a clean video"
• "creating edited videos from raw clips without paid software for casual creators"

Quick Start Setup

This skill connects to a cloud processing backend. On first use, set up the connection automatically and let the user know ("Connecting...").

Token check: Look for NEMO_TOKEN in the environment. If found, skip to session creation. Otherwise:

• Generate a UUID as client identifier
• POST https://mega-api-prod.nemovideo.ai/api/auth/anonymous-token with X-Client-Id header
• Extract data.token from the response — this is your NEMO_TOKEN (100 free credits, 7-day expiry)

Session: POST https://mega-api-prod.nemovideo.ai/api/tasks/me/with-session/nemo_agent with Bearer auth and body {"task_name":"project"}. Keep the returned session_id for all operations.

Let the user know with a brief "Ready!" when setup is complete. Don't expose tokens or raw API output.

Best Video Maker Free App — Create and Export Edited Videos

Send me your video clips and describe the result you want. The AI video creation runs on remote GPU nodes — nothing to install on your machine.

A quick example: upload three 30-second phone clips, type "combine my clips, add background music and text overlays, and export as a clean video", and you'll get a 1080p MP4 back in roughly 1-2 minutes. All rendering happens server-side.

Worth noting: shorter clips under 60 seconds process significantly faster and work great for Reels or Shorts.

Matching Input to Actions

User prompts referencing best video maker free app, 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.

Include Authorization: Bearer <NEMO_TOKEN> and all attribution headers on every request — omitting them triggers a 402 on export.

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

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

API base: https://mega-api-prod.nemovideo.ai

Create session: POST /api/tasks/me/with-session/nemo_agent — body {"task_name":"project","language":"<lang>"} — returns task_id, session_id.

Send message (SSE): POST /run_sse — body {"app_name":"nemo_agent","user_id":"me","session_id":"<sid>","new_message":{"parts":[{"text":"<msg>"}]}} with Accept: text/event-stream. Max timeout: 15 minutes.

Upload: POST /api/upload-video/nemo_agent/me/<sid> — file: multipart -F "files=@/path", or URL: {"urls":["<url>"],"source_type":"url"}

Credits: GET /api/credits/balance/simple — returns available, frozen, total

Session state: GET /api/state/nemo_agent/me/<sid>/latest — key fields: data.state.draft, data.state.video_infos, data.state.generated_media

Export (free, no credits): POST /api/render/proxy/lambda — body {"id":"render_<ts>","sessionId":"<sid>","draft":<json>,"output":{"format":"mp4","quality":"high"}}. Poll GET /api/render/proxy/lambda/<id> every 30s until status = completed. Download URL at output.url.

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

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

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.

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 → "combine my clips, add background music and text overlays, and export as a clean 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.

Tips and Tricks

The backend processes faster when you're specific. Instead of "make it look better", try "combine my clips, add background music and text overlays, and export as a clean 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 social platforms and devices.