Ai Video Generator Free Lifetime

Turn a short product description and three product photos into 1080p finished MP4 videos just by typing what you need. Whether it's generating videos from te...

Security Scan

The skill's declared requirements and metadata mostly match its stated video-rendering purpose, but small inconsistencies (required NEMO_TOKEN vs. auto-creation flow, a declared configPath that the instructions don't use) and the fact that it will upload user files and request a Bearer token suggest you should review token use and data-exfiltration implications before installing.

Purpose & Capability

Name/description align with a cloud video-rendering service and the declared primary credential (NEMO_TOKEN) and API host match that purpose. However the metadata requires NEMO_TOKEN while the instructions describe an anonymous-token acquisition flow when NEMO_TOKEN is absent — that's inconsistent but explainable (it allows either pre-provisioned tokens or anonymous use). The metadata also lists a config path (~/.config/nemovideo/) that is not referenced in the runtime instructions, which is unexpected.

Instruction Scope

SKILL.md contains detailed runtime instructions limited to interacting with the external nemovideo API: creating sessions, sending SSE messages, uploading files, polling renders, and reporting credits/status. It does not instruct reading unrelated system files or other credentials. It will upload user-provided images/files and transmit them to the external service — that is necessary for the stated function but has privacy implications.

Install Mechanism

This is an instruction-only skill with no install spec and no code files, so nothing gets written to disk by an installer. That lowers local install risk.

Credentials

The skill declares a single primary credential (NEMO_TOKEN), which fits a cloud API integration. But the metadata's required env var plus a fallback anonymous-token flow is inconsistent: the skill will create/use an anonymous token if NEMO_TOKEN is not present. The metadata also lists a config path (~/.config/nemovideo/) that the instructions do not actually reference — requesting access to a user config directory without justification is disproportionate. Also note that if you set NEMO_TOKEN it will be used as a Bearer token for all requests, so don't set a high-privilege/long-lived secret here unless you intend uploads and renders to use it.

Persistence & Privilege

always is false and the skill does not request or attempt to modify other skills or system-wide settings. It does not require persistent installation or elevated privileges in the agent.

What to consider before installing

This skill will send your text and any images you provide to https://mega-api-prod.nemovideo.ai and will use a Bearer token named NEMO_TOKEN (or create an anonymous token for you). Before installing: 1) Decide whether you are comfortable uploading the images/content to that external service and check their privacy/retention policy; 2) Do not put other sensitive credentials into NEMO_TOKEN — prefer a dedicated, limited token or let the skill use its anonymous token flow; 3) The metadata mentions ~/.config/nemovideo/ even though the runtime steps don't use it — avoid granting the agent access to unrelated config dirs; 4) Because this is instruction-only, no local code runs, but the agent will make network calls and upload files, so treat it like a network-connected plugin. If you need higher assurance, request the service's owner/source and a privacy/terms link before proceeding.

Getting Started

Share your text or images and I'll get started on AI video creation. 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"

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.

AI Video Generator Free Lifetime — Generate Videos from Text Free

Drop your text or images 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 a short product description and three product photos, ask for create a 30-second promotional video from my text and images, 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 under 60 seconds render significantly faster and use fewer credits.

Matching Input to Actions

User prompts referencing ai video generator free lifetime, 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-video-generator-free-lifetime
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 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 → "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, MOV, JPG, PNG for the smoothest experience.

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