Music To Youtube

Skip the learning curve of professional editing software. Describe what you want — turn my music track into a YouTube video with a visualizer and track title...

Security Scan

The skill's runtime instructions mostly match its stated purpose (cloud video rendering), but there are inconsistent metadata claims (required env/config) and it will upload user audio to a third-party API — review privacy and the metadata mismatch before installing.

Purpose & Capability

The name/description ('convert music track to a YouTube-ready MP4') aligns with the instructions to upload audio and request renders from mega-api-prod.nemovideo.ai. However, the SKILL.md frontmatter lists a config path (~/.config/nemovideo/) that is not shown in the registry metadata, and the description could be read as 'upload to YouTube' while the implementation only produces a downloadable MP4 (no direct YouTube upload). These mismatches should be clarified.

Instruction Scope

The SKILL.md contains explicit, detailed runtime steps: read NEMO_TOKEN from env, or generate an anonymous token by POSTing to the service; create sessions; upload files; stream/poll SSE endpoints; include attribution headers derived from local install path. All of these are within the scope of a cloud rendering service, but the document also instructs deriving X-Skill-Platform from local install paths (which can reveal local info) and to keep technical steps out of chat — both worth noting. The skill will transmit user audio and any provided images to an external domain (nemovideo.ai).

Install Mechanism

No install spec and no code files — instruction-only. That minimizes local write/execution risk (nothing is downloaded or installed).

Credentials

Registry declares NEMO_TOKEN as required/primary, but SKILL.md documents a fallback anonymous-token acquisition path if NEMO_TOKEN is absent (in practice the skill can run without providing a token). SKILL.md frontmatter also lists a config path (~/.config/nemovideo/) even though registry metadata listed none. The skill also asks to derive a header value from the install path, potentially reading or revealing local path information. These inconsistencies and the potential for leaking local install path info are disproportionate and should be clarified.

Persistence & Privilege

always is false and the skill does not request system-wide configuration changes. It creates short-lived sessions on the backend, which is normal for a cloud service. No elevated persistent privileges are requested.

What to consider before installing

This skill appears to do what it says (upload audio to a cloud renderer and return an MP4), but review these points before installing: (1) It will upload your audio/images to https://mega-api-prod.nemovideo.ai — do not upload sensitive or unpublished material unless you trust their privacy/terms. (2) The registry says NEMO_TOKEN is required, but the skill can obtain an anonymous token itself; clarify whether you must provide your own token. (3) The SKILL.md frontmatter lists a local config path (~/.config/nemovideo/) that the registry did not — ask the author why that path is declared and whether the skill will read local config files. (4) The skill asks to derive an attribution header from the agent’s install path, which can reveal local path information; if that concerns you, ask for a version that does not send local path metadata. If you need stronger assurance, request the skill author to (a) remove the config path requirement or document exactly what is read locally, (b) confirm whether any credentials or user files are stored long-term on their backend, and (c) provide a privacy link or service TOS. Because metadata is inconsistent, proceed cautiously.

Getting Started

Share your audio files and I'll get started on YouTube video creation. Or just tell me what you're thinking.

Try saying:

• "convert my audio files"
• "export 1080p MP4"
• "turn my music track into a"

Getting Connected

Before handling any user request, establish a connection to the backend API. Show a brief status like "Connecting...".

If NEMO_TOKEN is in the environment, use it directly and create a session. Otherwise, acquire a free starter token:

• Generate a UUID as client identifier
• POST to https://mega-api-prod.nemovideo.ai/api/auth/anonymous-token with the X-Client-Id header
• The response includes a token with 100 free credits valid for 7 days — use it as NEMO_TOKEN

Then create a session by POSTing to https://mega-api-prod.nemovideo.ai/api/tasks/me/with-session/nemo_agent with Bearer authorization and body {"task_name":"project","language":"en"}. The session_id in the response is needed for all following requests.

Tell the user you're ready. Keep the technical details out of the chat.

Music to YouTube — Convert Music Tracks to Videos

Drop your audio files in the chat and tell me what you need. I'll handle the YouTube video creation on cloud GPUs — you don't need anything installed locally.

Here's a typical use: you send a a 3-minute MP3 music track, ask for turn my music track into a YouTube video with a visualizer and track title overlay, and about 1-2 minutes later you've got a MP4 file ready to download. The whole thing runs at 1080p by default.

One thing worth knowing — adding a static cover image or looping background keeps the video engaging for the full track duration.

Matching Input to Actions

User prompts referencing music to youtube, 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.

Headers are derived from this file's YAML frontmatter. X-Skill-Source is music-to-youtube, 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.

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

SSE Event Handling

Event	Action
Text response	Apply GUI translation (§4), present to user
Tool call/result	Process internally, don't forward
heartbeat / empty data:	Keep waiting. Every 2 min: "⏳ Still working..."
Stream closes	Process final response

~30% of editing operations return no text in the SSE stream. When this happens: poll session state to verify the edit was applied, then summarize changes to the user.

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

Tips and Tricks

The backend processes faster when you're specific. Instead of "make it look better", try "turn my music track into a YouTube video with a visualizer and track title overlay" — concrete instructions get better results.

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

Export as MP4 with H.264 codec for best compatibility with YouTube's upload requirements.

Common Workflows

Quick edit: Upload → "turn my music track into a YouTube video with a visualizer and track title overlay" → 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.