Music Generator Free

Skip the learning curve of professional editing software. Describe what you want — generate a free background music track for my video with an upbeat, energe...

Security Scan

The skill's requirements and runtime instructions are consistent with a cloud-based AI music generator: it talks to a NemoVideo API, uses a single service token, and uploads user media — nothing requested appears unrelated to its stated purpose, though there are small metadata inconsistencies and privacy/persistence considerations to review before installing.

Purpose & Capability

The skill name and description match the behavior in SKILL.md: it sends user prompts/files to a remote NemoVideo render service and returns generated tracks. The required env var NEMO_TOKEN is appropriate. Minor incoherence: the registry metadata listed no required config paths, but the SKILL.md frontmatter references a config path (~/.config/nemovideo/) for token/session storage.

Instruction Scope

Instructions are scoped to connecting to the nemo API, creating an anonymous token (if none provided), creating sessions, uploading user files, streaming SSE responses, and exporting renders. These actions align with the stated purpose. The skill instructs the agent to auto-obtain and store tokens and session_ids and to not display raw tokens — this is expected but worth noting because it results in tokens being created and persisted without explicit user copy-paste.

Install Mechanism

No install spec or code files are present (instruction-only), so nothing will be downloaded or written by an installer step beyond what the agent does at runtime. This is the lowest install risk.

Credentials

Only one credential (NEMO_TOKEN) is declared and used. That is proportionate for a service that authenticates requests. No unrelated credentials or broad permissions are requested.

Persistence & Privilege

always:false and normal autonomous invocation make sense. The skill advises storing the anonymous token and session_id (and names a possible config path ~/.config/nemovideo/), so it will persist credentials locally for reuse — expected for UX but a persistence/privacy consideration the user should be aware of.

Assessment

This skill appears to do what it says: it uploads your media and talks to a nemo video render API using a single token. Before installing, consider: (1) uploads and prompts are sent to an external service (mega-api-prod.nemovideo.ai) — don't upload sensitive data; (2) the skill will create and store an anonymous NEMO_TOKEN (valid ~7 days) if you don't provide one — tokens enable the service to act on your behalf, so treat them like credentials and delete/revoke them if needed; (3) the SKILL.md references a config directory (~/.config/nemovideo/) not present in the registry declaration — confirm where tokens/sessions are stored and whether you want that persisted; (4) no other credentials are requested, and there is no install step, which limits local risk. If you need higher assurance, ask the publisher for a homepage/privacy policy and verify the API domain and retention policy for uploaded files and generated artifacts.

Getting Started

Got text or mood input 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 60-second upbeat background track prompt into a 1080p MP4"
• "generate a free background music track for my video with an upbeat, energetic vibe"
• "generating free background music for videos for content creators, YouTubers, TikTok creators"

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.

Music Generator Free — Generate Free AI Music Tracks

This tool takes your text or mood input and runs AI music generation through a cloud rendering pipeline. You upload, describe what you want, and download the result.

Say you have a 60-second upbeat background track prompt and want to generate a free background music track for my video with an upbeat, energetic vibe — the backend processes it in about 20-40 seconds and hands you a 1080p MP4.

Tip: shorter duration prompts generate faster and give more consistent results.

Matching Input to Actions

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

Base URL: https://mega-api-prod.nemovideo.ai

Endpoint	Method	Purpose
/api/tasks/me/with-session/nemo_agent	POST	Start a new editing session. Body: {"task_name":"project","language":"<lang>"}. Returns session_id.
/run_sse	POST	Send a user message. Body includes app_name, session_id, new_message. Stream response with Accept: text/event-stream. Timeout: 15 min.
/api/upload-video/nemo_agent/me/<sid>	POST	Upload a file (multipart) or URL.
/api/credits/balance/simple	GET	Check remaining credits (available, frozen, total).
/api/state/nemo_agent/me/<sid>/latest	GET	Fetch current timeline state (draft, video_infos, generated_media).
/api/render/proxy/lambda	POST	Start export. Body: {"id":"render_<ts>","sessionId":"<sid>","draft":<json>,"output":{"format":"mp4","quality":"high"}}. Poll status every 30s.

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

Three attribution headers are required on every request and must match this file's frontmatter:

Header	Value
X-Skill-Source	music-generator-free
X-Skill-Version	frontmatter version
X-Skill-Platform	auto-detect: clawhub / cursor / unknown from install path

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.

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

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 says	You 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 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)

Tips and Tricks

The backend processes faster when you're specific. Instead of "make it look better", try "generate a free background music track for my video with an upbeat, energetic vibe" — concrete instructions get better results.

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

Export as MP4 for widest compatibility when combining music with video.

Common Workflows

Quick edit: Upload → "generate a free background music track for my video with an upbeat, energetic vibe" → Download MP4. Takes 20-40 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.