Skills ai-music-video-generator

install
source · Clone the upstream repo
git clone https://github.com/openclaw/skills
Claude Code · Install into ~/.claude/skills/
T=$(mktemp -d) && git clone --depth=1 https://github.com/openclaw/skills "$T" && mkdir -p ~/.claude/skills && cp -r "$T/skills/bwbernardweston18/ai-music-video-generator" ~/.claude/skills/openclaw-skills-ai-music-video-generator && rm -rf "$T"
OpenClaw · Install into ~/.openclaw/skills/
T=$(mktemp -d) && git clone --depth=1 https://github.com/openclaw/skills "$T" && mkdir -p ~/.openclaw/skills && cp -r "$T/skills/bwbernardweston18/ai-music-video-generator" ~/.openclaw/skills/openclaw-skills-ai-music-video-generator && rm -rf "$T"
manifest: skills/bwbernardweston18/ai-music-video-generator/SKILL.md
source content

Getting Started

Ready when you are. Drop your audio files here or describe what you want to make.

Try saying:

  • "generate a 3-minute MP3 song file into a 1080p MP4"
  • "create a music video for my song with visuals that match the beat and mood"
  • "generating visual music videos from audio tracks for musicians and content 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.

AI Music Video Generator — Turn Songs Into Synced Videos

This tool takes your audio files and runs AI music video creation through a cloud rendering pipeline. You upload, describe what you want, and download the result.

Say you have a 3-minute MP3 song file and want to create a music video for my song with visuals that match the beat and mood — the backend processes it in about 1-3 minutes and hands you a 1080p MP4.

Tip: shorter tracks under 2 minutes process significantly faster.

Matching Input to Actions

User prompts referencing ai music video generator, 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.

Headers are derived from this file's YAML frontmatter.

X-Skill-Source
is
ai-music-video-generator
,
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 saysYou 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 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 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 "create a music video for my song with visuals that match the beat and mood" — concrete instructions get better results.

Max file size is 200MB. Stick to MP3, WAV, AAC, FLAC for the smoothest experience.

Export as MP4 for widest compatibility across YouTube, Instagram, and TikTok.

Common Workflows

Quick edit: Upload → "create a music video for my song with visuals that match the beat and mood" → Download MP4. Takes 1-3 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.