Free Video Generator Best

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

Security Scan

The skill's requirements and runtime instructions are coherent for a cloud video-generation connector, but it will upload user media to an external service (and can obtain an anonymous token if none is provided), so you should only use it with non-sensitive content or after verifying the service.

Purpose & Capability

The skill is a cloud video-generation front end and declares/uses a single service credential (NEMO_TOKEN) and a nemovideo config path; these map directly to its described backend API endpoints and session flow, so the requested items are appropriate for the stated purpose.

Instruction Scope

SKILL.md instructs the agent to check for NEMO_TOKEN, otherwise obtain an anonymous token via POST to mega-api-prod.nemovideo.ai, create a session, upload user media (up to 500MB), stream SSE for edits, poll render status, and return download URLs. All of this is within the expected scope for a cloud video-renderer, but it explicitly uploads user files and will generate/use credentials automatically—users should be aware media and metadata go to an external API.

Install Mechanism

Instruction-only skill with no install spec and no code files; this is low-risk from an installation perspective (nothing is written to disk by an installer).

Credentials

Only one credential (NEMO_TOKEN) is declared, which is proportionate to a service-backed video generator. However, the skill will auto-request an anonymous token if none is supplied and will read/detect install path for attribution headers—this behaviour is reasonable but increases the chance of unintentionally sending sensitive content or telemetry to the external service.

Persistence & Privilege

The skill does not request always:true, does not modify other skills, and does not install persistent agents. Autonomous invocation is allowed but is the platform default and not elevated here.

Assessment

This skill acts as a client for an external video-rendering service (mega-api-prod.nemovideo.ai). It will upload any files you provide and will use or create an authentication token (NEMO_TOKEN) to do so. Before installing or running: (1) Don’t upload sensitive or private videos unless you trust the service; (2) Prefer creating a scoped/limited token or a throwaway account rather than exposing a high-privilege credential; (3) Note the skill will auto-create an anonymous token if none is present—expect your media and some metadata to leave your machine; (4) The skill’s source/homepage are unknown—try to verify the vendor or review privacy/terms on their site if possible. If you need this for public marketing clips it’s coherent; for private or regulated media, treat it as risky.

Getting Started

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

Try saying:

• "generate my text prompts or clips"
• "export 1080p MP4"
• "generate 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.

Free Video Generator Best — Generate Videos from Text Free

This tool takes your text prompts or clips 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 text prompt describing a product demo scene and want to generate a 30-second promotional video from my product description — the backend processes it in about 1-2 minutes and hands you a 1080p MP4.

Tip: shorter, specific prompts produce more accurate and faster results.

Matching Input to Actions

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

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 free-video-generator-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.

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)

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

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.

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 promotional 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.

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 product description" — concrete instructions get better results.

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

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