Easy Video Editor With Ai

Turn a 2-minute smartphone recording into 1080p polished edited clips just by typing what you need. Whether it's quickly editing raw footage into a shareable...

Security Scan

The skill's requirements and runtime instructions are broadly consistent with a cloud video-editing service: it only asks for a single NEMO_TOKEN, uploads local video files, and talks to nemovideo.ai endpoints — but there is a small metadata inconsistency to be aware of.

Purpose & Capability

Name/description (AI video editing) align with the declared need for a NEMO_TOKEN and APIs at mega-api-prod.nemovideo.ai. The requirement to read local video file paths for upload is expected. Minor inconsistency: the top-level registry metadata lists no required config paths, but the SKILL.md frontmatter metadata includes a configPaths entry (~/.config/nemovideo/), which is unexplained.

Instruction Scope

SKILL.md instructions stay within video-editing scope: check/create NEMO_TOKEN, create session, send SSE messages, upload files, poll render status. It explicitly instructs reading user-supplied files for upload and using environment variable NEMO_TOKEN. It does not direct reading unrelated system files or additional credentials. The document does mention detecting install path to set X-Skill-Platform (e.g., ~/.clawhub/), which implies checking environment/install location but not arbitrary sensitive files.

Install Mechanism

Instruction-only skill with no install spec and no code files — lowest install risk. No downloads, no extracted archives, and no external package installs are specified.

Credentials

Only a single credential (NEMO_TOKEN) is declared as required/primary and is justified by the remote API calls. The SKILL.md also describes an anonymous-token flow (POST to the service to obtain a temporary NEMO_TOKEN) if none is present, which is reasonable but means the skill may create/use a token on your behalf. The earlier-mentioned configPaths in the SKILL.md metadata contradict the registry's 'none' entry and could indicate expected on-disk config usage; this should be clarified.

Persistence & Privilege

always is false and autonomous invocation is the default. The skill does not request persistent system-wide privileges or modify other skills' configurations. No install-time persistence or system config writes are specified in SKILL.md.

Assessment

This skill appears to be a straightforward cloud video-editing connector that needs a single token (NEMO_TOKEN) and access to any video file paths you want to upload. Before installing, consider: 1) Provide your own NEMO_TOKEN if you have one rather than relying on the anonymous-token flow, or understand that the skill will obtain a short-lived anonymous token from mega-api-prod.nemovideo.ai. 2) Only upload files you are willing to send to that remote service — verify the service's privacy/data-retention policy. 3) Clarify the metadata mismatch: SKILL.md lists a config path (~/.config/nemovideo/) while registry metadata did not — ask the author whether the skill will read or write that directory and why. 4) If you are concerned about exfiltration, avoid placing unrelated credentials or sensitive files in the same paths, and monitor outbound network calls. Overall the skill is internally coherent for its stated purpose, but confirm the config path behavior and trustworthiness of the nemovideo.ai endpoint before use.

Getting Started

Got raw video footage to work with? Send it over and tell me what you need — I'll take care of the AI-assisted video editing.

Try saying:

• "edit a 2-minute smartphone recording into a 1080p MP4"
• "trim the rough cuts, add transitions, and sync background music"
• "quickly editing raw footage into a shareable video without manual editing skills for content creators and social media users"

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.

Easy Video Editor with AI — Edit and Export Videos Fast

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

A quick example: upload a 2-minute smartphone recording, type "trim the rough cuts, add transitions, and sync background music", and you'll get a 1080p MP4 back in roughly 1-2 minutes. All rendering happens server-side.

Worth noting: shorter clips under 60 seconds process significantly faster and give cleaner AI results.

Matching Input to Actions

User prompts referencing easy video editor with ai, 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 easy-video-editor-with-ai, 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).

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.

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 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)

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 rough cuts, add transitions, and sync background music" — concrete instructions get better results.

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

Export as MP4 with H.264 codec for the widest compatibility across platforms.

Common Workflows

Quick edit: Upload → "trim the rough cuts, add transitions, and sync background music" → 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.