Maker Online Free

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

Security Scan

The skill's requests and runtime instructions mostly match a cloud video-exporter: it asks for a single service token and describes only network calls and user-file uploads—however there is a small metadata inconsistency about a config path that you should verify before installing.

Purpose & Capability

Name/description (cloud video creation and export) align with the runtime instructions and the single required credential NEMO_TOKEN. The API endpoints (nemovideo domain) and upload/export flows are coherent with the stated purpose. Note: the SKILL.md frontmatter declares a config path (~/.config/nemovideo/) even though the registry metadata listed no required config paths—this discrepancy should be clarified.

Instruction Scope

SKILL.md instructs the agent to obtain/refresh NEMO_TOKEN (optionally via anonymous-token flow), create sessions, upload user-provided media, stream SSE for interactive edits, and poll export status. All of these actions are within the expected scope for a cloud video-rendering skill. The instructions do not ask the agent to read unrelated system files or other credentials. It does, however, direct uploads of user files to an external service (the intended behavior) and requires the agent to include attribution headers on every request.

Install Mechanism

No install spec or code is present (instruction-only), so nothing is written to disk or downloaded by the skill itself. This is the lowest-risk install mechanism and matches the provided SKILL.md.

Credentials

Only NEMO_TOKEN is declared as required (primary credential), which is proportionate to calling the remote API. The SKILL.md frontmatter also lists a config path (~/.config/nemovideo/) that implies the agent might read local configuration to find stored tokens—this was not reflected in the top-level registry metadata and should be confirmed. No other unrelated secrets or credentials are requested.

Persistence & Privilege

always is false and the skill does not request system-wide changes. The agent may invoke the skill autonomously (normal default). The skill's instructions say to save a session_id, but do not instruct modifying other skills' configs or system settings.

Assessment

This skill appears to be what it says: a cloud-based video creator that needs one token (NEMO_TOKEN) to talk to the Nemovideo API and to upload your media. Before installing: confirm you are comfortable uploading your files to https://mega-api-prod.nemovideo.ai and review that service's privacy policy; verify the domain and that HTTPS is used; confirm whether the skill will read or store anything under ~/.config/nemovideo/ (SKILL.md frontmatter mentions this path but registry metadata did not); avoid using the skill with sensitive personal data unless you trust the remote service; and keep your real NEMO_TOKEN secret (the skill can also generate an ephemeral anonymous token if you prefer). If you want greater assurance, ask the skill author to remove or explicitly document any local config access and to explain how/where session tokens are persisted.

Getting Started

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

Try saying:

• "create my images or clips"
• "export 1080p MP4"
• "combine these images into a 30-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.

Maker Online Free — Create and Export Videos Online

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 combine these images into a 30-second promo video with music and text — the backend processes it in about 30-60 seconds and hands you a 1080p MP4.

Tip: using 5-10 images keeps processing fast and the final video tight.

Matching Input to Actions

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

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

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

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

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.

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

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

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.

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)

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" — 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 and devices.

Common Workflows

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