Free Video Generator No Limits

Skip the learning curve of professional editing software. Describe what you want — generate a 30-second promo video from my product photos with background mu...

Security Scan

The skill's requests and runtime instructions are broadly consistent with a cloud video-generation service — it needs a single API token and uploads user media to an external render API — but there are a few small inconsistencies and privacy considerations you should review before installing.

Purpose & Capability

Name/description (cloud video generation from text/images) match the runtime instructions and required credential (NEMO_TOKEN). The API endpoints, upload flow, and SSE stream behavior are coherent with a cloud render pipeline.

Instruction Scope

Instructions direct the agent to create or use a NEMO_TOKEN, open sessions, upload media, stream SSE responses, and poll render status — all expected for this purpose. The skill also instructs reading this file's YAML frontmatter and detecting the install path to set attribution headers, which requires minimal filesystem reads; this is explainable but worth noting because it touches local paths.

Install Mechanism

This is an instruction-only skill with no install spec or code to write to disk, which is the lowest-risk install model.

Credentials

Only NEMO_TOKEN is required (primary credential) which is proportionate for calling the external API. The SKILL.md's YAML metadata also references a config path (~/.config/nemovideo/) even though the registry metadata lists no required config paths — this mismatch is inconsistent and should be clarified. The skill will generate an anonymous token if none is provided, which is expected behavior but implies creating credentials on the user's behalf.

Persistence & Privilege

The skill is not always-on and does not request elevated platform privileges. It does instruct saving a session_id for ongoing jobs (normal), but it does not ask to modify other skills or system-wide config.

Assessment

Before installing, consider these points: - This skill uploads whatever media you provide to a third-party domain (mega-api-prod.nemovideo.ai). Do not upload sensitive or private data unless you trust that service and its privacy policy. - The skill can create an anonymous NEMO_TOKEN automatically if you don't provide one; that is convenient but means it will perform a network call to obtain credentials. If you prefer control, set NEMO_TOKEN yourself and avoid automatic creation. - The SKILL.md mentions reading its YAML frontmatter and detecting install paths to set attribution headers; this requires reading local paths but is limited in scope — still verify you are comfortable with that filesystem access. - There is a small inconsistency: the SKILL.md metadata references a config path (~/.config/nemovideo/), but the registry metadata showed no required config paths. Ask the publisher which is authoritative if that matters to you. - If you need stronger assurance, request the skill's source or a privacy/security policy from the publisher, or run the agent in an environment with non-sensitive test data first.

Getting Started

Send me your text or images and I'll handle the AI video creation. Or just describe what you're after.

Try saying:

• "generate a short text prompt or three product images into a 1080p MP4"
• "generate a 30-second promo video from my product photos with background music"
• "generating videos from text prompts or images without paywalls for content creators"

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 Video Generator No Limits — Generate and Export Videos Free

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 or three product images and want to generate a 30-second promo video from my product photos with background music — 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 faster.

Matching Input to Actions

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

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

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

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 with background music" — concrete instructions get better results.

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

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

Common Workflows

Quick edit: Upload → "generate a 30-second promo video from my product photos with background music" → 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.