Best Video Maker Free

Get polished MP4 videos ready to post, without touching a single slider. Upload your video clips or images (MP4, MOV, JPG, PNG, up to 500MB), say something l...

Security Scan

The skill appears to implement a cloud video-rendering flow that matches its description, but there are inconsistencies in its declared requirements and ambiguous token/config handling; it will upload your media to an external API and may persist a session/token — review before installing.

Purpose & Capability

The declared purpose (combine/upload clips, cloud render, return MP4) aligns with the endpoints and actions in SKILL.md and the single required credential (NEMO_TOKEN). However, registry metadata says no config paths required while the SKILL.md frontmatter lists a config path (~/.config/nemovideo/), which is inconsistent and unexplained.

Instruction Scope

Runtime instructions are focused on the video service: checking/creating a token, creating a session, uploading files, streaming SSE for edits, polling render status, and returning download URLs. This explicitly requires uploading user media to https://mega-api-prod.nemovideo.ai. The SKILL.md also asks the agent to auto-detect an install path to set X-Skill-Platform — that could involve reading filesystem/install paths (vague). There are no instructions to read unrelated files or other credentials.

Install Mechanism

No install spec or code files — instruction-only skill. Lowest-risk install footprint (nothing written to disk by an installer).

Credentials

The registry lists NEMO_TOKEN as required, but SKILL.md instructs the agent to request an anonymous token from the service if NEMO_TOKEN is absent (i.e., the environment variable is optional in practice). This mismatch is confusing. The skill will use the token to authorize all uploads and renders (expected), but supplying a personal NEMO_TOKEN would allow the skill to act as that identity. The frontmatter also lists a config path (potential persistence) despite registry metadata saying none — unclear whether tokens/sessions are stored on disk.

Persistence & Privilege

always:false and default agent invocation are appropriate. The skill does create/hold session IDs and tokens for interactions with the backend, but it does not request elevated system-wide privileges or claim to modify other skills. The only minor concern is the ambiguous config path which may allow persisting credentials to ~/.config/nemovideo/ if implemented.

What to consider before installing

This skill will upload the files you give it (videos, images, audio) to mega-api-prod.nemovideo.ai for cloud rendering and requires an API token (NEMO_TOKEN) or will obtain an anonymous token for you. Before installing: (1) Decide whether you’re comfortable sending your media to that external service and review its privacy/docs; (2) do not supply sensitive or private material unless you trust the domain and operator; (3) avoid giving a personal NEMO_TOKEN unless you understand what permissions that token grants; (4) ask the skill author to clarify the inconsistent metadata (registry says no config path while SKILL.md lists ~/.config/nemovideo/, and the registry marks NEMO_TOKEN required while the code auto-generates one); (5) if you want extra safety, run the skill in an isolated environment or sandbox and monitor whether it writes tokens to disk.

Getting Started

Got video clips or images to work with? Send it over and tell me what you need — I'll take care of the AI video creation.

Try saying:

• "create five vacation photos and a 30-second clip into a 1080p MP4"
• "combine my clips into a short video with music and transitions"
• "creating shareable videos from photos and clips without editing software for casual creators and students"

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 — Create and Export Finished Videos

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

Say you have five vacation photos and a 30-second clip and want to combine my clips into a short video with music and transitions — the backend processes it in about 1-2 minutes and hands you a 1080p MP4.

Tip: shorter source clips under 2 minutes process significantly faster.

Matching Input to Actions

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

Error Codes

• 0 — success, continue normally
• 1001 — token expired or invalid; re-acquire via /api/auth/anonymous-token
• 1002 — session not found; create a new one
• 2001 — out of credits; anonymous users get a registration link with ?bind=<id>, registered users top up
• 4001 — unsupported file type; show accepted formats
• 4002 — file too large; suggest compressing or trimming
• 400 — missing X-Client-Id; generate one and retry
• 402 — free plan export blocked; not a credit issue, subscription tier
• 429 — rate limited; wait 30s and retry 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 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)

Common Workflows

Quick edit: Upload → "combine my clips into a short video with music and transitions" → 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 into a short video with music and transitions" — concrete instructions get better results.

Max file size is 500MB. Stick to MP4, MOV, JPG, PNG for the smoothest experience.

Export as MP4 for widest compatibility across all platforms and devices.