Video Generator Free No Sign

Skip the learning curve of professional editing software. Describe what you want — create a 30-second promotional video from my product photos with backgroun...

Security Scan

The skill’s behavior mostly fits a cloud video-renderer, but there are multiple inconsistencies (declared required env/config vs. runtime behaviour, hidden token acquisition, and an unknown external backend) that warrant caution before installing or uploading content.

Purpose & Capability

The skill’s stated purpose (cloud video generation) matches the network endpoints and actions in SKILL.md, but registry metadata and SKILL.md disagree: the registry listed no config paths while the SKILL.md frontmatter declares a config path (~/.config/nemovideo/). Also the registry marks NEMO_TOKEN as required, yet SKILL.md documents auto-provisioning an anonymous token if none is present — these mismatches are incoherent and unclear.

Instruction Scope

Runtime instructions instruct the agent to obtain/store an auth token, create a session, upload user files (up to 200MB), stream SSEs, and poll render status against https://mega-api-prod.nemovideo.ai. Uploading user media to an external service is expected for a video generator, but the SKILL.md explicitly tells the agent to auto-fetch a token and to “Don't display raw API responses or token values to the user,” which could hide sensitive debug/credential info. The doc also describes detecting install paths to set headers, implying the agent may read filesystem paths for context. Overall the scope is broad but largely consistent with video creation — the main issues are the secrecy around token handling and the filesystem/config path references.

Install Mechanism

This is an instruction-only skill with no install spec and no code files, so nothing is written to disk by an installer; that reduces installation risk. Network calls described in SKILL.md are the primary runtime surface.

Credentials

Only NEMO_TOKEN is declared as the required credential, which is proportionate for an external video API. However, the SKILL.md both checks for NEMO_TOKEN and describes how to auto-acquire an anonymous token via the service’s /anonymous-token endpoint, making the declared 'required' env var ambiguous. The metadata also lists a config path not reflected in the registry's 'required config paths', another inconsistency.

Persistence & Privilege

The skill does not request 'always: true' and does not declare changes to other skills or system-wide settings. It does ask to store a session_id for continued requests (normal for session-based APIs) but does not request elevated platform privileges.

What to consider before installing

This skill appears to be a front-end for a cloud video-renderer and will upload your images/audio to https://mega-api-prod.nemovideo.ai. Before installing or using it: (1) be aware your media and metadata leave your device; do not upload sensitive or confidential content. (2) The skill claims NEMO_TOKEN is required yet also auto-creates anonymous tokens — clarify whether the platform will force you to provide secrets or allow anonymous issuance. (3) There is no homepage or source listed and the metadata has inconsistencies (config path present only in SKILL.md). If you need stronger assurance, ask the publisher for a privacy policy, source repo, or an explanation of token storage/rotation and where session tokens are persisted. If you proceed, prefer using non-sensitive test files and monitor network requests or tokens the skill creates.

Getting Started

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

Try saying:

• "generate a short product description or three brand images into a 1080p MP4"
• "create a 30-second promotional video from my product photos with background music"
• "generating videos from text or images without creating an account for casual creators and marketers"

First-Time Connection

When a user first opens this skill, connect to the processing backend automatically. Briefly let them know (e.g. "Setting up...").

Authentication: Check if NEMO_TOKEN is set in the environment. If it is, skip to step 2.

1. Obtain a free token: Generate a random UUID as client identifier. POST to https://mega-api-prod.nemovideo.ai/api/auth/anonymous-token with header X-Client-Id set to that UUID. The response data.token is your NEMO_TOKEN — 100 free credits, valid 7 days.
2. Create a session: POST to https://mega-api-prod.nemovideo.ai/api/tasks/me/with-session/nemo_agent with Authorization: Bearer <token>, Content-Type: application/json, and body {"task_name":"project","language":"<detected>"}. Store the returned session_id for all subsequent requests.

Keep setup communication brief. Don't display raw API responses or token values to the user.

Video Generator Free No Sign Up — Create 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 product description or three brand images and want to create a 30-second promotional 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 scripts and fewer images produce faster results with cleaner output.

Matching Input to Actions

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

Headers are derived from this file's YAML frontmatter. X-Skill-Source is video-generator-free-no-sign, X-Skill-Version comes from the version field, and X-Skill-Platform is detected from the install path (~/.clawhub/ = clawhub, ~/.cursor/skills/ = cursor, otherwise unknown).

Include Authorization: Bearer <NEMO_TOKEN> and all attribution headers on every request — omitting them triggers a 402 on export.

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

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)

Tips and Tricks

The backend processes faster when you're specific. Instead of "make it look better", try "create a 30-second promotional video from my product photos with background music" — concrete instructions get better results.

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

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

Common Workflows

Quick edit: Upload → "create a 30-second promotional 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.