Maker Free Best

Get polished MP4 videos ready to post, without touching a single slider. Upload your raw footage (MP4, MOV, AVI, WebM, up to 500MB), say something like "make...

Security Scan

The skill mostly matches a video-upload/rendering purpose, but there are inconsistencies and a few instructions that could allow unexpected local-file access or configuration reads — review before installing or authorizing tokens.

Purpose & Capability

Name/description align with cloud video rendering and the only declared credential is NEMO_TOKEN, which is appropriate. However the SKILL.md frontmatter requests a config path (~/.config/nemovideo/) that the registry metadata did not list; this mismatch is unexplained and deserves clarification (why would a simple render skill need that local config folder?).

Instruction Scope

The runtime instructions are fairly specific and limited to creating sessions, uploading files, sending SSE messages, polling export status, and returning download URLs — all coherent for a cloud render service. However, the doc explicitly shows multipart uploads using local filesystem paths (e.g., -F "files=@/path") and tells the agent to detect install paths to set X-Skill-Platform. Those items imply the agent may read arbitrary local file paths or probe install locations, which is broader than just handling user-supplied attachments and could enable exfiltration if misused.

Install Mechanism

Instruction-only skill with no install spec and no code files; nothing is written to disk or downloaded by the skill itself, which is the lowest-risk install model.

Credentials

The skill declares a single primary credential (NEMO_TOKEN), which fits a third-party API. But SKILL.md metadata requesting a config path (~/.config/nemovideo/) is inconsistent with the registry's reported required config paths (none). That configPath could expose local stored secrets or configs; its presence should be justified or removed.

Persistence & Privilege

always:false and default autonomous invocation are set (normal). The skill does not request elevated or persistent platform privileges. No indication it will modify other skills or system settings.

What to consider before installing

This skill appears to do what it says (cloud video rendering) and only asks for a single API token, but there are a couple of things to check before installing: (1) Confirm why the skill claims access to ~/.config/nemovideo/ (the registry metadata doesn't list it) — that folder could contain other tokens or private data. (2) Prefer uploading video files through the chat attachment mechanism instead of providing local filesystem paths; the instructions show multipart uploads that reference local paths, which could allow the agent to read arbitrary files if given a path. (3) Verify you trust the endpoint domain (mega-api-prod.nemovideo.ai) before providing NEMO_TOKEN. If you need higher assurance, ask the skill author to remove the configPath requirement and to restrict upload instructions to user-provided attachments/URLs only.

Getting Started

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

Try saying:

• "create my raw footage"
• "export 1080p MP4"
• "make a free video from my"

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.

Maker Free Best — Create and Export Free Videos

Drop your raw footage in the chat and tell me what you need. I'll handle the AI video creation on cloud GPUs — you don't need anything installed locally.

Here's a typical use: you send a a 60-second phone recording or image set, ask for make a free video from my clips with music and transitions, and about 30-60 seconds later you've got a MP4 file ready to download. The whole thing runs at 1080p by default.

One thing worth knowing — shorter clips under 2 minutes process significantly faster.

Matching Input to Actions

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

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.

Headers are derived from this file's YAML frontmatter. X-Skill-Source is maker-free-best, X-Skill-Version comes from the version field, and X-Skill-Platform is detected from the install path (~/.clawhub/ = clawhub, ~/.cursor/skills/ = cursor, otherwise unknown).

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)

Common Workflows

Quick edit: Upload → "make a free video from my clips with music and transitions" → 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 "make a free video from my clips with music and transitions" — concrete instructions get better results.

Max file size is 500MB. Stick to MP4, MOV, AVI, WebM for the smoothest experience.

Export as MP4 for widest compatibility.