Free Video Generation Ai Model

Get AI generated videos ready to post, without touching a single slider. Upload your text prompts (MP4, MOV, WebM, GIF, up to 500MB), say something like "gen...

Security Scan

The skill largely does what it claims (upload prompts/files and call a remote video-rendering API), but there are metadata inconsistencies, missing provenance, and ambiguous handling/storage of tokens/session data that warrant caution before installing or using with sensitive content.

Purpose & Capability

The skill's declared purpose (text→video via a remote GPU service) matches the runtime instructions (upload files, POST to nemovideo endpoints, poll render status). However there is no homepage/source repo and the registry metadata and the SKILL.md frontmatter disagree about config paths; absence of provenance reduces auditability.

Instruction Scope

Runtime instructions will automatically obtain an anonymous token (if NEMO_TOKEN not set), create a session, upload user media (up to 500MB) and send prompts to https://mega-api-prod.nemovideo.ai. The skill tells the agent to store session_id and use tokens but gives no secure-storage guidance. It does not request unrelated system files, but uploading user files and prompts to an external service is intrinsic and should be expected and explicitly consented to by users.

Install Mechanism

Instruction-only skill with no install steps and no code files — lowest install risk. Nothing will be written by a packaged installer according to the provided metadata.

Credentials

The only credential referenced is NEMO_TOKEN (declared primaryEnv). SKILL.md, however, instructs the agent to auto-request an anonymous token when NEMO_TOKEN is absent, so requiring NEMO_TOKEN upstream is inconsistent. The SKILL.md frontmatter also lists a config path (~/.config/nemovideo/) while the registry metadata said none — this mismatch should be clarified.

Persistence & Privilege

The skill does not request 'always: true' and allows normal agent invocation rules. It asks the agent to persist session_id/token for the session lifecycle, which is expected for a remote service but should be stored securely by the platform.

What to consider before installing

This skill will upload your prompts and media to mega-api-prod.nemovideo.ai and may create an anonymous API token for you; there is no homepage or source code to verify. Before installing: confirm you trust that external service and avoid uploading sensitive or proprietary content. Ask the publisher for a privacy/security policy or source repository. Clarify where session tokens are stored and whether data is retained/used for model training. If you must test it, run in a restricted/sandboxed environment or with non-sensitive sample media. The metadata mismatches (configPaths present in SKILL.md frontmatter but not in registry metadata, and the described auto-token flow vs. declared required env var) should be resolved by the publisher — treat those inconsistencies as reasons for extra caution.

Getting Started

Send me your text prompts and I'll handle the AI video generation. Or just describe what you're after.

Try saying:

• "generate a short text description like 'a sunset over a mountain lake with calm music' into a 1080p MP4"
• "generate a 30-second video from my text prompt with cinematic style"
• "generating videos from text prompts without any footage for content creators"

First-Time Connection

When a user first opens this skill, connect to the processing backend automatically. Briefly let them know (e.g. "Setting up...").

Authentication: Check if NEMO_TOKEN is set in the environment. If it is, skip to step 2.

1. Obtain a free token: Generate a random UUID as client identifier. POST to https://mega-api-prod.nemovideo.ai/api/auth/anonymous-token with header X-Client-Id set to that UUID. The response data.token is your NEMO_TOKEN — 100 free credits, valid 7 days.
2. Create a session: POST to https://mega-api-prod.nemovideo.ai/api/tasks/me/with-session/nemo_agent with Authorization: Bearer <token>, Content-Type: application/json, and body {"task_name":"project","language":"<detected>"}. Store the returned session_id for all subsequent requests.

Keep setup communication brief. Don't display raw API responses or token values to the user.

Free Video Generation AI Model — Generate Videos from Text Prompts

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

A quick example: upload a short text description like 'a sunset over a mountain lake with calm music', type "generate a 30-second video from my text prompt with cinematic style", and you'll get a 1080p MP4 back in roughly 1-2 minutes. All rendering happens server-side.

Worth noting: shorter and more specific prompts produce more accurate results.

Matching Input to Actions

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

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

Header	Value
X-Skill-Source	free-video-generation-ai-model
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.

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)

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

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 video from my text prompt with cinematic style" → 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 from my text prompt with cinematic style" — 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.