Ai Music Generator

Skip the learning curve of professional editing software. Describe what you want — generate upbeat background music that matches the mood and pace of my vide...

Security Scan

The skill's requirements and instructions match its stated purpose (cloud-based AI music generation) and request only a single service token, but its source is unknown and it will upload your media to a third-party endpoint, so review privacy before use.

Purpose & Capability

The skill is an instruction-only AI music generator and requests a single bearer token (NEMO_TOKEN) and an optional config path under ~/.config/nemovideo/ — both are coherent with a cloud service that renders user video with AI-generated music.

Instruction Scope

Runtime instructions describe authenticating (including auto-requesting an anonymous token if none is present), creating a session, uploading user video files (up to 500MB), streaming edits via SSE, and polling export endpoints. All actions map to the described purpose, but the skill will transmit user media and session tokens to https://mega-api-prod.nemovideo.ai — users should be aware this is an external service and that the skill auto-creates and stores tokens/sessions.

Install Mechanism

No install spec or code files are present (instruction-only), so nothing is downloaded or written by an installer. This is the lowest-risk install posture.

Credentials

Only one credential is required: NEMO_TOKEN (the primaryEnv). That is proportional for a service requiring a bearer token. Note that the token grants access to the service and must be treated as sensitive.

Persistence & Privilege

The skill does not request 'always: true' or attempt to modify other skills or system-wide configs. It instructs storing a session_id and token for its own requests, which is normal for this use case.

Assessment

This skill appears to do what it says: it uploads your video to a third-party rendering service and returns a music-backed video. Before installing or using it: (1) confirm you are comfortable uploading your videos to https://mega-api-prod.nemovideo.ai — do not send sensitive or confidential footage; (2) understand that the skill will create and store an anonymous NEMO_TOKEN if none is provided — treat that token like a password and remove it when you no longer need the service; (3) the skill's source and homepage are missing, so you cannot easily verify the vendor — prefer skills with a known publisher or public docs; (4) if you need stronger guarantees (privacy, deletion policies, billing), contact the service owner or avoid sending sensitive content. If you want higher assurance, request the skill's source code or official documentation before use.

Getting Started

Share your video or images and I'll get started on AI music generation. Or just tell me what you're thinking.

Try saying:

• "generate my video or images"
• "export 1080p MP4"
• "generate upbeat background music that matches"

First-Time Connection

When a user first opens this skill, connect to the processing backend automatically. Briefly let them know (e.g. "Setting up...").

Authentication: Check if NEMO_TOKEN is set in the environment. If it is, skip to step 2.

1. Obtain a free token: Generate a random UUID as client identifier. POST to https://mega-api-prod.nemovideo.ai/api/auth/anonymous-token with header X-Client-Id set to that UUID. The response data.token is your NEMO_TOKEN — 100 free credits, valid 7 days.
2. Create a session: POST to https://mega-api-prod.nemovideo.ai/api/tasks/me/with-session/nemo_agent with Authorization: Bearer <token>, Content-Type: application/json, and body {"task_name":"project","language":"<detected>"}. Store the returned session_id for all subsequent requests.

Keep setup communication brief. Don't display raw API responses or token values to the user.

AI Music Generator — Generate Music for Your Videos

Drop your video or images in the chat and tell me what you need. I'll handle the AI music generation on cloud GPUs — you don't need anything installed locally.

Here's a typical use: you send a a 60-second travel montage clip, ask for generate upbeat background music that matches the mood and pace of my video, 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 — shorter videos allow the AI to better match music tempo to your content.

Matching Input to Actions

User prompts referencing ai 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.

All calls go to https://mega-api-prod.nemovideo.ai. The main endpoints:

1. Session — POST /api/tasks/me/with-session/nemo_agent with {"task_name":"project","language":"<lang>"}. Gives you a session_id.
2. Chat (SSE) — POST /run_sse with session_id and your message in new_message.parts[0].text. Set Accept: text/event-stream. Up to 15 min.
3. Upload — POST /api/upload-video/nemo_agent/me/<sid> — multipart file or JSON with URLs.
4. Credits — GET /api/credits/balance/simple — returns available, frozen, total.
5. State — GET /api/state/nemo_agent/me/<sid>/latest — current draft and media info.
6. Export — POST /api/render/proxy/lambda with render ID and draft JSON. Poll GET /api/render/proxy/lambda/<id> every 30s for completed status and download URL.

Formats: mp4, mov, avi, webm, mkv, jpg, png, gif, webp, mp3, wav, m4a, aac.

Headers are derived from this file's YAML frontmatter. X-Skill-Source is ai-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).

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.

Draft JSON uses short keys: t for tracks, tt for track type (0=video, 1=audio, 7=text), sg for segments, d for duration in ms, m for metadata.

Example timeline summary:

Timeline (3 tracks): 1. Video: city timelapse (0-10s) 2. BGM: Lo-fi (0-10s, 35%) 3. Title: "Urban Dreams" (0-3s)

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

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.

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

Common Workflows

Quick edit: Upload → "generate upbeat 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.