Video Generator Free Open Source

generate text prompts or images into ready-to-share videos with this skill. Works with MP4, PNG, JPG, WebM files up to 200MB. indie creators and developers u...

Security Scan

The skill's declared requirements and runtime instructions generally match a cloud-based video-generation integration, but there are a few non-security/coherence issues and important privacy considerations to review before use.

Purpose & Capability

Name/description claim to be 'Free Open Source' but the registry entry has no source/homepage; otherwise the required NEMO_TOKEN and optional config path (~/.config/nemovideo/) align with a cloud video-rendering API.

Instruction Scope

SKILL.md instructs the agent to obtain/use a bearer token, create sessions, stream SSE, and upload files (multipart or URL) to an external API (mega-api-prod.nemovideo.ai). This is coherent for a remote render service, but it explicitly causes user files and prompt text to be sent off-host — the user should be aware that uploads (including images, audio, or video) will be transmitted to that third-party service.

Install Mechanism

No install spec or code files are present (instruction-only), so nothing is written to disk by an installer. This is the lowest-risk install pattern.

Credentials

Only a single credential (NEMO_TOKEN) is declared and used as the bearer token for the API, which is proportionate to a cloud-rendering integration. The metadata notes a config path for nemovideo which matches the service; no unrelated secrets or broad system credentials are requested.

Persistence & Privilege

The skill is not always-enabled and does not request elevated platform privileges. It does instruct the agent to save session_id and reuse tokens for sessions, which is normal for a session-based API; autonomous invocation is allowed by default (not a concern here without other red flags).

Assessment

This skill calls a third‑party API (mega-api-prod.nemovideo.ai) and will upload user-provided files (images, audio, video) and prompt text to that service. Before installing: verify the service's privacy/TOS and whether the 'open source' claim is true (there is no source/homepage listed); avoid uploading sensitive or proprietary content; prefer using a disposable/anonymous token if you only need a short evaluation; and ensure you are comfortable with the external domain keeping or processing your uploads. If you need assurance about token storage, ask how and where the agent will persist NEMO_TOKEN and session IDs and whether you can revoke them.

Getting Started

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

Try saying:

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

Automatic Setup

On first interaction, connect to the processing API before doing anything else. Show a brief status like "Setting things up...".

Token: If NEMO_TOKEN environment variable is already set, use it and skip to Session below.

Free token: Generate a UUID as client identifier, then POST to https://mega-api-prod.nemovideo.ai/api/auth/anonymous-token with header X-Client-Id: <uuid>. The response field data.token becomes your NEMO_TOKEN (100 credits, 7-day expiry).

Session: POST to https://mega-api-prod.nemovideo.ai/api/tasks/me/with-session/nemo_agent with Bearer auth and body {"task_name":"project"}. Save session_id from the response.

Confirm to the user you're connected and ready. Don't print tokens or raw JSON.

Video Generator Free Open Source — Generate Videos from Text or Images

Send me your text prompts or images 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 or a series of product images, type "generate a 30-second video from this product description and three images", and you'll get a 1080p MP4 back in roughly 1-3 minutes. All rendering happens server-side.

Worth noting: shorter prompts with clear scene descriptions produce more accurate results.

Matching Input to Actions

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

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

Header	Value
X-Skill-Source	video-generator-free-open-source
X-Skill-Version	frontmatter version
X-Skill-Platform	auto-detect: clawhub / cursor / unknown from install path

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.

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

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.

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)

Common Workflows

Quick edit: Upload → "generate a 30-second video from this product description and three images" → Download MP4. Takes 1-3 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 this product description and three images" — concrete instructions get better results.

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

Export as MP4 for widest compatibility across platforms and devices.