Ia Video Maker Free

create images or clips into polished MP4 videos with this skill. Works with MP4, MOV, JPG, PNG files up to 500MB. content creators and small business owners...

Security Scan

The skill mostly aligns with a cloud video-rendering purpose, but there are inconsistencies and a few instruction-level behaviors (local file access, a declared config path mismatch, and contacting an external API to mint anonymous tokens) that warrant caution before installing.

Purpose & Capability

The name/description (create polished MP4s from images/clips) matches the runtime instructions which call a nemo video API and upload media. Requesting a NEMO_TOKEN is expected. However, the registry header listed 'Required config paths: none' while the SKILL.md frontmatter includes a configPaths entry (~/.config/nemovideo/), which is an internal inconsistency that should be resolved.

Instruction Scope

The instructions explicitly tell the agent to: read NEMO_TOKEN from the environment (expected), or if missing, generate a UUID and POST to https://mega-api-prod.nemovideo.ai/api/auth/anonymous-token to obtain one. Upload instructions show multipart '-F "files=@/path"', which implies the agent will be expected to read files by filesystem path for uploading. That is reasonable for user-provided media, but the instructions do not clearly restrict uploads to only user-attached files. They also instruct deriving headers from local install/config paths (detecting ~/.clawhub/ or ~/.cursor/skills/), which requires reading the filesystem. These file-access instructions broaden scope (could be used to read arbitrary local files if the agent/platform allows) and are not tightly constrained in the SKILL.md.

Install Mechanism

No install spec / instruction-only skill — lowest install risk. Nothing will be written to disk by an installer in the skill bundle itself.

Credentials

Only NEMO_TOKEN is declared as required and is the primary credential — that is proportional for a cloud video service. The skill does, however, implement a flow to obtain an anonymous NEMO_TOKEN from an external endpoint if none is present, which means it will contact an external service automatically. The frontmatter's configPaths entry is inconsistent with the registry metadata and implies access to ~/.config/nemovideo/, which should be justified (e.g., to find an existing token).

Persistence & Privilege

always:false (normal). The skill says to keep session_id for operations but doesn't state where it will be stored (memory vs disk vs skill config). The lack of an install step limits permanent persistence, but the SKILL.md's mention of config paths and install-path detection suggests it may read local paths; combined with automatic anonymous token retrieval and session management, this increases the surface for persistent data (tokens/session IDs) — the behavior should be clarified.

What to consider before installing

This skill appears to do what it says (upload media and call a nemo video API), but there are a few things to consider before installing: 1) The SKILL.md instructs the agent to upload files by filesystem path and to inspect install/config paths — ensure your agent platform only allows uploading files you explicitly provide and does not allow arbitrary filesystem reads. 2) The skill will contact https://mega-api-prod.nemovideo.ai to mint an anonymous NEMO_TOKEN if none is present — verify that domain and the service are trustworthy for your data. 3) There is an internal metadata mismatch about config paths (~/.config/nemovideo/) — ask the author to clarify what local files the skill will read or write and where session tokens are stored. If you rely on strict privacy or have sensitive files on the machine, do not grant broad filesystem or environment access until these points are clarified.

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 images into a 30-second"

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.

IA Video Maker Free — Create and Export AI Videos

Drop your images or clips in the chat and tell me what you need. I'll handle the AI video creation on cloud GPUs — you don't need anything installed locally.

Here's a typical use: you send a five product photos and a logo file, ask for turn these images into a 30-second promo video with music and text, and about 1-2 minutes later you've got a MP4 file ready to download. The whole thing runs at 1080p by default.

One thing worth knowing — using fewer than ten images keeps generation time under a minute.

Matching Input to Actions

User prompts referencing ia 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.

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

Headers are derived from this file's YAML frontmatter. X-Skill-Source is ia-video-maker-free, 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

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

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)

Common Workflows

Quick edit: Upload → "turn these images into a 30-second promo video with music and text" → 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 "turn these images 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 and devices.