Best Free Video Generation Tools

Turn a short text description like 'a sunset over the ocean with calm waves' into 1080p AI-generated videos just by typing what you need. Whether it's genera...

Security Scan

The skill appears to do what it says (drive an external NemoVideo API to generate videos) and only requests a single service token; minor documentation/metadata inconsistencies and some privacy considerations are noted.

Purpose & Capability

The skill's name/description match the instructions (calls to mega-api-prod.nemovideo.ai to create sessions, upload media, render and download). Requiring a NEMO_TOKEN is coherent. Minor inconsistency: the top-level registry summary lists no required config paths, but the SKILL.md frontmatter metadata includes a config path (~/.config/nemovideo/). This likely means the skill intends to persist session/token metadata to a config directory but the registry metadata wasn't updated to reflect that.

Instruction Scope

Instructions are narrowly scoped to interacting with the NemoVideo API (auth, session management, SSE, upload, render, credits/status). They explicitly describe obtaining an anonymous token if NEMO_TOKEN is absent. Two items to be aware of: (1) upload instructions include multipart uploads referencing local file paths (files=@/path) — the agent will need access to any local files you ask it to upload; (2) the skill asks to auto-detect an install path/platform and send it via an X-Skill-Platform header, which could expose agent install-path information to the external service. Otherwise the instructions do not request unrelated files or credentials.

Install Mechanism

This is an instruction-only skill with no install spec and no code files. That minimizes risk from arbitrary downloads or writes during install.

Credentials

Only one environment variable is declared as required: NEMO_TOKEN (primary). That is proportional for a cloud API integration. The SKILL.md shows the skill can obtain an anonymous token itself when NEMO_TOKEN is not set, which reduces the need for the user to provide secrets. The metadata/config-path mismatch (see Purpose) is a small coherence issue but not a broad credential request.

Persistence & Privilege

The skill does not request always:true or system-level privileges. It stores a session_id and may persist token/session data (implied by the config path), but this is limited to its own config area and consistent with its function.

Assessment

This skill calls an external service (mega-api-prod.nemovideo.ai) to do all video generation. It will create or use a NEMO_TOKEN and store a session_id; the SKILL.md implies a config directory (~/.config/nemovideo/) may be used to persist state. Before installing: (1) confirm you are comfortable sending media and prompts to that external service; do not send sensitive files. (2) If you prefer not to allow the skill to create anonymous tokens for you, set your own NEMO_TOKEN in advance. (3) Be aware the skill may send an X-Skill-Platform value derived from the agent install path—this can leak minor environment information. (4) The only real inconsistency is a metadata/config-path mismatch in the registry; if you need guarantees about where tokens/sessions are stored, ask the author or inspect where the agent persists the session data.

Getting Started

Ready when you are. Drop your text prompts or images here or describe what you want to make.

Try saying:

• "generate a short text description like 'a sunset over the ocean with calm waves' into a 1080p MP4"
• "generate a 15-second video clip from my product description with background music"
• "generating short videos from text prompts or images without a camera for content creators, marketers, students"

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.

Best Free Video Generation Tools — Generate Videos from Text or Images

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

Here's a typical use: you send a a short text description like 'a sunset over the ocean with calm waves', ask for generate a 15-second video clip from my product description 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, more specific prompts tend to produce more accurate and usable results.

Matching Input to Actions

User prompts referencing best free video generation tools, 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	best-free-video-generation-tools
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.

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

Tips and Tricks

The backend processes faster when you're specific. Instead of "make it look better", try "generate a 15-second video clip from my product description with background music" — concrete instructions get better results.

Max file size is 200MB. Stick to MP4, MOV, PNG, JPG for the smoothest experience.

Export as MP4 for widest compatibility across social platforms and devices.

Common Workflows

Quick edit: Upload → "generate a 15-second video clip from my product description 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.