Free Maker Editing

Skip the learning curve of professional editing software. Describe what you want — trim the pauses, add background music, and export as MP4 — and get edited...

Security Scan

The skill's stated purpose (AI video editing) generally matches the runtime instructions, but there are inconsistent and unexplained requirements (a declared required NEMO_TOKEN despite an anonymous-token flow, and a metadata reference to a local config path) that warrant caution before installing or using it.

Purpose & Capability

The skill is a cloud video-editing integration and the runtime instructions call out a remote API (nemovideo.ai) and file uploads — that aligns with the name/description. However, registry metadata declares NEMO_TOKEN as required while the SKILL.md describes an anonymous-token generation flow if no token exists; those two declarations conflict. The SKILL.md frontmatter also lists a config path (~/.config/nemovideo/) which the registry earlier said was none — another inconsistency.

Instruction Scope

Instructions explicitly direct uploading user video files to https://mega-api-prod.nemovideo.ai and saving session tokens returned by the API — expected for a cloud editor. They also require adding attribution headers and advise auto-detecting platform from the agent's install path (this implies reading runtime/install path information). SKILL.md does not instruct reading unrelated system files, but the metadata-config-path mention suggests the skill may read a local config directory (not documented in the instruction steps).

Install Mechanism

No install spec and no code files are present (instruction-only). This minimizes on-disk installation risk — nothing is downloaded or executed by the skill itself.

Credentials

The registry lists a single required env var, NEMO_TOKEN (primaryEnv). The SKILL.md, however, explicitly describes a fallback anonymous-token POST flow if NEMO_TOKEN is not set. Requiring NEMO_TOKEN in metadata is therefore disproportionate or incorrect. No other credentials are requested, which is otherwise appropriate for the stated function.

Persistence & Privilege

The skill is not always-enabled and does not request elevated platform privileges. It instructs saving a session_id from API responses but does not specify writing to system-level config or other skills. The only minor concern is the frontmatter mention of a user config path (~/.config/nemovideo/) which could imply reading local config; that behavior is not documented in the operational steps.

What to consider before installing

This skill appears to do what it claims (cloud video editing) but has some inconsistencies you should resolve before installing or using it. Specifically: - Registry metadata marks NEMO_TOKEN as required, but the instructions include a documented anonymous-token flow (so the token should be optional). Ask the publisher why NEMO_TOKEN is listed as required and whether your token will be stored or transmitted elsewhere. - The SKILL.md frontmatter mentions a local config path (~/.config/nemovideo/) and asks to auto-detect platform from an install path — clarify whether the skill will read any files on your machine or only use environment variables you explicitly provide. - The skill uploads user video files to a third-party domain (mega-api-prod.nemovideo.ai). Do not send sensitive or private videos until you verify the service owner and privacy policy. - If you must use this skill, prefer creating a limited or anonymous token rather than placing long-lived credentials in your environment. Ask the author to correct the metadata to reflect that NEMO_TOKEN is optional when anonymous token creation is supported. If the publisher cannot clarify these points, treat the skill with caution or avoid sending sensitive content.

Getting Started

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

Try saying:

• "edit my raw video clips"
• "export 1080p MP4"
• "trim the pauses, add background music,"

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.

Free Maker Editing — Edit and Export Videos Free

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

A quick example: upload a 2-minute unedited screen recording, type "trim the pauses, add background music, and export as MP4", 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 significantly faster.

Matching Input to Actions

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

Every API call needs Authorization: Bearer <NEMO_TOKEN> plus the three attribution headers above. If any header is missing, exports return 402.

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

Header	Value
X-Skill-Source	free-maker-editing
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 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

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 JSON uses short keys: t for tracks, tt for track type (0=video, 1=audio, 7=text), sg for segments, d for duration in ms, m for metadata.

Example timeline summary:

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 → "trim the pauses, add background music, and export as MP4" → 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 "trim the pauses, add background music, and export as MP4" — 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.