Video Maker For Free Download

Turn five product photos and a background music file into 1080p finished MP4 videos just by typing what you need. Whether it's creating shareable videos from...

Security Scan

The skill's code-free instructions, required credential (NEMO_TOKEN), and API usage align with a cloud video-rendering service; no signs of obvious misdirection or excessive permissions, though it will send user media to a third-party API and a small metadata inconsistency exists.

Purpose & Capability

The skill claims to create/export videos and its instructions exclusively describe calls to a video-rendering backend (session creation, upload, render, download). Requesting a single NEMO_TOKEN credential is proportionate to that purpose. Note: SKILL.md includes a configPaths entry (~/.config/nemovideo/) in its YAML metadata while the registry metadata lists no required config paths — a minor inconsistency in declared metadata.

Instruction Scope

Runtime instructions stay within the stated video-creation flow (create session, upload files, run SSE, export). The skill will generate an anonymous token if no NEMO_TOKEN is present and will upload user media to https://mega-api-prod.nemovideo.ai. It also instructs deriving an attribution header value from the agent install path (reading install path to infer X-Skill-Platform), which is reasonable but means the skill reads some environment/installation context beyond just the provided token.

Install Mechanism

There is no install spec and no code files; this is instruction-only so nothing is downloaded or written to disk by the skill itself. That minimizes install-time risk.

Credentials

Only one credential (NEMO_TOKEN) is required and justified by the API calls. The SKILL.md also documents creating an anonymous token if NEMO_TOKEN is missing, which reduces the need for long-lived secrets but means the agent will call an auth endpoint automatically. The YAML metadata's configPaths field (~/.config/nemovideo/) is declared in the skill file but not in registry metadata — if the skill reads that path at runtime it could access local config, so verify whether your agent will expose those files.

Persistence & Privilege

always is false and the skill is user-invocable; disable-model-invocation is false (normal). The skill does not request permanent system-level presence or to modify other skills. Note that autonomous invocation is allowed by default on the platform — combined with network access this means the skill can contact the remote API when invoked.

Assessment

This skill appears coherent for its stated purpose, but it will upload whatever media the user supplies to a third-party API (mega-api-prod.nemovideo.ai) and may generate/obtain an anonymous token if no NEMO_TOKEN is supplied. Before installing or using it: (1) confirm you trust that remote service and are comfortable with your media and any metadata being transmitted and stored there; (2) avoid uploading sensitive content (private documents, PII, proprietary images) unless you’ve verified the service’s privacy terms; (3) be aware the skill may read some local agent/installation context to set headers (the SKILL.md lists a config path in its metadata) — if you want to be cautious, run it in a restricted environment or supply an explicit NEMO_TOKEN; (4) the skill’s registry/metadata had a small mismatch about config paths — consider asking the author for clarification or checking logs to see what local paths it actually reads.

Getting Started

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

Try saying:

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

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 for Free Download — Create and Export Videos Free

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 product photos and a background music file and want to combine these photos into a 30-second video with transitions and text overlays — the backend processes it in about 30-60 seconds and hands you a 1080p MP4.

Tip: keeping your source clips under 2 minutes each speeds up processing noticeably.

Matching Input to Actions

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

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.

Headers are derived from this file's YAML frontmatter. X-Skill-Source is video-maker-for-free-download, X-Skill-Version comes from the version field, and X-Skill-Platform is detected from the install path (~/.clawhub/ = clawhub, ~/.cursor/skills/ = cursor, otherwise unknown).

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 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

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 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 "combine these photos into a 30-second video with transitions 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.

Common Workflows

Quick edit: Upload → "combine these photos into a 30-second video with transitions 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.