Free Video Maker Ai

Skip the learning curve of professional editing software. Describe what you want — turn these photos into a 30-second promo video with music and text — and g...

Security Scan

The skill's runtime instructions mostly match a cloud video-rendering capability, but there are modest inconsistencies and privacy risks (unknown service origin, metadata asking for a config path that isn't used, and required uploads of user files to an external API).

Purpose & Capability

The name/description (AI video creation) aligns with the API endpoints and flows in SKILL.md. Requesting a NEMO_TOKEN credential is coherent for a third‑party rendering service. However, the metadata lists a config path (~/.config/nemovideo/) that the instructions never reference — a minor mismatch that raises a question about whether the skill intends to read local config files.

Instruction Scope

Instructions direct the agent to obtain/use a bearer token, create sessions, stream via SSE, and upload user files (MP4/MOV/JPG/PNG up to 500MB) to https://mega-api-prod.nemovideo.ai. Uploading user content to a third‑party service is expected for this functionality but is a clear privacy/exfiltration risk that users should understand. The skill also instructs the agent to read YAML frontmatter and infer an install path for attribution headers — detecting the agent install path could require filesystem context outside the skill file itself.

Install Mechanism

No install spec and no code files: instruction-only skill. This minimizes disk writes and arbitrary installs and is lower risk from an installation perspective.

Credentials

Only one required env var (NEMO_TOKEN), which is proportionate for an API client. The SKILL metadata also lists a config path (~/.config/nemovideo/) even though the SKILL.md doesn't instruct reading it — this mismatch is unexplained. The skill also describes an anonymous-token flow so it can operate without a pre-existing NEMO_TOKEN, which reduces but does not eliminate credential concerns.

Persistence & Privilege

always is false and there is no install-time persistence. The skill instructs saving session_id for the session lifecycle, but doesn't require writing to system-wide settings or modifying other skills. Autonomous invocation is allowed (platform default) but not combined with unusually broad privileges here.

What to consider before installing

This skill appears to do what it says (upload your media to a cloud render service and return an MP4), but you should be cautious before installing or using it: 1) The service domain (mega-api-prod.nemovideo.ai) and the skill owner have no homepage or published information — verify the provider and review its privacy/terms before sending content. 2) The skill uploads user files (potentially sensitive) to a third‑party API — do not upload private/confidential media unless you trust the service. 3) NEMO_TOKEN is the API credential; prefer an anonymous/ephemeral token if possible and rotate/revoke tokens after use. 4) Ask the publisher (or avoid using) why a config path (~/.config/nemovideo/) is listed in metadata but never referenced in the instructions. 5) If you need to test, try with non-sensitive sample media and monitor network activity; request a privacy policy or official homepage from the author before uploading real data.

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"
• "turn these photos 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.

Free Video Maker AI — Create and Export Videos Free

This tool takes your images or clips 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 logo file and want to turn these photos into a 30-second promo video with music and text — the backend processes it in about 30-60 seconds and hands you a 1080p MP4.

Tip: using fewer than 10 clips keeps render time under a minute.

Matching Input to Actions

User prompts referencing free video maker ai, 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: free-video-maker-ai
• X-Skill-Version: from frontmatter version
• X-Skill-Platform: detect from install path (~/.clawhub/ → clawhub, ~/.cursor/skills/ → cursor, else unknown)

Every API call needs Authorization: Bearer <NEMO_TOKEN> plus the three attribution headers above. If any header is missing, exports return 402.

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.

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)

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 → "turn these photos into a 30-second promo video with music and text" → 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 "turn these photos into a 30-second promo video with music and text" — 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.