Video Editor Better Than Capcut

Skip the learning curve of professional editing software. Describe what you want — trim the footage, add transitions, and overlay background music — and get...

Security Scan

The skill's behaviour largely matches a cloud video-editing tool, but there are inconsistencies (a claimed config path in the skill frontmatter vs registry metadata) and it will upload user files and obtain/handle tokens for an external API — the pieces mostly fit but a few unexpected items merit caution.

Purpose & Capability

The skill describes a cloud-based AI video editor and requires a NEMO_TOKEN which matches that purpose. However, the SKILL.md frontmatter declares a required config path (~/.config/nemovideo/) that is not listed in the registry-level 'Required config paths' metadata. The frontmatter also instructs detection of agent install paths (~/.clawhub, ~/.cursor), which implies reading filesystem locations beyond just handling uploaded clips — this mismatch should be clarified.

Instruction Scope

Runtime instructions are focused on creating a session, uploading clips, streaming SSE messages, checking credits/state, and exporting — all consistent with a cloud video editor. The instructions do ask the agent to read this file's YAML frontmatter and to detect install paths in the home directory: those file/FS reads are outside the core editing flow and could access user environment details that aren't strictly necessary for editing.

Install Mechanism

No install spec and no code files — this is instruction-only, so nothing is written to disk by an installer. That lowers install risk; the skill relies on making outbound API calls at runtime.

Credentials

Only a single credential (NEMO_TOKEN) is declared as required, which is proportionate for a cloud API. The skill also describes generating an anonymous token from the service if NEMO_TOKEN is absent (reasonable). The earlier-noted frontmatter configPaths entry suggests the skill may expect or attempt access to ~/.config/nemovideo/, which was not declared in the registry metadata — this inconsistency increases risk because it implies access to a local config area that wasn't advertised.

Persistence & Privilege

The skill is not always-enabled and uses normal autonomous invocation. It will, if used, send user video files and session tokens to an external domain (mega-api-prod.nemovideo.ai). Autonomous invocation plus outbound uploads means the skill could transmit data without further prompting if granted permission — combine that with the configPath ambiguity and you should be cautious about unattended/autonomous use on sensitive files.

What to consider before installing

This skill generally behaves like a cloud video-editor: it uploads your clips to an external API, creates/uses a NEMO_TOKEN, and returns edited outputs. Before installing or using it: (1) Verify the external domain (mega-api-prod.nemovideo.ai) and the publisher — there is no homepage or publisher info in the registry. (2) Prefer supplying your own NEMO_TOKEN only if you trust the service; anonymous tokens can be created automatically as the instructions describe. (3) Clarify why the skill's frontmatter references ~/.config/nemovideo/ and why the registry metadata doesn't list that config path — avoid installing if you don't want a skill that may access your home/config directories. (4) Do not allow autonomous/background runs on sensitive video files; the skill will upload files to an external cloud service. (5) If you need more assurance, ask the publisher for a privacy/storage policy and confirm whether uploaded media are persisted or used for model training.

Getting Started

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

Try saying:

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

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 Editor Better Than CapCut — Edit and Export Polished Videos

This tool takes your raw 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 60-second smartphone video clip and want to trim the footage, add transitions, and overlay background music — the backend processes it in about 1-2 minutes and hands you a 1080p MP4.

Tip: shorter clips under 60 seconds process faster and give cleaner AI edit suggestions.

Matching Input to Actions

User prompts referencing video editor better than capcut, 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.

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

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

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)

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

Common Workflows

Quick edit: Upload → "trim the footage, add transitions, and overlay 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.

Tips and Tricks

The backend processes faster when you're specific. Instead of "make it look better", try "trim the footage, add transitions, and overlay 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 for widest compatibility across TikTok, Instagram, and YouTube.