Free Video Generation Online

generate text or images into ready-to-share videos with this skill. Works with JPG, PNG, MP4, MOV files up to 200MB. content creators, marketers, students us...

Security Scan

The skill's requests and runtime instructions are broadly consistent with a cloud video-generation integration: it needs a single API token and calls a backend service to upload files, start jobs, and download results — nothing appears to be trying to access unrelated secrets or system-wide resources, though there are a few small inconsistencies to be aware of.

Purpose & Capability

The name/description (generate videos from text/images) matches the runtime instructions (upload files, start render sessions, poll for status, download MP4). Requesting a NEMO_TOKEN credential is appropriate for an API-backed service.

Instruction Scope

Instructions stay within the video-generation flow (auth, session creation, SSE, upload, export). Minor scope creep: the skill asks to detect install path (e.g., ~/.clawhub/, ~/.cursor/skills/) and to read the file's YAML frontmatter at runtime for attribution — these require reading some local paths/metadata but are limited in scope. No instructions request unrelated environment variables or system-wide secrets.

Install Mechanism

This is an instruction-only skill with no install spec or code to download or write to disk, which is lower risk. There is no package/install step that would pull arbitrary code.

Credentials

Only one env var (NEMO_TOKEN) is declared and used, which is proportional. The skill also implements a fallback flow to obtain an anonymous token from the service if NEMO_TOKEN is not present (POST to https://mega-api-prod.nemovideo.ai/api/auth/anonymous-token). Metadata declares a config path (~/.config/nemovideo/) that the instructions do not clearly use — a minor inconsistency but not exploitative by itself.

Persistence & Privilege

The skill is not always-enabled and does not request system-wide persistence or modify other skills. It maintains session tokens for API calls during usage, which is expected for this functionality.

Assessment

This skill will contact an external service (mega-api-prod.nemovideo.ai), upload files you provide, and include an Authorization header using NEMO_TOKEN (or obtain an anonymous token itself). Before installing, consider: (1) Do you trust nemovideo.ai with any media you upload? Avoid uploading sensitive/private files unless you're comfortable with that service's policies. (2) If you have a service token, prefer supplying a scoped/limited token and rotate it if possible. (3) The skill may read small local metadata (install path and its own SKILL.md frontmatter) for attribution — if you need to restrict filesystem access, run in an environment that prevents arbitrary path reads. Overall the skill appears coherent for video generation, but verify the service privacy/terms before sending confidential content.

Getting Started

Ready when you are. Drop your text or images here or describe what you want to make.

Try saying:

• "generate a short text prompt describing a product launch scene into a 1080p MP4"
• "generate a 30-second video from my product description and three product images"
• "generating short videos from text prompts or images without any editing software for content creators, marketers, students"

Quick Start Setup

This skill connects to a cloud processing backend. On first use, set up the connection automatically and let the user know ("Connecting...").

Token check: Look for NEMO_TOKEN in the environment. If found, skip to session creation. Otherwise:

• Generate a UUID as client identifier
• POST https://mega-api-prod.nemovideo.ai/api/auth/anonymous-token with X-Client-Id header
• Extract data.token from the response — this is your NEMO_TOKEN (100 free credits, 7-day expiry)

Session: POST https://mega-api-prod.nemovideo.ai/api/tasks/me/with-session/nemo_agent with Bearer auth and body {"task_name":"project"}. Keep the returned session_id for all operations.

Let the user know with a brief "Ready!" when setup is complete. Don't expose tokens or raw API output.

Free Video Generation Online — Generate Videos from Text or Images

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 text prompt describing a product launch scene and want to generate a 30-second video from my product description and three product images — the backend processes it in about 1-2 minutes and hands you a 1080p MP4.

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

Matching Input to Actions

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

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

• X-Skill-Source: free-video-generation-online
• 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.

SSE Event Handling

Event	Action
Text response	Apply GUI translation (§4), present to user
Tool call/result	Process internally, don't forward
heartbeat / empty data:	Keep waiting. Every 2 min: "⏳ Still working..."
Stream closes	Process final response

~30% of editing operations return no text in the SSE stream. When this happens: poll session state to verify the edit was applied, then summarize changes to the user.

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

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 → "generate a 30-second video from my product description and three product images" → 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 30-second video from my product description and three product images" — concrete instructions get better results.

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

Export as MP4 for widest compatibility across social platforms and devices.