Video Editing With Ai Help

v1.0.0

edit raw video footage into edited video clips with this skill. Works with MP4, MOV, AVI, WebM files up to 500MB. content creators and marketers use it for e...

0· 45·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 vynbosserman65/video-editing-with-ai-help.

Previewing Install & Setup.
Prompt PreviewInstall & Setup
Install the skill "Video Editing With Ai Help" (vynbosserman65/video-editing-with-ai-help) from ClawHub.
Skill page: https://clawhub.ai/vynbosserman65/video-editing-with-ai-help
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-editing-with-ai-help

ClawHub CLI

Package manager switcher

npx clawhub@latest install video-editing-with-ai-help
Security Scan
VirusTotalVirusTotal
Pending
View report →
OpenClawOpenClaw
Benign
high confidence
Purpose & Capability
Name/description match the instructions and required credential (NEMO_TOKEN). One minor inconsistency: the frontmatter/metadata declares a config path (~/.config/nemovideo/) but the SKILL.md never instructs the agent to read or write that path. That mismatch is likely benign (extra metadata) but worth noting.
Instruction Scope
SKILL.md confines actions to connecting to the nemo API, creating/using a session, uploading user-provided video files (multipart or URL), streaming SSE responses, polling render status, and returning download URLs. There are no instructions to read arbitrary system files, secrets, or unrelated environment variables.
Install Mechanism
Instruction-only skill with no install steps or remote downloads. No code is written to disk by the skill itself, which is the lowest-risk install profile.
Credentials
The only required credential is NEMO_TOKEN (primaryEnv). That is appropriate and expected for a third-party cloud video API. The skill also documents how to obtain a short-lived anonymous token. No unrelated credentials or secrets are requested.
Persistence & Privilege
The skill is not always-enabled and does not request elevated platform privileges. It instructs saving session_id for the active session (normal for API usage) but does not modify other skills or global agent settings.
Assessment
This skill appears to do what it says: it uploads your videos to nemo's cloud service for AI-assisted editing and returns download URLs. Before installing or using it: (1) confirm you trust the endpoint https://mega-api-prod.nemovideo.ai and review that service's privacy/data-retention policy — your video files are sent off-device; (2) prefer the anonymous short-lived token flow if you don't want to store long-lived credentials; (3) be comfortable that uploaded content (including audio/text in the video) will be processed by the vendor; (4) note the metadata mentions a local config path (~/.config/nemovideo/) even though the runtime instructions don't reference it — if you have concerns, ask the publisher why that path is declared; and (5) revoke or rotate any tokens you set if you stop using the skill.

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

Runtime requirements

🎬 Clawdis
EnvNEMO_TOKEN
Primary envNEMO_TOKEN
latestvk9799b4yt31c8c83t3twshdz9185jnnm
45downloads
0stars
1versions
Updated 2d ago
v1.0.0
MIT-0

Getting Started

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

Try saying:

  • "edit my raw video footage"
  • "export 1080p MP4"
  • "cut the pauses, add background music,"

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 Editing with AI Help — Edit and Export Polished Videos

This tool takes your raw video footage and runs AI-assisted video editing through a cloud rendering pipeline. You upload, describe what you want, and download the result.

Say you have a 3-minute unedited screen recording and want to cut the pauses, add background music, and smooth the transitions — the backend processes it in about 1-2 minutes and hands you a 1080p MP4.

Tip: shorter clips under 2 minutes process significantly faster and give the AI more precise results.

Matching Input to Actions

User prompts referencing video editing with ai help, 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.

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

HeaderValue
X-Skill-Sourcevideo-editing-with-ai-help
X-Skill-Versionfrontmatter version
X-Skill-Platformauto-detect: clawhub / cursor / unknown from install path

Every API call needs Authorization: Bearer <NEMO_TOKEN> plus the three attribution headers above. If any header is missing, exports return 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.

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

Common Workflows

Quick edit: Upload → "cut the pauses, add background music, and smooth the transitions" → 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 "cut the pauses, add background music, and smooth the transitions" — 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.

Comments

Loading comments...