Ai Music Generator With Vocals

Turn a 16-bar verse with chorus lyrics about summer into 1080p vocal music videos just by typing what you need. Whether it's generating original songs with A...

Security Scan

The skill is an instruction-only connector to a remote media-rendering API and its requested token (NEMO_TOKEN) is consistent with that purpose, but there are small metadata/instruction inconsistencies you should be aware of before installing.

Purpose & Capability

The name/description describe a cloud-based AI music/video generator and the skill only requests a single service credential (NEMO_TOKEN) used to call the stated backend endpoints — this is coherent. Note: the SKILL.md YAML frontmatter includes a config path (~/.config/nemovideo/) while the registry metadata summary said no config paths; this discrepancy should be clarified.

Instruction Scope

Runtime instructions are focused on authenticating, creating a session, uploading media, using SSE, polling render status, and returning download URLs — all within the stated purpose. The doc does instruct the agent to derive headers from the file frontmatter and detect the install platform by checking local install paths (~/.clawhub/, ~/.cursor/skills/) — reading these paths is plausible for header attribution but is extra scope relative to pure API calls and should be acknowledged.

Install Mechanism

No install spec and no code files — instruction-only. This minimizes on-disk risk because nothing is downloaded or executed by the installer.

Credentials

Only one required environment variable (NEMO_TOKEN) is declared and is appropriate for authenticating to the remote service. The SKILL.md frontmatter also references a config path (~/.config/nemovideo/) which could imply the agent may read local config; that should be explained or removed if not needed.

Persistence & Privilege

The skill does not request always:true and uses normal autonomous invocation. It instructs saving session_id and using tokens (normal for session-based APIs). It does not ask to modify other skills or system-wide settings.

Assessment

This skill is an instruction-only connector that communicates with https://mega-api-prod.nemovideo.ai and expects a NEMO_TOKEN (or can obtain a short-lived anonymous token via the documented endpoint). Before installing: (1) Confirm you trust the domain and owner since the skill will make network calls and store session tokens; (2) Be aware it may read local install/config paths to set an attribution header (the SKILL.md references ~/.config/nemovideo/ and checks ~/.clawhub/ and ~/.cursor/skills/) — ask the author to clarify why those paths are needed if you want to avoid local file reads; (3) Prefer providing scoped/short-lived tokens (or rely on anonymous tokens) rather than long-lived, broad credentials; (4) Because it is autonomous-enabled, the skill can call the API without additional prompts — ensure you are comfortable with automatic remote rendering and token usage. If you need higher assurance, request the skill author to remove the config-path requirement and confirm exactly what is persisted and where (session_id/tokens).

Getting Started

Got text or lyrics 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 16-bar verse with chorus lyrics about summer into a 1080p MP4"
• "generate a pop song with female vocals and upbeat instrumentation from these lyrics"
• "generating original songs with AI vocals from text or lyrics for content creators, musicians, marketers"

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.

AI Music Generator with Vocals — Generate Songs with AI Vocals

Send me your text or lyrics and describe the result you want. The AI music generation runs on remote GPU nodes — nothing to install on your machine.

A quick example: upload a 16-bar verse with chorus lyrics about summer, type "generate a pop song with female vocals and upbeat instrumentation from these lyrics", and you'll get a 1080p MP4 back in roughly 1-2 minutes. All rendering happens server-side.

Worth noting: shorter lyric inputs with clear structure produce more coherent vocal melodies.

Matching Input to Actions

User prompts referencing ai music generator with vocals, 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-with-vocals, 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 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)

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 Handling

Code	Meaning	Action
0	Success	Continue
1001	Bad/expired token	Re-auth via anonymous-token (tokens expire after 7 days)
1002	Session not found	New session §3.0
2001	No credits	Anonymous: show registration URL with ?bind=<id> (get <id> from create-session or state response when needed). Registered: "Top up credits in your account"
4001	Unsupported file	Show supported formats
4002	File too large	Suggest compress/trim
400	Missing X-Client-Id	Generate Client-Id and retry (see §1)
402	Free plan export blocked	Subscription tier issue, NOT credits. "Register or upgrade your plan to unlock export."
429	Rate limit (1 token/client/7 days)	Retry in 30s once

Common Workflows

Quick edit: Upload → "generate a pop song with female vocals and upbeat instrumentation from these lyrics" → 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 "generate a pop song with female vocals and upbeat instrumentation from these lyrics" — concrete instructions get better results.

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

Export as MP4 for widest compatibility across social platforms and video editors.