Video Generator Free No Limits

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 runtime instructions mostly match a cloud video-generation purpose, but there are small inconsistencies around declared config paths and filesystem access that the user should understand before installing.

Purpose & Capability

Name/description (generate videos from text/images) aligns with the actions the SKILL.md describes (upload files, SSE, render/export endpoints). However the frontmatter in SKILL.md declares a config path (~/.config/nemovideo/) and asks the agent to read YAML frontmatter/installation paths for attribution headers; the registry metadata reported no required config paths. This mismatch is unexplained.

Instruction Scope

All runtime instructions are focused on the nemovideo.ai API (auth, session creation, upload, SSE, render). That is consistent with the stated purpose. The instructions also direct the agent to detect an install path (~/.clawhub, ~/.cursor/skills/) and read this file's YAML frontmatter at runtime to populate attribution headers — this requires local filesystem inspection of agent paths, which is not strictly necessary to perform a video render and is worth noting.

Install Mechanism

Instruction-only skill with no install spec and no code files. Lowest install risk — nothing is written to disk by an installer.

Credentials

The only declared credential is NEMO_TOKEN, which is appropriate for a cloud video API. But the SKILL.md frontmatter references a config path (~/.config/nemovideo/) that the registry did not list; the skill will also generate anonymous tokens if NEMO_TOKEN is missing. Verify you are not supplying a shared or high-privilege token, since the skill will send Bearer auth to the specified domain.

Persistence & Privilege

Skill is not always-enabled and has no install-time persistence. It asks the agent to store a session_id (ephemeral) and to re-auth as needed. It does not request elevated host privileges or modifications to other skills.

What to consider before installing

This skill appears to do what it says (cloud video creation) and only needs a NEMO_TOKEN to call nemovideo.ai, but there are a few things to check before using it: 1) Confirm you trust the domain https://mega-api-prod.nemovideo.ai — the skill will send Bearer tokens there. 2) The SKILL.md references a local config path (~/.config/nemovideo/) and asks the agent to detect install paths to populate attribution headers; the registry metadata did not list that path — ask the publisher why filesystem reads are needed. 3) Prefer using the anonymous/ephemeral token path if you don't want to expose a persistent or shared token; do not reuse high-privilege tokens as NEMO_TOKEN. 4) Because this is instruction-only, there is no installer risk, but the agent will perform network calls and local path checks at runtime — consider running in a sandbox or reviewing network logs if you have sensitive local data. If you want to proceed, ask the publisher to clarify the config-path usage and whether the skill ever persists tokens to disk.

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"
• "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.

Video Generator Free No Limits — Generate Videos From Any Input

Drop your text or images in the chat and tell me what you need. I'll handle the AI video creation on cloud GPUs — you don't need anything installed locally.

Here's a typical use: you send a a short product description or three brand images, ask for generate a 30-second promo video from my product photos and description, and about 30-90 seconds later you've got a MP4 file ready to download. The whole thing runs at 1080p by default.

One thing worth knowing — shorter prompts with clear scene descriptions produce more accurate results.

Matching Input to Actions

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

Base URL: https://mega-api-prod.nemovideo.ai

Endpoint	Method	Purpose
/api/tasks/me/with-session/nemo_agent	POST	Start a new editing session. Body: {"task_name":"project","language":"<lang>"}. Returns session_id.
/run_sse	POST	Send a user message. Body includes app_name, session_id, new_message. Stream response with Accept: text/event-stream. Timeout: 15 min.
/api/upload-video/nemo_agent/me/<sid>	POST	Upload a file (multipart) or URL.
/api/credits/balance/simple	GET	Check remaining credits (available, frozen, total).
/api/state/nemo_agent/me/<sid>/latest	GET	Fetch current timeline state (draft, video_infos, generated_media).
/api/render/proxy/lambda	POST	Start export. Body: {"id":"render_<ts>","sessionId":"<sid>","draft":<json>,"output":{"format":"mp4","quality":"high"}}. Poll status every 30s.

Accepted file types: 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: video-generator-free-no-limits
• X-Skill-Version: from frontmatter version
• X-Skill-Platform: detect from install path (~/.clawhub/ → clawhub, ~/.cursor/skills/ → cursor, else unknown)

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.

Error Handling

Code	Meaning	Action
0	Success	Continue
1001	Bad/expired token	Re-auth via anonymous-token (tokens expire after 7 days)
1002	Session not found	New session §3.0
2001	No credits	Anonymous: show registration URL with ?bind=<id> (get <id> from create-session or state response when needed). Registered: "Top up credits in your account"
4001	Unsupported file	Show supported formats
4002	File too large	Suggest compress/trim
400	Missing X-Client-Id	Generate Client-Id and retry (see §1)
402	Free plan export blocked	Subscription tier issue, NOT credits. "Register or upgrade your plan to unlock export."
429	Rate limit (1 token/client/7 days)	Retry in 30s once

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.

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)

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.

Common Workflows

Quick edit: Upload → "generate a 30-second promo video from my product photos and description" → Download MP4. Takes 30-90 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.