Video Editing Free

Turn a 2-minute unedited phone recording into 1080p edited MP4 clips just by typing what you need. Whether it's editing raw footage into a finished video wit...

Security Scan

The skill's requests and runtime instructions are broadly consistent with a cloud-based video-editing service, but there are a few small metadata inconsistencies and privacy decisions you should understand before installing.

Purpose & Capability

The name/description claim a cloud-based video editing service and the instructions only require a single service token (NEMO_TOKEN) and network calls to a nemo-video API, which is coherent with the stated purpose.

Instruction Scope

Runtime instructions instruct the agent to upload user video files and to POST/GET to the listed nemo API endpoints (session creation, SSE, upload, render, credits, state). This is expected for a cloud rendering service, but note the skill will (a) transmit user media to an external domain (mega-api-prod.nemovideo.ai) and (b) may automatically acquire an anonymous token if NEMO_TOKEN is not present.

Install Mechanism

No install spec or code files are included (instruction-only skill), so nothing is written to disk by an installer—lowest install risk.

Credentials

The skill declares a single primary credential (NEMO_TOKEN), which matches its API usage. Small inconsistency: registry metadata showed no required config paths, but the SKILL.md frontmatter references configPaths (~/.config/nemovideo/). Also the skill will attempt to obtain an anonymous token by POSTing to an auth endpoint if NEMO_TOKEN is missing, which is a capability you should be aware of (it means the skill can create a short-lived token and use it without you providing one).

Persistence & Privilege

The skill does not request 'always: true' and gives no instructions to modify other skills or system-wide settings. It maintains per-session state with the remote service, which is normal for this functionality.

Assessment

This skill uploads your raw video files to an external service (mega-api-prod.nemovideo.ai) and requires a NEMO_TOKEN to authorize requests — if you don't provide one it will request an anonymous token for you. Before installing: (1) confirm you trust the nemo-video service and its privacy policy because your media will be transmitted off-device; (2) consider providing your own NEMO_TOKEN rather than relying on anonymous tokens; (3) note the SKILL.md references a config path (~/.config/nemovideo/) that wasn't listed in registry metadata — ask the publisher to clarify whether the skill will read local config files; (4) if you need stronger guarantees, test with non-sensitive sample footage first and verify the returned URLs and tokens are scoped/temporary.

Getting Started

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

Try saying:

• "edit my raw video clips"
• "export 1080p MP4"
• "trim the silent parts, add transitions,"

Quick Start Setup

This skill connects to a cloud processing backend. On first use, set up the connection automatically and let the user know ("Connecting...").

Token check: Look for NEMO_TOKEN in the environment. If found, skip to session creation. Otherwise:

• Generate a UUID as client identifier
• POST https://mega-api-prod.nemovideo.ai/api/auth/anonymous-token with X-Client-Id header
• Extract data.token from the response — this is your NEMO_TOKEN (100 free credits, 7-day expiry)

Session: POST https://mega-api-prod.nemovideo.ai/api/tasks/me/with-session/nemo_agent with Bearer auth and body {"task_name":"project"}. Keep the returned session_id for all operations.

Let the user know with a brief "Ready!" when setup is complete. Don't expose tokens or raw API output.

Video Editing Free — Edit and Export Finished Videos

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

A quick example: upload a 2-minute unedited phone recording, type "trim the silent parts, add transitions, and export a clean final cut", and you'll get a 1080p MP4 back in roughly 1-2 minutes. All rendering happens server-side.

Worth noting: shorter clips under 3 minutes process significantly faster and use fewer credits.

Matching Input to Actions

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

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.

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 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 "trim the silent parts, add transitions, and export a clean final cut" — 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 silent parts, add transitions, and export a clean final cut" → 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.