Tiktok Add Music

Get music-backed videos ready to post, without touching a single slider. Upload your video clips (MP4, MOV, AVI, WebM, up to 500MB), say something like "add...

Security Scan

The skill's instructions match its stated purpose (adding music to videos) and only request one credential (NEMO_TOKEN), but there are inconsistent metadata and minor scope concerns (reading config/install paths) that merit caution before installing.

Purpose & Capability

The name/description (add music to TikTok videos) aligns with the instructions: the SKILL.md documents endpoints to upload video, run a render/export job, poll for status, and return a download URL. Requiring a service token (NEMO_TOKEN) and the described API calls are coherent with the stated purpose.

Instruction Scope

Most runtime instructions stay within the expected scope (establish session, upload files, poll SSE, render/export). However the SKILL.md instructs the agent to read the skill's frontmatter and to detect the install path to set X-Skill-Platform, and the frontmatter lists a config path (~/.config/nemovideo/). Reading install/config paths is outside the core audio-addition task and could expose unrelated local configuration if implemented; this is worth noting.

Install Mechanism

No install spec and no code files (instruction-only). This minimizes on-disk execution risk — nothing is fetched or installed by the skill itself.

Credentials

The skill only requires one credential (NEMO_TOKEN), which is proportionate for a cloud rendering service. But the frontmatter's configPaths (~/.config/nemovideo/) is either unnecessary or inconsistent with the registry metadata (which listed no config paths). If the agent actually reads that path it could expose other Nemovideo-related credentials or files. The skill also instructs anonymous token acquisition if NEMO_TOKEN is missing, which is acceptable but means the skill will make network auth calls on the user's behalf.

Persistence & Privilege

always:false and no install means the skill does not request persistent/system-wide presence or elevated privileges. It does not attempt to modify other skills or agent configs.

What to consider before installing

This skill appears to do what it says (upload your video to a nemovideo.ai backend, add music, and return a download URL) and only asks for one token (NEMO_TOKEN). Before installing, consider: 1) NEMO_TOKEN is a credential — confirm what that token grants and whether you want to share it with this skill; if unsure prefer using an anonymous token flow or a short-lived token. 2) The SKILL.md references reading an install path and a config directory (~/.config/nemovideo/); ask the skill author why that is needed and what the skill will read from that path. 3) The skill source and homepage are unknown — verify the backend domain (mega-api-prod.nemovideo.ai) and the publisher before uploading private videos. 4) Because this is instruction-only, nothing is installed locally, but your videos and metadata will be sent to an external service — review privacy/retention policies. If you need stronger assurance, request a clear privacy statement from the publisher or run music addition via a local tool instead.

Getting Started

Send me your video clips and I'll handle the AI music addition. Or just describe what you're after.

Try saying:

• "add a 30-second TikTok clip without background music into a 1080p MP4"
• "add a trending background track that fits the mood of my TikTok video"
• "adding background music to TikTok videos for TikTok creators"

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.

TikTok Add Music — Add Music to TikTok Videos

This tool takes your video clips and runs AI music addition through a cloud rendering pipeline. You upload, describe what you want, and download the result.

Say you have a 30-second TikTok clip without background music and want to add a trending background track that fits the mood of my TikTok video — the backend processes it in about 20-40 seconds and hands you a 1080p MP4.

Tip: vertical 9:16 video works perfectly for TikTok output.

Matching Input to Actions

User prompts referencing tiktok add music, 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 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.

Skill attribution — read from this file's YAML frontmatter at runtime:

• X-Skill-Source: tiktok-add-music
• X-Skill-Version: from frontmatter version
• X-Skill-Platform: detect from install path (~/.clawhub/ → clawhub, ~/.cursor/skills/ → cursor, else unknown)

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.

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

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

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.

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 "add a trending background track that fits the mood of my TikTok 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 TikTok and other platforms.

Common Workflows

Quick edit: Upload → "add a trending background track that fits the mood of my TikTok video" → 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.