Free Generator Online

Turn a short product description or three brand images into 1080p ready-to-share videos just by typing what you need. Whether it's generating videos from tex...

Security Scan

The skill's high-level purpose (remote video generation) matches its network calls, but the SKILL.md asks the agent to access local files/paths and the embedded metadata disagrees with the registry; those inconsistencies and unclear persistence behaviors are concerning.

Purpose & Capability

The skill claims to call a remote video-generation API and requires a NEMO_TOKEN — that is consistent with its stated purpose. However the SKILL.md frontmatter declares a required config path (~/.config/nemovideo/) that is not present in the registry metadata, which is unexpected for a simple API client.

Instruction Scope

Runtime instructions direct the agent to: detect the agent install path to set X-Skill-Platform, read this file's YAML frontmatter at runtime (for attribution), generate and store a UUID client id, request or persist a session_id and token, and upload local files via multipart. Reading local config/install paths and saving session state are outside the minimal scope of 'call remote API' and are not fully specified (where/how to save session/token).

Install Mechanism

Instruction-only skill with no install spec or code to download — lowest-risk install mechanism.

Credentials

Registry lists a single required env var NEMO_TOKEN (reasonable). But SKILL.md frontmatter includes an extra required config path (~/.config/nemovideo/) and the instructions reference detecting install paths and reading YAML frontmatter — these require filesystem access that wasn't declared. The skill also instructs obtaining an anonymous token via the API if NEMO_TOKEN is not present; that behavior is plausible but the persistence and scope of stored credentials/tokens is unclear.

Persistence & Privilege

always:false (normal). The skill instructs saving a session_id and possibly the generated anonymous token, which implies local persistence; the registry doesn't explain where or with what lifetime. Autonomous invocation is allowed (platform default) — combine that with stored session tokens and filesystem access increases blast radius if misused.

What to consider before installing

What to consider before installing: - The skill legitimately talks to a remote video API and needs a NEMO_TOKEN; that's expected. But the SKILL.md also wants to read local paths (install path, YAML frontmatter) and save session state, while the registry metadata does not declare those filesystem requirements — ask the author to clarify exactly which files/paths will be read and where session/token data is stored. - If you provide a permanent NEMO_TOKEN, the agent could use it for all calls to that API. If you prefer, allow the skill to use an anonymous token (the skill can create one) rather than a long-lived credential. Confirm the token storage location and lifetime first. - Confirm the domain (https://mega-api-prod.nemovideo.ai) is the official service you expect. If unsure, request source code or clearer metadata (explicit configPaths, where session data is persisted, exact headers used). - If you want lower risk: refuse granting filesystem access or persistent tokens, or run this skill in an environment-level sandboxed session where it cannot read your home directory. Overall: the functionality matches the description, but metadata/instruction inconsistencies and unclear persistence warrant caution and clarification before use.

Getting Started

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

Try saying:

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

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.

Free Generator Online — Generate Videos From Text or Images

Send me your text 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 product description or three brand images, type "generate a 30-second promo video from my product photos and description", and you'll get a 1080p MP4 back in roughly 30-60 seconds. All rendering happens server-side.

Worth noting: shorter text prompts with clear details produce faster and more accurate video results.

Matching Input to Actions

User prompts referencing free generator online, 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.

Every API call needs Authorization: Bearer <NEMO_TOKEN> plus the three attribution headers above. If any header is missing, exports return 402.

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

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

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

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.

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)

Common Workflows

Quick edit: Upload → "generate a 30-second promo video from my product photos and description" → Download MP4. Takes 30-60 seconds 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 promo video from my product photos and description" — 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 across social platforms and devices.