Ai Video Generator Free Best

Turn a short product description and three product photos into 1080p ready-to-share videos just by typing what you need. Whether it's generating videos from...

Security Scan

The skill's declared purpose (cloud AI video generation) matches its instructions and requested credential (NEMO_TOKEN); nothing in the SKILL.md asks for unrelated secrets or installs arbitrary code.

Purpose & Capability

Name and description describe a cloud video-generation service; the only required credential is NEMO_TOKEN and the API endpoints in the instructions match that purpose. The declared config path (~/.config/nemovideo/) and session-based workflow are plausible for this service.

Instruction Scope

Instructions are focused on connecting to the remote API, session management, uploads, SSE handling, credits, and exports. They instruct the agent to POST for anonymous tokens if NEMO_TOKEN is absent and to upload user files to the remote service — which is expected for this skill but means user content (images/text) will be transmitted to the external API. The text mentions detecting an install path to set an attribution header; that implies reading environment/paths but is limited and explained.

Install Mechanism

No install spec or code files — instruction-only skill. Nothing is downloaded or written to disk by a packaged installer, minimizing install-time risk.

Credentials

Only NEMO_TOKEN is required (declared as primaryEnv). The SKILL.md does not request other unrelated secrets. It will also use or create an anonymous token if NEMO_TOKEN is not present — this behavior is documented in the instructions.

Persistence & Privilege

always is false and the skill is user-invocable; it doesn't request persistent system privileges or modify other skills. Declared configPaths are limited to the service's config directory and are plausible for a client that caches tokens or settings.

Assessment

This skill appears coherent for a cloud video-generation service, but note these practical privacy/security points before installing: - The skill will upload your images and text to https://mega-api-prod.nemovideo.ai; do not send confidential or sensitive images or text. - If you set NEMO_TOKEN in your environment, the skill will reuse that token — ensure it is a limited-scope token or revoke it if you are unsure. If NEMO_TOKEN is absent the skill will obtain an anonymous token (100 free credits) from the service. - The skill may read ~/.config/nemovideo/ or detect known install paths to populate an attribution header; ensure no sensitive secrets are stored there. - Verify the API domain (nemovideo.ai) is the legitimate service you expect before providing content or credentials. If you are uncomfortable with uploading content or exposing a token, do not set NEMO_TOKEN and avoid using the skill.

Getting Started

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

Try saying:

• "generate my text or images"
• "export 1080p MP4"
• "create a 30-second promotional video from"

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.

AI Video Generator Free Best — Generate Videos from Text or Images

This tool takes your text or images and runs AI video generation through a cloud rendering pipeline. You upload, describe what you want, and download the result.

Say you have a short product description and three product photos and want to create a 30-second promotional video from my text and images — the backend processes it in about 1-2 minutes and hands you a 1080p MP4.

Tip: shorter scripts under 60 words produce faster and more focused video results.

Matching Input to Actions

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

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

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.

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

Common Workflows

Quick edit: Upload → "create a 30-second promotional video from my text and images" → 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 "create a 30-second promotional video from my text and images" — concrete instructions get better results.

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

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