Video Generator For Free Ai

Get ready-to-share videos ready to post, without touching a single slider. Upload your text or images (MP4, MOV, JPG, PNG, up to 200MB), say something like "...

Security Scan

The skill's declared requirements and runtime instructions are broadly consistent with a remote video-rendering integration, but there are a few metadata inconsistencies and privacy/operational considerations you should review before enabling it.

Purpose & Capability

The skill claims to generate videos via a remote API and only requests a single API credential (NEMO_TOKEN) needed to call that API. The endpoints, upload, session, credits, and render flows in SKILL.md align with a cloud video-rendering service. No unrelated cloud/provider credentials or unrelated binaries are requested.

Instruction Scope

The instructions focus on authenticating, creating sessions, uploading media, streaming SSE responses, polling render status, and returning a download URL — all within the stated purpose. They instruct the agent to persist a session_id and to not print tokens/raw JSON. One minor scope creep: SKILL.md describes detecting the install path to set an X-Skill-Platform header (it infers ~/.clawhub/ and ~/.cursor/skills/), which implies reading or inspecting the agent's filesystem/install path; the registry metadata does not list any required config paths but the SKILL.md frontmatter does include a configPaths entry (~/.config/nemovideo/). That mismatch should be clarified.

Install Mechanism

This is an instruction-only skill with no install spec and no code files — lowest-risk install profile because nothing is downloaded or written by an install step.

Credentials

Only NEMO_TOKEN is declared as required and is used as the Bearer token for API calls; SKILL.md also supports anonymous-token creation when no token is present. That is proportionate to the stated purpose. Watch for the apparent metadata mention of a config path (~/.config/nemovideo/) which was not listed in the registry's required config paths; if the skill will read/write that path, you should know what is stored there.

Persistence & Privilege

The skill is not marked always:true and has no installer so it doesn't request elevated persistence. It does instruct the agent to save session_id and to reuse tokens when present, which is normal for session-based APIs. No instructions attempt to modify other skills or global agent configuration.

Assessment

This skill appears to do what it says: it talks to a remote video-rendering API and requires a single API token. Before installing, consider: (1) There is no homepage or known source — verify the domain (mega-api-prod.nemovideo.ai) and the provider's reputation and privacy policy. Uploaded media and generated content will be sent to that external service. (2) Confirm how and where the agent will store the session_id and any tokens locally (the frontmatter mentions ~/.config/nemovideo/) and whether you are comfortable with that. (3) The skill may check your install path to set X-Skill-Platform, which could read your home directory/install locations — ask the author to clarify exactly what filesystem reads/writes occur. (4) If you handle sensitive assets, avoid uploading them until you trust the service and know retention/policy details. If you want higher assurance, request a source repo, a privacy/security policy, or an explanation of the apparent metadata/configPath mismatch.

Getting Started

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

Try saying:

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

Automatic Setup

On first interaction, connect to the processing API before doing anything else. Show a brief status like "Setting things up...".

Token: If NEMO_TOKEN environment variable is already set, use it and skip to Session below.

Free token: Generate a UUID as client identifier, then POST to https://mega-api-prod.nemovideo.ai/api/auth/anonymous-token with header X-Client-Id: <uuid>. The response field data.token becomes your NEMO_TOKEN (100 credits, 7-day expiry).

Session: POST to https://mega-api-prod.nemovideo.ai/api/tasks/me/with-session/nemo_agent with Bearer auth and body {"task_name":"project"}. Save session_id from the response.

Confirm to the user you're connected and ready. Don't print tokens or raw JSON.

Video Generator for Free AI — Generate Videos from Text Free

Send me your text or images and describe the result you want. The AI video creation runs on remote GPU nodes — nothing to install on your machine.

A quick example: upload a short text prompt or three product photos, type "generate a 30-second video from my product description", and you'll get a 1080p MP4 back in roughly 1-2 minutes. All rendering happens server-side.

Worth noting: shorter prompts with clear details produce more accurate video output.

Matching Input to Actions

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

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

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

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)

Tips and Tricks

The backend processes faster when you're specific. Instead of "make it look better", try "generate a 30-second video from my product description" — 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.

Common Workflows

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