Video Editor Free Download

edit raw video clips into edited MP4 clips with this skill. Works with MP4, MOV, AVI, WebM files up to 500MB. casual creators and students use it for editing...

Security Scan

The skill's instructions are broadly consistent with a cloud video-editing service, but its provenance is unknown and there are inconsistencies and minor scope-creep (probing local paths, frontmatter vs registry metadata) that raise privacy and trust concerns.

Purpose & Capability

The skill's declared purpose (cloud video editing) matches the runtime instructions (uploading media, creating sessions, rendering on remote GPUs) and the single required credential (NEMO_TOKEN). However the SKILL.md frontmatter lists a configPaths entry (~/.config/nemovideo/) while the registry metadata said no required config paths — this mismatch is an incoherence in metadata/provenance. Also the skill has no visible homepage or known source, reducing traceability.

Instruction Scope

The instructions ask the agent to upload user media to an external API (mega-api-prod.nemovideo.ai) and to include attribution headers read from the skill's frontmatter and by detecting the agent's install path (checking ~/.clawhub/, ~/.cursor/skills/). Probing the user's home paths to detect platform and reading frontmatter for headers are beyond pure editing logic and amount to filesystem checks that may be sensitive. Uploading potentially private videos to an external service is expected for a cloud editor but is an important privacy/scope consideration that should be clear to users.

Install Mechanism

This is an instruction-only skill with no install spec and no code files, so nothing is written to disk by an installer. That lowers installation risk.

Credentials

Only one credential (NEMO_TOKEN) is declared as required and is coherent with API authentication. The SKILL.md also supports obtaining an anonymous token if NEMO_TOKEN is absent, which reduces the need to supply a secret but also means the skill will call an external auth endpoint automatically. The frontmatter's mention of a configPath is not reflected in registry metadata, which is a small inconsistency to be aware of.

Persistence & Privilege

The skill is not always-enabled (always: false) and uses normal autonomous invocation settings. It does not request persistent system-wide privileges in the metadata provided.

What to consider before installing

This skill appears to do cloud-based video editing and will upload whatever media you provide to mega-api-prod.nemovideo.ai (expected for a cloud editor). Before installing or using it: 1) consider the privacy of the videos you plan to upload — don't upload sensitive content unless you trust the service; 2) note the skill's source/homepage are missing (no provenance) and SKILL.md metadata disagrees with registry metadata about config paths; 3) the agent is instructed to probe common install paths in your home directory to set an X-Skill-Platform header — if you prefer the agent not to inspect your filesystem, avoid installing; 4) if you must use this, prefer supplying your own NEMO_TOKEN from a trusted account rather than relying on anonymous tokens; and 5) ask the publisher for a homepage, privacy policy, or audited code before trusting sensitive content. If you want, I can point out the exact lines in SKILL.md that cause these concerns.

Getting Started

Send me your raw video clips and I'll handle the AI video editing. Or just describe what you're after.

Try saying:

• "edit a 2-minute unedited screen recording into a 1080p MP4"
• "trim the pauses, add transitions, and export as a clean MP4"
• "editing and exporting videos without installing software for casual creators and students"

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.

Video Editor Free Download — Edit and Export Videos Online

Send me your raw video clips and describe the result you want. The 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 transitions, and export as a clean MP4", and you'll get a 1080p MP4 back in roughly 30-60 seconds. All rendering happens server-side.

Worth noting: shorter clips under 3 minutes process significantly faster.

Matching Input to Actions

User prompts referencing video editor free download, 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.

Base URL: https://mega-api-prod.nemovideo.ai

Endpoint	Method	Purpose
/api/tasks/me/with-session/nemo_agent	POST	Start a new editing session. Body: {"task_name":"project","language":"<lang>"}. Returns session_id.
/run_sse	POST	Send a user message. Body includes app_name, session_id, new_message. Stream response with Accept: text/event-stream. Timeout: 15 min.
/api/upload-video/nemo_agent/me/<sid>	POST	Upload a file (multipart) or URL.
/api/credits/balance/simple	GET	Check remaining credits (available, frozen, total).
/api/state/nemo_agent/me/<sid>/latest	GET	Fetch current timeline state (draft, video_infos, generated_media).
/api/render/proxy/lambda	POST	Start export. Body: {"id":"render_<ts>","sessionId":"<sid>","draft":<json>,"output":{"format":"mp4","quality":"high"}}. Poll status every 30s.

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

Skill attribution — read from this file's YAML frontmatter at runtime:

• X-Skill-Source: video-editor-free-download
• X-Skill-Version: from frontmatter version
• X-Skill-Platform: detect from install path (~/.clawhub/ → clawhub, ~/.cursor/skills/ → cursor, else unknown)

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.

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

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.

Translating GUI Instructions

The backend responds as if there's a visual interface. Map its instructions to API calls:

• "click" or "点击" → execute the action via the relevant endpoint
• "open" or "打开" → query session state to get the data
• "drag/drop" or "拖拽" → send the edit command through SSE
• "preview in timeline" → show a text summary of current tracks
• "Export" or "导出" → run the export workflow

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)

Tips and Tricks

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