Ai Video Maker Free Browser

Get finished MP4 videos ready to post, without touching a single slider. Upload your video clips or images (MP4, MOV, JPG, PNG, up to 500MB), say something l...

Security Scan

The skill's requests and runtime instructions are consistent with its stated purpose (cloud video creation) and its single declared credential; nothing in the SKILL.md demands unrelated system access or unexplained credentials.

Purpose & Capability

The name/description (cloud AI video creation) match the runtime instructions and the single required environment variable NEMO_TOKEN and config path (~/.config/nemovideo/). The API host (mega-api-prod.nemovideo.ai) and endpoints referenced align with the described functionality.

Instruction Scope

Instructions focus on creating a session, sending SSE messages, uploading user media, polling render status, and downloading results — all appropriate for a cloud video service. Notable: the skill instructs agents to upload local files via multipart (files=@/path), and to generate an anonymous token if NEMO_TOKEN is absent (POST to the provider). It also advises keeping technical/auth details out of chat (UX guidance). These are expected for this type of skill but mean the agent will read user-provided files and make outbound network requests to the service.

Install Mechanism

No install spec or third-party downloads are present (instruction-only skill), so nothing is written to disk by an installer. This is the lowest-risk install model.

Credentials

Only one credential is required (NEMO_TOKEN) and a single config path is declared. This is proportionate to a cloud-rendering video service. The SKILL.md does not request unrelated secrets or additional environment variables.

Persistence & Privilege

The skill does not request 'always' presence and does not modify other skills or system-wide configuration. It stores/uses session tokens for the service as expected; no elevated or persistent privileges are requested.

Assessment

This skill appears to do what it says: it connects to a nemovideo.ai backend, uploads files you provide, and returns rendered videos. Before installing, be aware that (1) the agent will need to read any local files you upload (it uses multipart file uploads), (2) it will make network requests to mega-api-prod.nemovideo.ai and may generate an anonymous token if you don't supply NEMO_TOKEN, and (3) technical/auth steps are intentionally kept out of chat—so verify you trust the service and review its privacy/terms if you plan to upload sensitive media. If you prefer, supply your own NEMO_TOKEN rather than relying on an anonymous token. If you want extra assurance, request the skill maintainers or publisher information (homepage/source) before use.

Getting Started

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

Try saying:

• "create five product images and a logo file into a 1080p MP4"
• "turn these images into a 30-second promotional video with music and text"
• "creating videos from images or clips without installing software 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 Maker Free Browser — Create and Export Videos Online

This tool takes your video clips 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 five product images and a logo file and want to turn these images into a 30-second promotional video with music and text — the backend processes it in about 1-2 minutes and hands you a 1080p MP4.

Tip: shorter source clips and fewer images render faster in the browser.

Matching Input to Actions

User prompts referencing ai video maker 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.

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

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

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.

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.

Translating GUI Instructions

The backend responds as if there's a visual interface. Map its instructions to API calls:

• "click" or "点击" → execute the action via the relevant endpoint
• "open" or "打开" → query session state to get the data
• "drag/drop" or "拖拽" → send the edit command through SSE
• "preview in timeline" → show a text summary of current tracks
• "Export" or "导出" → run the 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

Tips and Tricks

The backend processes faster when you're specific. Instead of "make it look better", try "turn these images into a 30-second promotional video with music and text" — 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 platforms and devices.

Common Workflows

Quick edit: Upload → "turn these images into a 30-second promotional video with music and text" → 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.