Tiktok Add Music To

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 requirements and runtime instructions are generally consistent with a cloud-based video-music-processing service, but there are a few small manifest/instruction mismatches and privacy-relevant behaviors to be aware of.

Purpose & Capability

Name/description (add music to TikTok videos) align with the runtime instructions: uploads, session creation, render/export endpoints and a single service credential (NEMO_TOKEN). Requesting a NEMO_TOKEN as the primary credential is proportionate for a cloud processing backend. Note: the SKILL.md frontmatter also references a config path (~/.config/nemovideo/) even though the top-level metadata listed no required config paths — a minor inconsistency.

Instruction Scope

Instructions stay within the stated purpose (upload video files, create sessions, submit render jobs, poll for results). They explicitly send user-uploaded media to an external API (mega-api-prod.nemovideo.ai) and will create an anonymous token if NEMO_TOKEN is absent. The skill also instructs the agent to detect install path and read the skill frontmatter to set attribution headers, which requires reading local paths (e.g., ~/.clawhub, ~/.cursor/skills/) — this is privacy-sensitive but not unrelated to the skill's stated behavior.

Install Mechanism

Instruction-only skill with no install spec and no code files; nothing is written to disk by an installer. This is the lowest-risk install pattern.

Credentials

Only one credential is declared (NEMO_TOKEN), which is appropriate for a single third-party service. The SKILL.md, however, implements a fallback that generates an anonymous token by contacting the service directly when NEMO_TOKEN is absent — this means the skill can obtain and use credentials autonomously. Also, the SKILL.md frontmatter references a local config path (~/.config/nemovideo/) not declared elsewhere in the registry metadata; that mismatch should be clarified.

Persistence & Privilege

The skill is not always-enabled and does not request elevated platform privileges. It maintains session state with the backend (session_id) for operation, which is normal for this type of cloud service. It does not request modification of other skills or system-wide settings.

Assessment

This skill appears to do what it says: it uploads videos to a third-party cloud service (mega-api-prod.nemovideo.ai) and returns rendered MP4s. Before installing or using it, consider: (1) you will be uploading your video files to an external API — confirm you trust that domain and understand their privacy/retention policy; (2) the skill will use a NEMO_TOKEN if provided or obtain an anonymous token itself (100 free credits, 7-day expiry) — don't reuse a sensitive token you use for other services; (3) the SKILL.md asks the agent to read local install paths (to set attribution headers) and references a local config directory (~/.config/nemovideo/) in its frontmatter — ask the publisher why that config path is needed and whether the skill will read or write files there; (4) there's no homepage or verifiable source listed — if you require higher assurance, ask the publisher for source/docs or prefer a skill with an identifiable vendor and privacy policy.

Getting Started

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

Try saying:

• "add my video clips"
• "export 1080p MP4"
• "add background music to my TikTok"

Quick Start Setup

This skill connects to a cloud processing backend. On first use, set up the connection automatically and let the user know ("Connecting...").

Token check: Look for NEMO_TOKEN in the environment. If found, skip to session creation. Otherwise:

• Generate a UUID as client identifier
• POST https://mega-api-prod.nemovideo.ai/api/auth/anonymous-token with X-Client-Id header
• Extract data.token from the response — this is your NEMO_TOKEN (100 free credits, 7-day expiry)

Session: POST https://mega-api-prod.nemovideo.ai/api/tasks/me/with-session/nemo_agent with Bearer auth and body {"task_name":"project"}. Keep the returned session_id for all operations.

Let the user know with a brief "Ready!" when setup is complete. Don't expose tokens or raw API output.

TikTok Add Music To — Add Music to TikTok Videos

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

Here's a typical use: you send a a 30-second TikTok clip without audio, ask for add background music to my TikTok video and sync it to the beat, and about 20-40 seconds later you've got a MP4 file ready to download. The whole thing runs at 1080p by default.

One thing worth knowing — shorter clips under 60 seconds process fastest and sync music more accurately.

Matching Input to Actions

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

Every API call needs Authorization: Bearer <NEMO_TOKEN> plus the three attribution headers above. If any header is missing, exports return 402.

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

• X-Skill-Source: tiktok-add-music-to
• 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 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

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

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.

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 background music to my TikTok video and sync it to the beat" — 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 with TikTok and other platforms.

Common Workflows

Quick edit: Upload → "add background music to my TikTok video and sync it to the beat" → 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.