Free Video Generator Like Veo

Skip the learning curve of professional editing software. Describe what you want — generate a 10-second cinematic video of a sunset over mountains — and get...

Security Scan

The skill's requirements and instructions are consistent with a remote AI video-generation service and do not request unrelated credentials or install arbitrary code, though there are a couple of small metadata inconsistencies to be aware of.

Purpose & Capability

The skill's name and description match the actions in SKILL.md: it talks to a remote video-generation API, accepts uploads, creates sessions, polls rendering status and returns download URLs. The only mismatch is a small metadata inconsistency: the registry summary lists no required config paths, but the SKILL.md frontmatter includes a configPaths entry (~/.config/nemovideo/). This is likely benign but should be clarified.

Instruction Scope

Runtime instructions stay within the stated purpose: obtain/use NEMO_TOKEN (or request an anonymous token), create sessions, send messages via SSE, upload media, poll state and export endpoints. The doc asks the agent to read its own frontmatter and detect install path to set an attribution header — this requires limited filesystem access (skill bundle/install path) but is proportional to the stated attribution requirement. The instructions do not request unrelated system files, other credentials, or exfiltration to unexpected endpoints.

Install Mechanism

This is an instruction-only skill with no install spec and no code files, which is the lowest-risk install model.

Credentials

The only required environment variable is NEMO_TOKEN (declared as primaryEnv) and the SKILL.md provides a fallback to obtain an anonymous token if none is present. There are no unrelated secret requirements. Note again the SKILL.md frontmatter mentions ~/.config/nemovideo/ as a config path — the registry metadata elsewhere omitted this; confirm whether the skill will attempt to read that path if you are concerned about local config access.

Persistence & Privilege

The skill does not request always:true and does not modify other skills or system-wide settings. It may read its own file frontmatter and detect install path for attribution headers; these are limited privileges and consistent with its functionality. Autonomous invocation is enabled by default (normal for skills).

Assessment

This skill appears to do what it says: it calls a remote video-generation API and requires a single token (NEMO_TOKEN). Before installing, consider: 1) Only provide a token with the minimal scope and lifetime you are comfortable with (use a short-lived or anonymous token where possible). 2) The skill will call https://mega-api-prod.nemovideo.ai and may request an anonymous token from that host — verify you trust that endpoint and its privacy/terms. 3) There is a small metadata mismatch: SKILL.md mentions a local config path (~/.config/nemovideo/) while the registry summary did not; ask the publisher whether the skill will read that path if you want to be certain. 4) Because this is an instruction-only skill, no binaries are installed, but the agent will make network requests — avoid giving long-lived credentials if you are unsure. If you want extra safety, run with only an anonymous token (the skill supports obtaining one) or inspect network activity while testing.

Getting Started

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

Try saying:

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

Getting Connected

Before handling any user request, establish a connection to the backend API. Show a brief status like "Connecting...".

If NEMO_TOKEN is in the environment, use it directly and create a session. Otherwise, acquire a free starter token:

• Generate a UUID as client identifier
• POST to https://mega-api-prod.nemovideo.ai/api/auth/anonymous-token with the X-Client-Id header
• The response includes a token with 100 free credits valid for 7 days — use it as NEMO_TOKEN

Then create a session by POSTing to https://mega-api-prod.nemovideo.ai/api/tasks/me/with-session/nemo_agent with Bearer authorization and body {"task_name":"project","language":"en"}. The session_id in the response is needed for all following requests.

Tell the user you're ready. Keep the technical details out of the chat.

Free Video Generator Like Veo — 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 prompt describing a sunset over mountains, type "generate a 10-second cinematic video of a sunset over mountains", and you'll get a 1080p MP4 back in roughly 1-2 minutes. All rendering happens server-side.

Worth noting: shorter, specific prompts produce more accurate video results.

Matching Input to Actions

User prompts referencing free video generator like veo, 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-generator-like-veo
• 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.

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

Common Workflows

Quick edit: Upload → "generate a 10-second cinematic video of a sunset over mountains" → 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 10-second cinematic video of a sunset over mountains" — 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.