Maker Editor Free

Skip the learning curve of professional editing software. Describe what you want — cut the best moments, add music and transitions, and export as a short vid...

Security Scan

The skill largely matches a remote AI video-editing integration (it only needs a NEMO_TOKEN and uploads user videos) but a few instruction and metadata details are inconsistent or unnecessary and could leak environment information or hide activity from the user.

Purpose & Capability

The declared primary credential (NEMO_TOKEN) and the described API endpoints line up with a remote video-editing service. However, the SKILL.md frontmatter advertises a config path (~/.config/nemovideo/) while the skill registry metadata earlier reported no required config paths — an inconsistency. The skill also asks the agent to detect an install path and include it in request headers (X-Skill-Platform), which is not strictly necessary for video editing and widens what the skill reads about its host environment.

Instruction Scope

Instructions direct the agent to obtain or use NEMO_TOKEN, create sessions, upload user video files, poll render status, and return download URLs — all consistent with the stated purpose. Concerningly, the SKILL.md instructs the agent to derive and send headers based on the agent's install path (e.g., reading ~/.clawhub/ or ~/.cursor/skills/), which means the skill may inspect filesystem paths outside the user-uploaded files. The document also instructs the agent not to display raw API responses or token values to the user; while that can be legitimate to avoid exposing secrets, it also reduces visibility into what the backend returns and could hide unexpected behavior.

Install Mechanism

This is an instruction-only skill with no install spec or code to download, so it does not write files or execute an installer during installation. That minimizes install-time risk.

Credentials

Only NEMO_TOKEN is declared as required and is appropriate for a third-party API. The runtime instructions also create an anonymous short-lived token if none is present, which is reasonable. Still, the SKILL.md's additional metadata (config path ~./config/nemovideo/) and requirement to detect install paths increases the scope of host data the skill reads and sends in requests, which is more than strictly needed to edit videos.

Persistence & Privilege

The skill stores a session_id and may persist the anonymous token for reuse (normal for sessions). It does not request always: true and does not ask to modify other skills or global agent settings. No elevated persistent privileges are requested.

What to consider before installing

This skill appears to be a typical remote video-editing integration and only needs a NEMO_TOKEN to operate, but consider the following before installing or using it: - The skill uploads your raw video files to https://mega-api-prod.nemovideo.ai for processing. Do not upload sensitive or private footage unless you trust that service and its privacy policy. - If you don't already have a NEMO_TOKEN, the skill will obtain an anonymous short-lived token on your behalf. That token (and session_id) may be stored locally; ask where it is stored and how to revoke it. - The instructions tell the agent to detect its install path and include that information (X-Skill-Platform) in every request. This leaks host-environment details; ask the developer why this is necessary and whether it can be omitted. - The skill tells the agent not to show raw API responses or token values to users. While hiding secrets is reasonable, it also reduces transparency about backend behavior. Consider requesting visibility/logging for API responses (without exposing secrets) or only using the skill with non-sensitive content. - There is a small metadata inconsistency (config path listed in SKILL.md frontmatter but not in registry metadata). Ask the publisher to clarify what local config the skill will create or read. If you choose to proceed: provide your own NEMO_TOKEN (so you control lifecycle), avoid uploading sensitive material, and confirm how to delete any stored tokens or sessions.

Getting Started

Got raw video clips to work with? Send it over and tell me what you need — I'll take care of the AI video creation and editing.

Try saying:

• "create a 2-minute unedited phone recording into a 1080p MP4"
• "cut the best moments, add music and transitions, and export as a short video"
• "making and editing videos without paid software for content creators and students"

First-Time Connection

When a user first opens this skill, connect to the processing backend automatically. Briefly let them know (e.g. "Setting up...").

Authentication: Check if NEMO_TOKEN is set in the environment. If it is, skip to step 2.

1. Obtain a free token: Generate a random UUID as client identifier. POST to https://mega-api-prod.nemovideo.ai/api/auth/anonymous-token with header X-Client-Id set to that UUID. The response data.token is your NEMO_TOKEN — 100 free credits, valid 7 days.
2. Create a session: POST to https://mega-api-prod.nemovideo.ai/api/tasks/me/with-session/nemo_agent with Authorization: Bearer <token>, Content-Type: application/json, and body {"task_name":"project","language":"<detected>"}. Store the returned session_id for all subsequent requests.

Keep setup communication brief. Don't display raw API responses or token values to the user.

Maker Editor Free — Make and Edit Videos Free

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

A quick example: upload a 2-minute unedited phone recording, type "cut the best moments, add music and transitions, and export as a short video", and you'll get a 1080p MP4 back in roughly 1-2 minutes. All rendering happens server-side.

Worth noting: shorter clips under 60 seconds process and export the fastest.

Matching Input to Actions

User prompts referencing maker editor 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.

Headers are derived from this file's YAML frontmatter. X-Skill-Source is maker-editor-free, 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).

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

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.

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.

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

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

Tips and Tricks

The backend processes faster when you're specific. Instead of "make it look better", try "cut the best moments, add music and transitions, and export as a short video" — 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 across platforms and devices.

Common Workflows

Quick edit: Upload → "cut the best moments, add music and transitions, and export as a short video" → 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.