Ai Video Generator Free Link

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 shareable vi...

Security Scan

The skill's instructions largely match a cloud video-generation workflow, but there are inconsistencies (declared config path in the skill frontmatter vs registry metadata) and a few implementation details that merit caution before installing or giving credentials.

Purpose & Capability

The name/description (AI video generation) align with the runtime instructions that call nemovideo.ai APIs to upload media, create sessions, and render videos. However, the SKILL.md frontmatter declares a config path (~/.config/nemovideo/) while the registry metadata lists no required config paths — this mismatch is unexplained and could indicate the skill expects to read local configuration or tokens that the registry didn't disclose.

Instruction Scope

The SKILL.md stays within the stated purpose: it checks for NEMO_TOKEN, optionally obtains an anonymous token from the service, creates a session, uploads files, streams SSE, and starts renders. It does not instruct reading arbitrary system files or unrelated credentials. The required attribution headers and use of SSE and render endpoints are consistent with a cloud-render workflow.

Install Mechanism

This is instruction-only (no install spec, no code files), so nothing is written to disk by an installer. That is the lowest install risk.

Credentials

The skill only requires a single credential (NEMO_TOKEN), which is proportionate for a cloud API. It also documents how to obtain an anonymous token automatically if none is present. That behavior is reasonable but worth noting: the agent will make network calls to mint tokens and must include the token in Authorization headers. The frontmatter's mention of a config path (possible local token/config storage) is not reflected in registry requirements — this could cause the skill to read or expect local config without the registry disclosing that.

Persistence & Privilege

always is false and the skill contains no install steps that request persistent system changes. It does not ask to modify other skills or global agent settings. The only potential persistence vector is the undocumented config path in SKILL.md where keys or client state might be read/written; the skill does not explicitly instruct writing tokens to disk.

What to consider before installing

This skill looks like a legitimate cloud video-generator that talks to nemovideo.ai, but proceed carefully: 1) the SKILL.md frontmatter references ~/.config/nemovideo/ while the registry did not — ask the publisher if the skill will read or write files there. 2) Only provide a NEMO_TOKEN you control (use an anonymous or limited-scope token if possible); avoid reusing long-lived credentials. 3) Expect media and prompts to be uploaded to mega-api-prod.nemovideo.ai — do not send sensitive content. 4) If you want to install, ask the author to clarify the config path behavior and whether tokens will be persisted locally, and confirm the authoritative homepage/source (the package currently lists no source).

Getting Started

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

Try saying:

• "generate a short product description and three product photos into a 1080p MP4"
• "generate a 30-second promotional video from my text and images with background music"
• "generating shareable videos from text prompts or images for free for content creators"

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 — Generate and Share Videos 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 generate a 30-second promotional video from my text and images 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 text prompts with clear instructions produce more accurate video results.

Matching Input to Actions

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

Base URL: https://mega-api-prod.nemovideo.ai

Endpoint	Method	Purpose
/api/tasks/me/with-session/nemo_agent	POST	Start a new editing session. Body: {"task_name":"project","language":"<lang>"}. Returns session_id.
/run_sse	POST	Send a user message. Body includes app_name, session_id, new_message. Stream response with Accept: text/event-stream. Timeout: 15 min.
/api/upload-video/nemo_agent/me/<sid>	POST	Upload a file (multipart) or URL.
/api/credits/balance/simple	GET	Check remaining credits (available, frozen, total).
/api/state/nemo_agent/me/<sid>/latest	GET	Fetch current timeline state (draft, video_infos, generated_media).
/api/render/proxy/lambda	POST	Start export. Body: {"id":"render_<ts>","sessionId":"<sid>","draft":<json>,"output":{"format":"mp4","quality":"high"}}. Poll status every 30s.

Accepted file types: mp4, mov, avi, webm, mkv, jpg, png, gif, webp, mp3, wav, m4a, aac.

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

Header	Value
X-Skill-Source	ai-video-generator-free-link
X-Skill-Version	frontmatter version
X-Skill-Platform	auto-detect: clawhub / cursor / unknown from install path

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

Error Handling

Code	Meaning	Action
0	Success	Continue
1001	Bad/expired token	Re-auth via anonymous-token (tokens expire after 7 days)
1002	Session not found	New session §3.0
2001	No credits	Anonymous: show registration URL with ?bind=<id> (get <id> from create-session or state response when needed). Registered: "Top up credits in your account"
4001	Unsupported file	Show supported formats
4002	File too large	Suggest compress/trim
400	Missing X-Client-Id	Generate Client-Id and retry (see §1)
402	Free plan export blocked	Subscription tier issue, NOT credits. "Register or upgrade your plan to unlock export."
429	Rate limit (1 token/client/7 days)	Retry in 30s once

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 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)

Tips and Tricks

The backend processes faster when you're specific. Instead of "make it look better", try "generate a 30-second promotional video from my text and images with background music" — 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.

Common Workflows

Quick edit: Upload → "generate a 30-second promotional video from my text and images 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.