Best Free Video Generation

generate text prompts into AI generated videos with this skill. Works with MP4, MOV, WebM, GIF files up to 500MB. content creators use it for generating vide...

Security Scan

The skill's requirements and runtime instructions are consistent with a cloud video-generation service, but it relies on an external API (unknown origin) and will upload user media and obtain/handle tokens — review privacy and trust of the remote endpoint before use.

Purpose & Capability

Name/description (text→video, uploads, exports) match the declared runtime actions: session creation, SSE chat for edits, upload and export endpoints. Requesting a single service token (NEMO_TOKEN) and a config path for nemovideo is proportional to a remote video-rendering service.

Instruction Scope

SKILL.md only instructs calls to the nemovideo API and managing session/token state — within scope for a cloud render skill. Notable points: it will upload user media to a third-party domain and may create an anonymous token via an API call; it instructs to 'save session_id' and treat data returned as session state but does not specify persistent storage location for tokens. The file-transfer and token-acquisition behavior is expected but has privacy implications.

Install Mechanism

Instruction-only skill with no install spec or code files — lowest installation risk. Nothing is downloaded or written by an installer step in the package itself.

Credentials

Only NEMO_TOKEN is required (primary credential), which is appropriate. Metadata also lists a config path (~/.config/nemovideo/) — reasonable to store session/config files but the SKILL.md does not describe reading other unrelated credentials. The skill will generate and use an anonymous token if NEMO_TOKEN is not provided (7-day expiry).

Persistence & Privilege

always is false and the skill does not request system-wide privileges. Autonomous invocation is allowed (platform default). There is no instruction to modify other skills or system configurations.

Assessment

This skill appears to do what it says: it will upload your media and use a NEMO_TOKEN to call a remote API (mega-api-prod.nemovideo.ai) to create and render videos. Before installing or using it: 1) Verify you trust the remote service/domain and its privacy policy — your media will be transmitted to that endpoint. 2) Decide whether to set a persistent NEMO_TOKEN (your account token) or let the skill request an anonymous 7-day token; avoid using sensitive credentials if unsure. 3) The skill may store session state (session_id) — confirm where it is stored if you need to delete history. 4) Because the skill’s source/homepage is unknown, prefer testing with non-sensitive sample files first. Providing the skill’s homepage, source code, or reputation information for the api domain would increase confidence.

Getting Started

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

Try saying:

• "generate my text prompts"
• "export 1080p MP4"
• "generate a 30-second video of a"

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.

Best Free Video Generation — Generate Videos from Text Prompts

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

Say you have a short text prompt describing a sunset beach scene and want to generate a 30-second video of a product launch with background music — the backend processes it in about 1-2 minutes and hands you a 1080p MP4.

Tip: shorter, more specific prompts tend to produce more accurate results.

Matching Input to Actions

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

All calls go to https://mega-api-prod.nemovideo.ai. The main endpoints:

1. Session — POST /api/tasks/me/with-session/nemo_agent with {"task_name":"project","language":"<lang>"}. Gives you a session_id.
2. Chat (SSE) — POST /run_sse with session_id and your message in new_message.parts[0].text. Set Accept: text/event-stream. Up to 15 min.
3. Upload — POST /api/upload-video/nemo_agent/me/<sid> — multipart file or JSON with URLs.
4. Credits — GET /api/credits/balance/simple — returns available, frozen, total.
5. State — GET /api/state/nemo_agent/me/<sid>/latest — current draft and media info.
6. Export — POST /api/render/proxy/lambda with render ID and draft JSON. Poll GET /api/render/proxy/lambda/<id> every 30s for completed status and download URL.

Formats: 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 best-free-video-generation, 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).

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.

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)

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

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.

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 → "generate a 30-second video of a product launch 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.

Tips and Tricks

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

Max file size is 500MB. Stick to MP4, MOV, WebM, GIF for the smoothest experience.

Export as MP4 for widest compatibility across all platforms.