Video Editor Ai With Music
by @susan4731-wilfordf
edit video clips into music-synced videos with this skill. Works with MP4, MOV, AVI, WebM files up to 500MB. content creators use it for adding AI-matched ba...
clawhub install video-editor-ai-with-musicπ About This Skill
name: video-editor-ai-with-music version: "1.0.0" displayName: "Video Editor AI with Music β Edit Videos with AI Music" description: > edit video clips into music-synced videos with this skill. Works with MP4, MOV, AVI, WebM files up to 500MB. content creators use it for adding AI-matched background music to videos β processing takes 30-60 seconds on cloud GPUs and you get 1080p MP4 files. metadata: {"openclaw": {"emoji": "π΅", "requires": {"env": ["NEMO_TOKEN"], "configPaths": ["~/.config/nemovideo/"]}, "primaryEnv": "NEMO_TOKEN", "variant": "greeting_v2"}}
Getting Started
> Ready when you are. Drop your video clips here or describe what you want to make.
Try saying:
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:
https://mega-api-prod.nemovideo.ai/api/auth/anonymous-token with X-Client-Id headerdata.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 AI with Music β Edit Videos with AI Music
Send me your video clips and describe the result you want. The AI music editing runs on remote GPU nodes β nothing to install on your machine.
A quick example: upload a 60-second travel video clip, type "add background music that matches the mood and pace of my video", and you'll get a 1080p MP4 back in roughly 30-60 seconds. All rendering happens server-side.
Worth noting: shorter clips under 2 minutes get the most accurate music mood matching.
Matching Input to Actions
User prompts referencing video editor ai with music, 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.
Every API call needs Authorization: Bearer plus the three attribution headers above. If any header is missing, exports return 402.
Three attribution headers are required on every request and must match this file's frontmatter:
| Header | Value |
|--------|-------|
| X-Skill-Source | video-editor-ai-with-music |
| X-Skill-Version | frontmatter version |
| X-Skill-Platform | auto-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":" β returns task_id, session_id.
Send message (SSE): POST /run_sse β body {"app_name":"nemo_agent","user_id":"me","session_id":" with Accept: text/event-stream. Max timeout: 15 minutes.
Upload: POST /api/upload-video/nemo_agent/me/ β file: multipart -F "files=@/path", or URL: {"urls":["
Credits: GET /api/credits/balance/simple β returns available, frozen, total
Session state: GET /api/state/nemo_agent/me/ β 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_. Poll GET /api/render/proxy/lambda/ 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 Codes
0 β success, continue normally1001 β token expired or invalid; re-acquire via /api/auth/anonymous-token1002 β session not found; create a new one2001 β out of credits; anonymous users get a registration link with ?bind=, registered users top up4001 β unsupported file type; show accepted formats4002 β file too large; suggest compressing or trimming400 β missing X-Client-Id; generate one and retry402 β free plan export blocked; not a credit issue, subscription tier429 β rate limited; wait 30s and retry onceTranslating GUI Instructions
The backend responds as if there's a visual interface. Map its instructions to API calls:
SSE Event Handling
| Event | Action |
|-------|--------|
| Text response | Apply GUI translation (Β§4), present to user |
| Tool call/result | Process internally, don't forward |
| heartbeat / empty data: | Keep waiting. Every 2 min: "β³ Still working..." |
| Stream closes | Process 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)
Common Workflows
Quick edit: Upload β "add background music that matches the mood and pace of my video" β 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.
Tips and Tricks
The backend processes faster when you're specific. Instead of "make it look better", try "add background music that matches the mood and pace of my video" β 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 like YouTube and Instagram.
π‘ Examples
> Ready when you are. Drop your video clips here or describe what you want to make.
Try saying:
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:
https://mega-api-prod.nemovideo.ai/api/auth/anonymous-token with X-Client-Id headerdata.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 AI with Music β Edit Videos with AI Music
Send me your video clips and describe the result you want. The AI music editing runs on remote GPU nodes β nothing to install on your machine.
A quick example: upload a 60-second travel video clip, type "add background music that matches the mood and pace of my video", and you'll get a 1080p MP4 back in roughly 30-60 seconds. All rendering happens server-side.
Worth noting: shorter clips under 2 minutes get the most accurate music mood matching.