Video Maker Editor Free

edit video clips or images into edited MP4 videos with this skill. Works with MP4, MOV, AVI, WebM files up to 500MB. content creators and students use it for...

Security Scan

The skill's behavior mostly matches its stated video-editing purpose, but a few mismatches in metadata and some vague instructions about token/session storage and install-path detection merit caution before installing.

Purpose & Capability

Name/description match the runtime instructions: the SKILL.md describes uploading media, editing via SSE, and exporting MP4s using the nemovideo backend. Requesting a single NEMO_TOKEN credential is proportionate to a cloud video-rendering service. However, the SKILL.md frontmatter references a configPath (~/.config/nemovideo/) while the registry metadata earlier reported no required config paths — an inconsistency worth clarifying.

Instruction Scope

Instructions stay within video-editing scope (create anonymous token if none, create session, upload files, SSE streaming, poll export). They require the agent to call external endpoints and to generate/store a session token. Two items to note: (1) the skill asks to 'auto-detect' platform from install path, which implies reading the agent's install/runtime path (minor scope creep), and (2) it leaves unspecified where tokens/session IDs should be persisted (memory, skill storage, or disk), which is important for privacy and lifecycle.

Install Mechanism

No install spec or code is included (instruction-only), so nothing will be written to disk by an installer. This is lower risk than a skill that downloads or extracts remote binaries.

Credentials

Only NEMO_TOKEN is declared as required and is the primary credential — this aligns with a single-cloud-service integration. The skill's workflow also generates an anonymous token when none is provided. The frontmatter's mention of a config path (~/.config/nemovideo/) conflicts with the registry's 'no config paths' listing; it's unclear whether the skill will read or write that directory. The agent will send the token and uploaded media to the external nemovideo API, so users should assume media and token are transmitted off-device.

Persistence & Privilege

always:false and normal autonomous invocation are set (expected). The skill will request storing a session_id for ongoing jobs; this is a normal transient persistence need for a cloud render workflow. There is no instruction to modify other skills or system-wide settings.

What to consider before installing

This skill appears to do what it says (cloud video editing) but proceed cautiously: 1) The skill will send your videos and a bearer token to https://mega-api-prod.nemovideo.ai — do not upload sensitive or private footage unless you trust that service. 2) The SKILL.md and registry disagree about a config path (~/.config/nemovideo/); ask the publisher whether the skill will read or write that directory and where session tokens are stored (in-memory vs disk). 3) The skill auto-creates anonymous tokens (valid 7 days) if none are provided — anonymous tokens reduce friction but still grant network access to your uploads. 4) The skill’s source is unknown and there is no homepage; weigh privacy concerns and prefer services with clear provenance if you need strong guarantees. If you decide to install, test with non-sensitive sample videos first and ask the developer to clarify where tokens and session state are persisted and why the configPath metadata differs.

Getting Started

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

Try saying:

• "edit my video clips or images"
• "export 1080p MP4"
• "trim the footage, add background music,"

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.

Video Maker Editor Free — Edit and Export Videos Online

Drop your video clips or images in the chat and tell me what you need. I'll handle the AI video editing on cloud GPUs — you don't need anything installed locally.

Here's a typical use: you send a a 2-minute raw phone recording, ask for trim the footage, add background music, and export as a clean MP4, and about 1-2 minutes 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 60 seconds process significantly faster.

Matching Input to Actions

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

All calls go to https://mega-api-prod.nemovideo.ai. The main endpoints:

1. Session — POST /api/tasks/me/with-session/nemo_agent with {"task_name":"project","language":"<lang>"}. Gives you a session_id.
2. Chat (SSE) — POST /run_sse with session_id and your message in new_message.parts[0].text. Set Accept: text/event-stream. Up to 15 min.
3. Upload — POST /api/upload-video/nemo_agent/me/<sid> — multipart file or JSON with URLs.
4. Credits — GET /api/credits/balance/simple — returns available, frozen, total.
5. State — GET /api/state/nemo_agent/me/<sid>/latest — current draft and media info.
6. Export — POST /api/render/proxy/lambda with render ID and draft JSON. Poll GET /api/render/proxy/lambda/<id> every 30s for completed status and download URL.

Formats: mp4, mov, avi, webm, mkv, jpg, png, gif, webp, mp3, wav, m4a, aac.

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

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

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

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)

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.

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

Tips and Tricks

The backend processes faster when you're specific. Instead of "make it look better", try "trim the footage, add background music, and export as a clean 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 and devices.

Common Workflows

Quick edit: Upload → "trim the footage, add background music, and export as a clean 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.