Free Video Generation Model Ai

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's requirements and runtime instructions are consistent with a cloud video-generation integration: it only needs a single service token and instructs the agent how to call the vendor API and manage a session.

Purpose & Capability

The name/description (AI video generation) matches the declared requirement (NEMO_TOKEN) and the SKILL.md endpoints (nemovideo.ai). Requiring an API token and session management is appropriate for a cloud render pipeline that accepts uploads and returns download URLs.

Instruction Scope

The SKILL.md stays within the stated purpose (session creation, SSE for edits, uploads, export/polling). It instructs the agent to obtain an anonymous token if none is present, store session_id, and include attribution headers. Two small scope notes: (1) it instructs detecting the agent's install path (e.g., ~/.clawhub/) to set X-Skill-Platform — this reads local path context and is narrow but should be considered by users who care about filesystem access; (2) the frontmatter requests a config path (~/.config/nemovideo/) but the top-level registry metadata said no config paths — this mismatch is likely benign but inconsistent.

Install Mechanism

There is no install spec and no code files — the skill is instruction-only. That minimizes risk because nothing is downloaded or written to disk by an installer.

Credentials

Only a single credential (NEMO_TOKEN) is declared as required and used for Authorization. The SKILL.md also documents a legitimate anonymous-token flow if the env var is absent (100 free credits, 7-day validity). No unrelated secrets or broad permissions are requested.

Persistence & Privilege

The skill does not request always:true and makes no claims about modifying other skills or system-wide config. It does instruct storing a session_id for the duration of interaction, which is typical and limited in scope.

Assessment

This skill appears to do what it says: it uploads media and text prompts to a nemovideo.ai backend and returns generated videos. Before installing, consider: (1) network activity — your files will be uploaded to https://mega-api-prod.nemovideo.ai, so review that service's privacy/data-retention policy if you plan to upload sensitive content; (2) token handling — the skill will create or use a NEMO_TOKEN (anonymous tokens are short-lived); know where session tokens are stored by your agent and whether you want them persisted; (3) filesystem reads — the skill may check common install/config paths to set an attribution header (X-Skill-Platform); this is minimal but worth noting if you restrict tools from reading your home directory. If any of those behaviors are unacceptable (uploading private videos, automatic token creation, or local path reads), do not enable the skill or inspect runtime logging/configuration to control where tokens and session state are stored.

Getting Started

Got text prompts to work with? Send it over and tell me what you need — I'll take care of the AI video generation.

Try saying:

• "generate a short text description of a sunset beach scene into a 1080p MP4"
• "generate a 10-second video clip of a futuristic city skyline at night"
• "generating short video clips from text prompts for free 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 Model AI — Generate Videos From Text Prompts

This tool takes your text prompts 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 description of a sunset beach scene and want to generate a 10-second video clip of a futuristic city skyline at night — 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 video results.

Matching Input to Actions

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

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.

Skill attribution — read from this file's YAML frontmatter at runtime:

• X-Skill-Source: free-video-generation-model-ai
• X-Skill-Version: from frontmatter version
• X-Skill-Platform: detect from install path (~/.clawhub/ → clawhub, ~/.cursor/skills/ → cursor, else 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 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)

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

Tips and Tricks

The backend processes faster when you're specific. Instead of "make it look better", try "generate a 10-second video clip of a futuristic city skyline at night" — 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 platforms and devices.

Common Workflows

Quick edit: Upload → "generate a 10-second video clip of a futuristic city skyline at night" → 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.