Ai Create Video Free

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

Security Scan

The skill's requirements and instructions are largely consistent with a cloud video-rendering integration, but it will automatically contact a third-party API and upload user media — review privacy implications and a small metadata inconsistency before installing.

Purpose & Capability

Name and description claim cloud video creation; declared primaryEnv (NEMO_TOKEN) and the SKILL.md REST endpoints (nemovideo.ai) directly correspond to that purpose. No unrelated credentials or binaries are requested.

Instruction Scope

The runtime instructions direct the agent to automatically obtain an anonymous token (if NEMO_TOKEN not present), create sessions, upload files (up to 500MB), stream SSE events, and poll render status. These are expected for a cloud render service, but they imply automatic network calls and sending user files to a third-party. The SKILL.md frontmatter also lists a config path (~/.config/nemovideo/) while the registry metadata lists no required config paths — that mismatch is unexplained.

Install Mechanism

This is an instruction-only skill with no install spec and no code files, so nothing is written to disk by the skill itself. Lowest install risk.

Credentials

Only a single credential (NEMO_TOKEN) is required, which is proportionate for a remote API. The skill also describes how to auto-generate an anonymous token if none is present; that behavior is sensible but worth noting because it causes outward network activity and stored session state.

Persistence & Privilege

always:false and no special system-wide privileges are requested. The skill asks the agent to store a session_id for ongoing requests; this is normal for session-based APIs and does not alter other skills or global agent settings.

Assessment

This skill will send your uploaded images/text to https://mega-api-prod.nemovideo.ai for cloud rendering and may automatically obtain an anonymous token if you haven't supplied NEMO_TOKEN. Before installing, consider: 1) privacy — do not upload sensitive PII or proprietary assets unless you trust the service and its retention policy; 2) token behavior — the skill can generate and store anonymous tokens/sessions automatically; decide whether you prefer to provide your own NEMO_TOKEN or disallow the skill from auto-connecting; 3) metadata mismatch — the SKILL.md references a config path (~/.config/nemovideo/) but the registry shows no required config paths; ask the publisher to clarify where session data will be stored. If these behaviors are acceptable for your use case, the skill appears coherent for cloud video creation.

Getting Started

Got images or text 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 product photos and a caption into a 1080p MP4"
• "turn these images into a 30-second promo video with background music"
• "generating videos from images or text prompts for content creators and marketers"

First-Time Connection

When a user first opens this skill, connect to the processing backend automatically. Briefly let them know (e.g. "Setting up...").

Authentication: Check if NEMO_TOKEN is set in the environment. If it is, skip to step 2.

1. Obtain a free token: Generate a random UUID as client identifier. POST to https://mega-api-prod.nemovideo.ai/api/auth/anonymous-token with header X-Client-Id set to that UUID. The response data.token is your NEMO_TOKEN — 100 free credits, valid 7 days.
2. Create a session: POST to https://mega-api-prod.nemovideo.ai/api/tasks/me/with-session/nemo_agent with Authorization: Bearer <token>, Content-Type: application/json, and body {"task_name":"project","language":"<detected>"}. Store the returned session_id for all subsequent requests.

Keep setup communication brief. Don't display raw API responses or token values to the user.

AI Create Video Free — Create Videos from Images or Text

Drop your images or text 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 caption, ask for turn these images into a 30-second promo video with background music, 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 — shorter scripts and fewer images produce faster results.

Matching Input to Actions

User prompts referencing ai create video 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.

Three attribution headers are required on every request and must match this file's frontmatter:

Header	Value
X-Skill-Source	ai-create-video-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.

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