Video Maker Free Website

Skip the learning curve of professional editing software. Describe what you want — combine these images into a 30-second promo video with music and text over...

Security Scan

The skill's requirements and runtime instructions are broadly consistent with a cloud-based video creation service that needs a single service token and uploads user media to a remote API — but review the unknown origin, a metadata inconsistency (declared config path), and the privacy implications of uploading files before installing.

Purpose & Capability

The name/description (cloud video maker) line up with the single required credential (NEMO_TOKEN) and the HTTP endpoints described in SKILL.md. One inconsistency: the SKILL.md frontmatter includes a required configPaths entry (~/.config/nemovideo/) whereas the registry metadata provided earlier reported no required config paths. The skill's homepage/source are unknown, which reduces provenance confidence but does not contradict capability.

Instruction Scope

Runtime instructions stay within the stated purpose: authenticate (NEMO_TOKEN or anonymous token), create a session, upload media, request renders, poll state, and return download URLs. The instructions explicitly send user files and metadata to the remote API — expected for this service but important to note for privacy. There is no instruction to read unrelated local files or other environment variables.

Install Mechanism

This is an instruction-only skill with no install spec and no code files, so it does not write or execute code on disk. That is the lowest-risk install pattern and matches the skill design.

Credentials

The skill requests one credential (NEMO_TOKEN) as its primary env var, which is proportionate for a third-party API. The SKILL.md also documents generating/using an anonymous token if NEMO_TOKEN is absent — reasonable for a free-tier flow. The earlier-mentioned mismatch about configPaths in the frontmatter vs registry should be checked (why is a config path listed in metadata if registry shows none?).

Persistence & Privilege

The skill does not request always:true, has no install actions, and does not ask to modify other skills or system-wide agent settings. It requires only normal runtime token usage and network calls to the service endpoints.

Assessment

This skill appears to implement a legitimate cloud video creation flow, but before installing consider: (1) provenance — the skill has no homepage and an unknown source; verify the service domain (mega-api-prod.nemovideo.ai) and its operator. (2) Privacy — your images/audio are uploaded to a remote GPU service; avoid sensitive content unless you trust the provider and its terms. (3) Credentials — NEMO_TOKEN is the only credential requested; if you don't have one the agent will ask the service for an anonymous token (7-day, limited credits). (4) Metadata mismatch — the SKILL.md frontmatter lists a config path (~/.config/nemovideo/) even though the registry showed none; ask the publisher to clarify why a config path is declared. (5) Test with non-sensitive, small files first to confirm behavior, quotas, and any billing/upgrade prompts. If you need higher assurance, ask the publisher for an official homepage, privacy policy, and contact/support information before using real customer materials.

Getting Started

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

Try saying:

• "create five product photos and a logo file into a 1080p MP4"
• "combine these images into a 30-second promo video with music and text overlays"
• "creating short videos from photos and clips without paid software for small business owners and content creators"

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.

Video Maker Free Website — Create and Export Videos Online

Send me your images or clips and describe the result you want. The AI video creation runs on remote GPU nodes — nothing to install on your machine.

A quick example: upload five product photos and a logo file, type "combine these images into a 30-second promo video with music and text overlays", and you'll get a 1080p MP4 back in roughly 1-2 minutes. All rendering happens server-side.

Worth noting: using fewer than 10 clips keeps render times under a minute.

Matching Input to Actions

User prompts referencing video maker free website, 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	video-maker-free-website
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.

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.

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)

Common Workflows

Quick edit: Upload → "combine these images into a 30-second promo video with music and text overlays" → 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 "combine these images into a 30-second promo video with music and text overlays" — 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 social platforms.