Video Generator Free App

Get ready-to-share videos ready to post, without touching a single slider. Upload your images or clips (MP4, MOV, JPG, PNG, up to 200MB), say something like...

Security Scan

The skill's requirements and runtime instructions are largely consistent with a cloud-based video-generation tool, but it will upload user media to an external API and there is a small metadata inconsistency you should confirm before installing.

Purpose & Capability

The skill is a cloud video generator and it requests a single service token (NEMO_TOKEN), plus an anonymous-token fallback flow — this matches the stated purpose. The attribution headers and session-based render API described are coherent with a hosted rendering backend. One inconsistency: the SKILL.md frontmatter declares a configPaths entry (~/.config/nemovideo/) while the registry metadata provided earlier listed no required config paths; clarify whether the skill needs local config access.

Instruction Scope

Instructions stay within the stated purpose: create a session, upload user media, stream SSE for progress, and request renders. The agent is explicitly told to POST user files and metadata to https://mega-api-prod.nemovideo.ai — this means user images/clips will be transmitted to a third-party service. The skill also instructs obtaining an anonymous token when NEMO_TOKEN is absent. The SKILL.md does not instruct reading unrelated system files, but the frontmatter's configPaths (see above) could imply optional local config access; confirm whether the agent will read ~/.config/nemovideo/.

Install Mechanism

No install spec and no code files (instruction-only). This is the lowest install risk: nothing will be written to disk by an installer step. Runtime will make network calls as described.

Credentials

Only one credential (NEMO_TOKEN) is declared and used, which is proportionate for a hosted API. However, the frontmatter's configPaths value suggests optional local config access that wasn't declared in the registry metadata — this discrepancy should be clarified. Also be aware that if NEMO_TOKEN is present in the environment, the skill will use it automatically to authenticate requests.

Persistence & Privilege

The skill is not always-enabled and does not request system-level privileges. Autonomous invocation (disable-model-invocation=false) is normal for skills and expected here. The instructions do not direct modifying other skills or system-wide configurations.

Assessment

This skill appears to do what it says: it will upload the media you provide to a third-party rendering service (mega-api-prod.nemovideo.ai) and use a NEMO_TOKEN (or fetch an anonymous token) to run jobs. Before installing or invoking it: (1) confirm you are comfortable having your images/audio sent to that external service and review their privacy/terms; (2) verify whether the skill actually needs to read ~/.config/nemovideo/ (frontmatter vs registry metadata mismatch) — if not, ask the publisher to remove the configPaths entry; (3) avoid putting long-lived or high-privilege secrets in NEMO_TOKEN unless you trust the service; using the anonymous-token flow minimizes credential exposure; (4) verify the backend domain and publisher (source is unknown) if you need stronger provenance. If any of these points are unclear, treat the installation cautiously or ask the publisher for clarification.

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:

• "generate five product photos and a logo file into a 1080p MP4"
• "turn these photos into a 30-second promo video with music and text overlays"
• "generating short videos from images or clips without editing software for TikTok 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 Generator Free App — Create and Export Videos Free

This tool takes your images or clips 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 photos and a logo file and want to turn these photos into a 30-second promo video with music and text overlays — the backend processes it in about 30-60 seconds and hands you a 1080p MP4.

Tip: using 5 or fewer images keeps generation time under a minute.

Matching Input to Actions

User prompts referencing video generator free app, 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-generator-free-app
X-Skill-Version	frontmatter version
X-Skill-Platform	auto-detect: clawhub / cursor / unknown from install path

Every API call needs Authorization: Bearer <NEMO_TOKEN> plus the three attribution headers above. If any header is missing, exports return 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

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.

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 field mapping: t=tracks, tt=track type (0=video, 1=audio, 7=text), sg=segments, d=duration(ms), m=metadata.

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 → "turn these photos into a 30-second promo video with music and text overlays" → Download MP4. Takes 30-60 seconds 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 "turn these photos into a 30-second promo video with music and text overlays" — 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.