Video Editor Free Software

Turn a 3-minute raw screen recording into 1080p edited MP4 clips just by typing what you need. Whether it's editing raw footage into polished videos without...

Security Scan

The skill's behavior (cloud-based video editing using a NEMO_TOKEN) mostly fits its description, but it instructs the agent to hide technical details, to read local install paths/frontmatter for attribution, and it talks to an external API with no source/homepage — these mismatches warrant caution.

Purpose & Capability

The skill claims cloud AI video editing and requires a single service token (NEMO_TOKEN), which is coherent. However the package has no source/homepage and the API domain (mega-api-prod.nemovideo.ai) is unfamiliar; the SKILL.md also includes metadata (configPaths) that conflicts with the registry's 'required config paths: none'. The absence of provenance (no homepage, unknown owner slug) is a legitimacy concern but not proof of malice.

Instruction Scope

Runtime instructions include network calls to create sessions, upload videos, run renders, poll results, and generate anonymous tokens when NEMO_TOKEN is absent — these are expected for a cloud editor. Red flags: the instructions explicitly say to 'keep the technical details out of the chat' (discourages transparency), and they ask the agent to read this file's YAML frontmatter and detect install paths (e.g. ~/.clawhub/, ~/.cursor/skills/) at runtime. Asking the agent to hide action details and to probe local install paths broadens scope beyond purely editing video and is worth scrutiny.

Install Mechanism

No install spec and no code files — instruction-only skill — so nothing is written to disk by an installer. This is low-risk from an install mechanism perspective.

Credentials

The skill requests a single service credential (NEMO_TOKEN) which is appropriate for a cloud editing service. It also describes obtaining anonymous tokens via the remote auth endpoint if no token is present. Minor inconsistency: the SKILL.md frontmatter claims a config path (~/.config/nemovideo/) while the registry metadata lists 'required config paths: none'. Verify why the skill expects local config access and whether any tokens or files would be persisted locally.

Persistence & Privilege

always:false and no install-time persistence are present. The skill asks only to read frontmatter and detect common install paths (read-only checks). It does not request to modify other skills or system-wide settings. No elevated persistence privileges observed.

What to consider before installing

This skill appears to do what it says (cloud-based AI video editing) but has several things to verify before installing or using it with sensitive content: 1) Confirm the backend domain (mega-api-prod.nemovideo.ai) and the NEMO_TOKEN issuer are trustworthy — there is no homepage or source linked. 2) Ask how uploaded videos are stored, who can access them, retention period, and whether outputs are shared with third parties. 3) Note the skill tells the agent to 'keep technical details out of the chat' — request transparency about network calls and operations in logs or an explicit confirmation of actions. 4) Check why the skill might read local install paths or frontmatter and whether it will persist tokens/config locally. 5) If you proceed, test with non-sensitive sample videos first and prefer providing an account-based NEMO_TOKEN (not production or sensitive credentials). If you need higher assurance, request the skill's source or a vendor homepage and an explanation of data handling and security practices.

Getting Started

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

Try saying:

• "edit a 3-minute raw screen recording into a 1080p MP4"
• "trim the pauses, add transitions, and export as MP4"
• "editing raw footage into polished videos without paid software for students and independent creators"

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 Software — Edit and Export Polished Videos

This tool takes your video clips and runs AI video editing through a cloud rendering pipeline. You upload, describe what you want, and download the result.

Say you have a 3-minute raw screen recording and want to trim the pauses, add transitions, and export as MP4 — the backend processes it in about 1-2 minutes and hands you a 1080p MP4.

Tip: shorter clips under 2 minutes process significantly faster.

Matching Input to Actions

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

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

• X-Skill-Source: video-editor-free-software
• X-Skill-Version: from frontmatter version
• X-Skill-Platform: detect from install path (~/.clawhub/ → clawhub, ~/.cursor/skills/ → cursor, else 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 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

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.

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 transitions, 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 transitions, 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 and devices.