Ai Video Generator Free Browser

Skip the learning curve of professional editing software. Describe what you want — create a 30-second promo video from my product description — and get ready...

Security Scan

The skill's requested token, endpoints, and runtime instructions are consistent with a browser-based AI video service; nothing in the instructions requests unrelated credentials or installs arbitrary code, though there are a couple of small metadata inconsistencies and privacy considerations to review before use.

Purpose & Capability

The skill claims to connect to a Nemovideo backend and only requests a NEMO_TOKEN credential, which matches the stated purpose. Minor inconsistency: the SKILL.md frontmatter lists a config path (~/.config/nemovideo/) while the provided registry metadata earlier says no required config paths — this mismatch should be clarified but does not by itself indicate malicious behavior.

Instruction Scope

The SKILL.md instructs the agent to make HTTP calls to mega-api-prod.nemovideo.ai, upload user media, open sessions, stream SSE, and include attribution headers. Those actions are expected for a cloud video-rendering service. User data (media, scripts) will be transmitted to the external service — this is normal for the stated purpose but is a privacy surface the user should be aware of.

Install Mechanism

Instruction-only skill with no install spec or downloaded code; lowest-risk install mechanism. The skill will not write files or install packages on the host as part of an installer.

Credentials

The skill requires a single credential (NEMO_TOKEN), which is proportional to a cloud API usage. It also documents a fallback anonymous-token flow that generates a short-lived token via the service API. Treat NEMO_TOKEN as a sensitive bearer credential since it is used for authorization on all requests.

Persistence & Privilege

The skill is not always-enabled and does not request persistent system-wide privileges or modify other skills. Autonomous model invocation is allowed by default (normal for skills) but not combined with other concerning privileges.

Assessment

This skill appears to do what it says: it uploads your text/images to a nemovideo backend and returns generated videos. Before installing, consider: (1) the NEMO_TOKEN is a bearer credential—only provide a token you trust and avoid using sensitive account tokens if you don't want uploads tied to your account; (2) media you upload (images, video, audio, text) will be sent to an external service—review any privacy/ownership implications; (3) clarify the small metadata mismatch about the config path (~/.config/nemovideo/) if you are concerned about file access; and (4) verify the external domain (mega-api-prod.nemovideo.ai) and its privacy/terms if you need stronger assurance. If you prefer not to provide a permanent token, the anonymous-token flow described will create short-lived demo tokens, but those also permit uploads to the external service.

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 script or three product images into a 1080p MP4"
• "create a 30-second promo video from my product description"
• "generating videos from text or images without software installs for content creators and marketers"

Getting Connected

Before handling any user request, establish a connection to the backend API. Show a brief status like "Connecting...".

If NEMO_TOKEN is in the environment, use it directly and create a session. Otherwise, acquire a free starter token:

• Generate a UUID as client identifier
• POST to https://mega-api-prod.nemovideo.ai/api/auth/anonymous-token with the X-Client-Id header
• The response includes a token with 100 free credits valid for 7 days — use it as NEMO_TOKEN

Then create a session by POSTing to https://mega-api-prod.nemovideo.ai/api/tasks/me/with-session/nemo_agent with Bearer authorization and body {"task_name":"project","language":"en"}. The session_id in the response is needed for all following requests.

Tell the user you're ready. Keep the technical details out of the chat.

AI Video Generator Free Browser — Generate Videos Free in Browser

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 script or three product images and want to create a 30-second promo video from my product description — the backend processes it in about 1-2 minutes and hands you a 1080p MP4.

Tip: shorter scripts under 60 words generate faster and more accurately.

Matching Input to Actions

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

Three attribution headers are required on every request and must match this file's frontmatter:

Header	Value
X-Skill-Source	ai-video-generator-free-browser
X-Skill-Version	frontmatter version
X-Skill-Platform	auto-detect: clawhub / cursor / unknown from install path

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

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

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)

Common Workflows

Quick edit: Upload → "create a 30-second promo video from my product description" → 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 "create a 30-second promo video from my product 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.