Video Maker Free Download Online

Skip the learning curve of professional editing software. Describe what you want — combine these images into a 30-second video with music and text overlays —...

Security Scan

The skill's requests and runtime instructions are consistent with a cloud video creation integration — it only asks for a single service token and describes API calls that match its purpose — but it comes from an unknown source and has a few minor inconsistencies you should be aware of.

Purpose & Capability

The skill is a cloud video creation front-end and only declares a single service credential (NEMO_TOKEN) used in Authorization headers to the nemo video API. That credential is proportionate to a remote rendering service. The SKILL.md describes uploading media, creating sessions, SSE streaming, and exporting — all coherent with the stated purpose. One minor inconsistency: the top-level registry metadata said no required config paths, but the skill frontmatter lists a configPath (~/.config/nemovideo/). This is likely benign (optional local cache) but is an inconsistency.

Instruction Scope

Instructions focus on communicating with the remote API and mapping GUI-like SSE events to API calls. They instruct saving session_id and using it for subsequent calls, and to include attribution headers. The skill also directs the agent to read the skill file's YAML frontmatter at runtime and to detect install path to set an X-Skill-Platform header — this requires reading the skill file and potentially checking install paths. Reading its own skill metadata is reasonable, but any filesystem reads beyond that would be out-of-scope. The instructions also require uploading user media to the external API — this is expected but entails privacy/bandwidth implications.

Install Mechanism

No install spec and no code files — the skill is instruction-only, so it doesn't write or execute code on disk. This is the lowest-risk install mechanism.

Credentials

Only one environment variable is required (NEMO_TOKEN) and the SKILL.md explains how to use an existing token or obtain an anonymous token from the same service. That single token is appropriate for authorizing API requests to the described service. There are no unrelated credentials requested.

Persistence & Privilege

The skill is not always-enabled and has normal agent invocation permissions. It asks the agent to persist session_id for the duration of a session, which is reasonable. It does not request elevated system-wide privileges or to modify other skills.

Assessment

This skill is internally consistent for a remote video-rendering integration, but exercise caution because the source and homepage are unknown. Before installing: (1) Recognize that any media you upload will be sent to mega-api-prod.nemovideo.ai — don't upload sensitive private content unless you trust that endpoint. (2) NEMO_TOKEN is a bearer credential for the service; provide a token with minimal scope and rotate/revoke it if you stop using the skill. (3) The skill will read its own frontmatter and may check install paths; ensure the agent is not granted broader filesystem access. (4) The registry metadata contains a minor inconsistency about config paths — ask the publisher what local config is stored and where. If you need stronger assurance, request an official homepage or source repository and prefer skills from known publishers.

Getting Started

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

Try saying:

• "create my images or clips"
• "export 1080p MP4"
• "combine these images into a 30-second"

Automatic Setup

On first interaction, connect to the processing API before doing anything else. Show a brief status like "Setting things up...".

Token: If NEMO_TOKEN environment variable is already set, use it and skip to Session below.

Free token: Generate a UUID as client identifier, then POST to https://mega-api-prod.nemovideo.ai/api/auth/anonymous-token with header X-Client-Id: <uuid>. The response field data.token becomes your NEMO_TOKEN (100 credits, 7-day expiry).

Session: POST to https://mega-api-prod.nemovideo.ai/api/tasks/me/with-session/nemo_agent with Bearer auth and body {"task_name":"project"}. Save session_id from the response.

Confirm to the user you're connected and ready. Don't print tokens or raw JSON.

Video Maker Free Download Online — Create and Export Videos Online

Send me your images or 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 five product photos and a logo file, type "combine these images into a 30-second video with music and text overlays", and you'll get a 1080p MP4 back in roughly 30-60 seconds. All rendering happens server-side.

Worth noting: using fewer than ten clips keeps render times under a minute.

Matching Input to Actions

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

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

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

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

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.

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.

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)

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

Common Workflows

Quick edit: Upload → "combine these images into a 30-second video with music and text overlays" → Download MP4. Takes 30-60 seconds 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 these images into a 30-second video with music and text overlays" — 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 social platforms and devices.