Ai Video Generator Free I

generate text or images into ready-to-share videos with this skill. Works with MP4, MOV, JPG, PNG files up to 200MB. content creators use it for generating v...

Security Scan

The skill's described functionality (cloud video generation) matches its runtime instructions, but there are inconsistencies and privacy/visibility concerns (automatic anonymous token minting, implicit storage of session/token, and mismatched declared config paths) that warrant caution before installing.

Purpose & Capability

The skill's name and description (generate videos from text/images via a cloud backend) align with the API calls and upload/export flows in SKILL.md. Requesting a single service token (NEMO_TOKEN) is appropriate for a cloud service. However, the SKILL.md frontmatter lists a configPaths entry (~/.config/nemovideo/) while the registry metadata indicated no required config paths — this mismatch should be clarified.

Instruction Scope

At first-run the skill automatically POSTs to external endpoints to mint an anonymous token and create a session, and it instructs the agent to persist the session_id for later calls. It also instructs reading the skill's YAML frontmatter and probing install paths to set attribution headers. These are within the purpose (talking to the video backend), but the automatic, silent network activity and instructions to hide raw API responses/tokens from the user reduce visibility and control — a privacy/consent concern.

Install Mechanism

There is no install spec and no code files; the skill is instruction-only, which minimizes disk-write and supply-chain risk.

Credentials

The skill requires a single credential (NEMO_TOKEN) which is proportionate. It explicitly supports obtaining an anonymous token if none is provided. However, the SKILL.md metadata references a config path that may be used to read or store tokens/sessions (~/.config/nemovideo/) despite the registry summary listing no required config paths — this extra filesystem access should be justified.

Persistence & Privilege

always:false (no forced inclusion), and autonomous invocation is normal. The skill does instruct storing session tokens and possibly using a config directory for persistence; that is a reasonable behavior for a long-running session, but it increases the window for stale credentials and means the skill will create persistent state on the host unless the user opts out.

What to consider before installing

This skill appears to do what it says (upload media and call a cloud rendering API), but it will automatically call external endpoints on first use to mint an anonymous token and create a session, and it may persist session/token data (SKILL.md mentions ~/.config/nemovideo/). The source and homepage are unknown — before installing, consider: (1) Do you trust the domain mega-api-prod.nemovideo.ai to handle your media and personal data? (2) If you prefer control, set NEMO_TOKEN yourself rather than allowing anonymous token minting. (3) Ask the publisher to clarify the config path behavior and where session data is stored, and request a privacy policy. If you need stronger guarantees, avoid using the skill until its source and storage behavior are verified.

Getting Started

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

Try saying:

• "generate my text or images"
• "export 1080p MP4"
• "create a 30-second promotional video from"

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.

AI Video Generator Free — Generate Videos from Text Free

This tool takes your text or images 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 product description or three brand images and want to create a 30-second promotional video from my product photos — the backend processes it in about 1-2 minutes and hands you a 1080p MP4.

Tip: shorter scripts generate faster and stay under free tier limits.

Matching Input to Actions

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

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

• X-Skill-Source: ai-video-generator-free-i
• X-Skill-Version: from frontmatter version
• X-Skill-Platform: detect from install path (~/.clawhub/ → clawhub, ~/.cursor/skills/ → cursor, else unknown)

Include Authorization: Bearer <NEMO_TOKEN> and all attribution headers on every request — omitting them triggers a 402 on export.

API base: https://mega-api-prod.nemovideo.ai

Create session: POST /api/tasks/me/with-session/nemo_agent — body {"task_name":"project","language":"<lang>"} — returns task_id, session_id.

Send message (SSE): POST /run_sse — body {"app_name":"nemo_agent","user_id":"me","session_id":"<sid>","new_message":{"parts":[{"text":"<msg>"}]}} with Accept: text/event-stream. Max timeout: 15 minutes.

Upload: POST /api/upload-video/nemo_agent/me/<sid> — file: multipart -F "files=@/path", or URL: {"urls":["<url>"],"source_type":"url"}

Credits: GET /api/credits/balance/simple — returns available, frozen, total

Session state: GET /api/state/nemo_agent/me/<sid>/latest — key fields: data.state.draft, data.state.video_infos, data.state.generated_media

Export (free, no credits): POST /api/render/proxy/lambda — body {"id":"render_<ts>","sessionId":"<sid>","draft":<json>,"output":{"format":"mp4","quality":"high"}}. Poll GET /api/render/proxy/lambda/<id> every 30s until status = completed. Download URL at output.url.

Supported formats: mp4, mov, avi, webm, mkv, jpg, png, gif, webp, mp3, wav, m4a, aac.

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.

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

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)

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 → "create a 30-second promotional video from my product photos" → 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 "create a 30-second promotional video from my product photos" — 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.