Video Local

Skip the learning curve of professional editing software. Describe what you want — trim the intro, add background music, and export for YouTube — and get edi...

Security Scan

The skill advertises “local” editing but its instructions clearly upload files and use a remote API; metadata also inconsistently references a local config path and install-path detection, which could expose environment information — these mismatches warrant caution.

Purpose & Capability

The name/description emphasize "local" editing, but the SKILL.md describes uploading user video files to https://mega-api-prod.nemovideo.ai and doing all rendering server-side. That is a meaningful mismatch between user expectation (local-only) and actual behavior. Additionally, the SKILL.md metadata declares a required configPaths (~/.config/nemovideo/) and detection of install paths (~/.clawhub/, ~/.cursor/skills/), which are not reflected in the registry requirement summary — another inconsistency.

Instruction Scope

Runtime instructions tell the agent to: generate an anonymous token (POST /api/auth/anonymous-token), create sessions, upload local files via multipart POST (/api/upload-video/...), stream SSE (/run_sse), poll render status, and include many headers. They also instruct detecting local install paths to set X-Skill-Platform, which implies reading filesystem paths (~/.clawhub/, ~/.cursor/skills/) and potentially ~/.config/nemovideo/. These filesystem checks and uploads go beyond simple editing instructions and can reveal environment information and transmit user files to a third-party API — inconsistent with a strictly local editing claim.

Install Mechanism

Instruction-only skill with no install steps or downloaded code, so it does not write new binaries to disk or pull remote archives. This is the lowest install risk.

Credentials

The skill requests a single credential (NEMO_TOKEN) which is appropriate for a hosted service. However, SKILL.md metadata also references a config path (~/.config/nemovideo/) and requires detecting installation directories; that expands the scope of data the agent may read beyond just one token and is not justified by the registry metadata inconsistency.

Persistence & Privilege

The skill does not request always:true and has no install-time hooks. It instructs saving session_id and using tokens for API calls, which is normal for session-based APIs and does not indicate elevated platform privileges or modifications to other skills.

What to consider before installing

This skill claims to edit "local" videos but the runtime instructions upload your files to a remote API (mega-api-prod.nemovideo.ai) and may probe local paths (~/.clawhub/, ~/.cursor/skills/, ~/.config/nemovideo/) to set headers — so it is not offline/local-only. Before installing or using it: (1) assume your videos will be transmitted to the vendor's servers; do not send sensitive footage. (2) Ask the publisher how long uploads and derived data are retained, who operates the endpoint, and whether uploads are encrypted/isolated. (3) If you need true local-only editing, do not use this skill. (4) Consider testing with a non-sensitive short clip first and only provide a minimal-scoped token (or use the anonymous token flow) if you accept cloud processing. (5) Note the metadata inconsistency about config paths and ask the author to clarify why the skill needs to inspect local directories.

Getting Started

Ready when you are. Drop your local video files here or describe what you want to make.

Try saying:

• "edit a 3-minute MP4 recorded on your phone into a 1080p MP4"
• "trim the intro, add background music, and export for YouTube"
• "editing locally stored video files without uploading to external platforms for content creators and casual editors"

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.

Video Local — Edit and Export Local Videos

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

A quick example: upload a 3-minute MP4 recorded on your phone, type "trim the intro, add background music, and export for YouTube", and you'll get a 1080p MP4 back in roughly 1-2 minutes. All rendering happens server-side.

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

Matching Input to Actions

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

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.

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

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 intro, add background music, and export for YouTube" — concrete instructions get better results.

Max file size is 500MB. Stick to MP4, MOV, AVI, WebM for the smoothest experience.

H.264 codec gives the best balance of quality and file size.

Common Workflows

Quick edit: Upload → "trim the intro, add background music, and export for YouTube" → 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.