Video Editor Capcut

v1.0.0

Get edited video clips ready to post, without touching a single slider. Upload your raw video clips (MP4, MOV, AVI, WebM, up to 500MB), say something like "t...

0· 106·0 current·0 all-time

Install

OpenClaw Prompt Flow

Install with OpenClaw

Best for remote or guided setup. Copy the exact prompt, then paste it into OpenClaw for mhogan2013-9/video-editor-capcut.

Previewing Install & Setup.
Prompt PreviewInstall & Setup
Install the skill "Video Editor Capcut" (mhogan2013-9/video-editor-capcut) from ClawHub.
Skill page: https://clawhub.ai/mhogan2013-9/video-editor-capcut
Keep the work scoped to this skill only.
After install, inspect the skill metadata and help me finish setup.
Required env vars: NEMO_TOKEN
Use only the metadata you can verify from ClawHub; do not invent missing requirements.
Ask before making any broader environment changes.

Command Line

CLI Commands

Use the direct CLI path if you want to install manually and keep every step visible.

OpenClaw CLI

Bare skill slug

openclaw skills install video-editor-capcut

ClawHub CLI

Package manager switcher

npx clawhub@latest install video-editor-capcut
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
Purpose & Capability
The name and description promise cloud-based AI video editing; the SKILL.md describes a cloud API for session creation, upload, SSE-driven editing, and export. The single required env var (NEMO_TOKEN) and the declared config path align with a dedicated video-editing backend.
Instruction Scope
Runtime instructions focus on creating/using a session token, uploading video files, polling renders, and reporting status. They do not instruct reading unrelated system files or harvesting unrelated environment variables. The skill will send user video files and metadata to the described API (mega-api-prod.nemovideo.ai), which is expected for this purpose.
Install Mechanism
No install spec or code files are present (instruction-only). That minimizes on-disk execution risk; all actions are HTTP interactions described in SKILL.md.
Credentials
Only NEMO_TOKEN is required and marked primary. The SKILL.md also documents how an anonymous token may be obtained if none is present. There are no unrelated secret env vars requested. The metadata lists a config path (~/.config/nemovideo/) which is plausible for storing service config, though the instructions do not require reading it.
Persistence & Privilege
The skill is not always-enabled and does not request elevated platform privileges. It does not instruct modifying other skills or system-wide agent settings; its behavior is limited to interacting with its own cloud backend.
Assessment
This skill uploads whatever video files you provide to the nemovideo.ai backend and uses a single service token (NEMO_TOKEN) to authenticate. Before installing or using it: (1) Confirm you trust the domain (mega-api-prod.nemovideo.ai) and its privacy/storage practices before uploading sensitive video content; (2) Prefer using an anonymous/token tied to this service (the skill can create one) rather than a shared secret; (3) Expect uploads and renders to occur on remote GPUs and that files will be transmitted over the network; (4) Check retention/cost/credit rules (tokens expire after 7 days and some operations may require registration/upgrades per the docs); (5) If you keep a long-lived NEMO_TOKEN in your environment, treat it like a service credential and rotate/revoke it if leaked.

Like a lobster shell, security has layers — review code before you run it.

Runtime requirements

🎬 Clawdis
EnvNEMO_TOKEN
Primary envNEMO_TOKEN
latestvk978fm90jx1mbvkyaxnfpsnjgd84sqnc
106downloads
0stars
1versions
Updated 2w ago
v1.0.0
MIT-0

Getting Started

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

Try saying:

  • "edit a 60-second vertical phone recording into a 1080p MP4"
  • "trim the clip, add text overlays, and sync background music"
  • "editing short-form videos for TikTok and Reels for TikTok creators"

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

Drop your raw video clips in the chat and tell me what you need. I'll handle the AI video editing on cloud GPUs — you don't need anything installed locally.

Here's a typical use: you send a a 60-second vertical phone recording, ask for trim the clip, add text overlays, and sync background music, and about 30-60 seconds later you've got a MP4 file ready to download. The whole thing runs at 1080p by default.

One thing worth knowing — vertical 9:16 video works perfectly for TikTok and Instagram Reels exports.

Matching Input to Actions

User prompts referencing video editor capcut, aspect ratio, text overlays, or audio tracks get routed to the corresponding action via keyword and intent classification.

User says...ActionSkip 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.

Include Authorization: Bearer <NEMO_TOKEN> and all attribution headers on every request — omitting them triggers a 402 on export.

Three attribution headers are required on every request and must match this file's frontmatter:

HeaderValue
X-Skill-Sourcevideo-editor-capcut
X-Skill-Versionfrontmatter version
X-Skill-Platformauto-detect: clawhub / cursor / unknown from install path

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

CodeMeaningAction
0SuccessContinue
1001Bad/expired tokenRe-auth via anonymous-token (tokens expire after 7 days)
1002Session not foundNew session §3.0
2001No creditsAnonymous: show registration URL with ?bind=<id> (get <id> from create-session or state response when needed). Registered: "Top up credits in your account"
4001Unsupported fileShow supported formats
4002File too largeSuggest compress/trim
400Missing X-Client-IdGenerate Client-Id and retry (see §1)
402Free plan export blockedSubscription tier issue, NOT credits. "Register or upgrade your plan to unlock export."
429Rate limit (1 token/client/7 days)Retry in 30s once

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

SSE Event Handling

EventAction
Text responseApply GUI translation (§4), present to user
Tool call/resultProcess internally, don't forward
heartbeat / empty data:Keep waiting. Every 2 min: "⏳ Still working..."
Stream closesProcess 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.

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)

Tips and Tricks

The backend processes faster when you're specific. Instead of "make it look better", try "trim the clip, add text overlays, 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 for widest compatibility across all social platforms.

Common Workflows

Quick edit: Upload → "trim the clip, add text overlays, and sync background music" → Download MP4. Takes 30-60 seconds 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.

Comments

Loading comments...