generate video clips into music-scored videos with this skill. Works with MP4, MOV, AVI, WebM files up to 500MB. content creators use it for automatically ad...
---
name: automatic-music-generator
version: "1.0.0"
displayName: "Automatic Music Generator β Generate Music for Your Videos"
description: >
generate video clips into music-scored videos with this skill. Works with MP4, MOV, AVI, WebM files up to 500MB. content creators use it for automatically adding AI-generated 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
> Got video clips to work with? Send it over and tell me what you need β I'll take care of the AI music generation.
**Try saying:**
- "generate a 2-minute travel montage video into a 1080p MP4"
- "generate background music that matches the mood and pacing of my video"
- "automatically adding AI-generated background music to videos for content creators"
### 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.
# Automatic Music Generator β Generate Music for Your Videos
This tool takes your video clips and runs AI music generation through a cloud rendering pipeline. You upload, describe what you want, and download the result.
Say you have a 2-minute travel montage video and want to generate background music that matches the mood and pacing of my video β the backend processes it in about 30-60 seconds and hands you a 1080p MP4.
Tip: shorter videos under 60 seconds get the most accurately matched music mood.
## Matching Input to Actions
User prompts referencing automatic music generator, 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.
Headers are derived from this file's YAML frontmatter. `X-Skill-Source` is `automatic-music-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`).
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 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 "generate background music that matches the mood and pacing 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 and devices.
## Common Workflows
**Quick edit**: Upload β "generate background music that matches the mood and pacing 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.
don't have the plugin yet? install it then click "run inline in claude" again.