Video Maker Online

Turn five product photos and a logo file into 1080p polished MP4 videos just by typing what you need. Whether it's assembling clips and images into a finishe...

Security Scan

The skill's declared purpose (cloud video creation) and required credential (NEMO_TOKEN) are consistent, but the runtime instructions reference filesystem paths and config metadata that don't match the registry metadata and could cause the agent to read system install locations; review before installing.

Purpose & Capability

Name/description match the actions described in SKILL.md (upload media, request cloud render, download MP4). The single required env var, NEMO_TOKEN, is appropriate for a cloud API that uses Bearer auth.

Instruction Scope

The SKILL.md instructs the agent to: (a) use or obtain a NEMO_TOKEN and create sessions and render jobs (expected), (b) include skill attribution headers and specifically to 'detect from install path' by checking common install directories (~/.clawhub/, ~/.cursor/skills/) to set X-Skill-Platform. That requires reading filesystem install paths outside the skill's own files. The frontmatter metadata also lists a config path (~/.config/nemovideo/) despite the registry metadata showing no required config paths—this mismatch is inconsistent and worth questioning.

Install Mechanism

No install spec or code files — instruction-only skill. Lowest install risk (nothing is downloaded or written by the skill itself).

Credentials

Only NEMO_TOKEN is declared and used, which is proportional for calling the nemovideo API. The skill does offer an anonymous-token flow (POST with a generated UUID) so users can avoid supplying a personal token. Verify whether you want to provide a long-lived/token with broad access or prefer the ephemeral anonymous token.

Persistence & Privilege

The skill is not always-enabled and has normal autonomy settings. It does not request system-level persistence or claim to modify other skills' configs.

What to consider before installing

This skill appears to do what it says (upload media → cloud render → download), and it needs a NEMO_TOKEN to authenticate — that's expected. Two things to check before installing: (1) SKILL.md asks the agent to examine install directories (~/.clawhub/, ~/.cursor/skills/) and references a config path (~/.config/nemovideo/) even though the registry metadata did not declare config paths. If you don't want the agent inspecting your filesystem, ask the developer to remove or clarify that behavior. (2) All media you upload will be sent to https://mega-api-prod.nemovideo.ai; if your images contain sensitive data, prefer the anonymous-token flow or avoid providing a long-lived NEMO_TOKEN. If you proceed, consider using a scoped/ephemeral token and confirm the service's privacy/retention policy for uploaded media.

Getting Started

Share your video clips or images and I'll get started on AI video creation. Or just tell me what you're thinking.

Try saying:

• "create my video clips or images"
• "export 1080p MP4"
• "combine these clips into a 60-second"

Automatic Setup

On first interaction, connect to the processing API before doing anything else. Show a brief status like "Setting things up...".

Token: If NEMO_TOKEN environment variable is already set, use it and skip to Session below.

Free token: Generate a UUID as client identifier, then POST to https://mega-api-prod.nemovideo.ai/api/auth/anonymous-token with header X-Client-Id: <uuid>. The response field data.token becomes your NEMO_TOKEN (100 credits, 7-day expiry).

Session: POST to https://mega-api-prod.nemovideo.ai/api/tasks/me/with-session/nemo_agent with Bearer auth and body {"task_name":"project"}. Save session_id from the response.

Confirm to the user you're connected and ready. Don't print tokens or raw JSON.

Video Maker Online — Create and Export Finished Videos

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 photos and a logo file and want to combine these clips into a 60-second video with background music and text overlays — the backend processes it in about 1-2 minutes and hands you a 1080p MP4.

Tip: shorter source clips under 2 minutes process significantly faster.

Matching Input to Actions

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

Skill attribution — read from this file's YAML frontmatter at runtime:

• X-Skill-Source: video-maker-online
• X-Skill-Version: from frontmatter version
• X-Skill-Platform: detect from install path (~/.clawhub/ → clawhub, ~/.cursor/skills/ → cursor, else unknown)

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 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)

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

Common Workflows

Quick edit: Upload → "combine these clips into a 60-second video with background 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 clips into a 60-second video with background 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 platforms and devices.