Skill flagged — suspicious patterns detected

ClawHub Security flagged this skill as suspicious. Review the scan results before using.

Youtube Audio Library

v1.0.0

add video files into music-enhanced videos with this skill. Works with MP4, MOV, AVI, WebM files up to 500MB. YouTubers use it for adding royalty-free music...

0· 92·0 current·0 all-time

Install

OpenClaw Prompt Flow

Install with OpenClaw

Best for remote or guided setup. Copy the exact prompt, then paste it into OpenClaw for susan4731-wilfordf/youtube-audio-library.

Previewing Install & Setup.
Prompt PreviewInstall & Setup
Install the skill "Youtube Audio Library" (susan4731-wilfordf/youtube-audio-library) from ClawHub.
Skill page: https://clawhub.ai/susan4731-wilfordf/youtube-audio-library
Keep the work scoped to this skill only.
After install, inspect the skill metadata and help me finish setup.
Required env vars: NEMO_TOKEN
Use only the metadata you can verify from ClawHub; do not invent missing requirements.
Ask before making any broader environment changes.

Command Line

CLI Commands

Use the direct CLI path if you want to install manually and keep every step visible.

OpenClaw CLI

Bare skill slug

openclaw skills install youtube-audio-library

ClawHub CLI

Package manager switcher

npx clawhub@latest install youtube-audio-library
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Suspicious
medium confidence
Purpose & Capability
The skill's name/description (add royalty-free music to videos) aligns with the required NEMO_TOKEN, declared config path (~/.config/nemovideo/), and the SKILL.md which documents upload, render, and export API calls to a nemo backend. Required env/config entries are consistent with a cloud rendering service.
!
Instruction Scope
Runtime instructions direct the agent to upload user video files and polling/render workflows to an external API (expected), but also instruct the agent to detect install path to set X-Skill-Platform, auto-generate anonymous tokens if NEMO_TOKEN is missing, and to 'keep technical details out of the chat' — these broaden what the agent will read/send (filesystem probing and automatic token acquisition) and reduce transparency to the user. All network calls go to an external third-party domain (mega-api-prod.nemovideo.ai), so private videos will be transmitted off-device.
Install Mechanism
No install specification or code files are present (instruction-only). This is low-risk from an install/execution perspective — nothing is downloaded or written by an installer.
Credentials
Only one environment credential is required (NEMO_TOKEN), which is proportionate to a cloud API service. However, the skill also instructs the agent to create anonymous tokens automatically if none are present (network call to the same domain), which could result in implicit session creation and unexpected uploads if the user is unaware.
Persistence & Privilege
The skill is not always-enabled, has no install actions, and does not request system-wide configuration changes. It does require temporary session state with the remote service (session_id/render job ids) but does not claim elevated platform privileges.
What to consider before installing
This skill appears to do what it says (upload video, add music, return a processed MP4), but exercise caution before using it with private or sensitive videos because it sends your files to an external domain (mega-api-prod.nemovideo.ai) operated by an unknown source and there is no homepage or source repository. Before installing/using: (1) ask the publisher for source code or a privacy policy and verify the backend domain; (2) only supply a NEMO_TOKEN if you trust the service; (3) avoid uploading sensitive footage — the skill will auto-create anonymous tokens and upload files if no token is provided; (4) consider local alternatives (offline editors or well-known cloud services) if you cannot verify the service; (5) ask the skill author to remove or clearly justify filesystem probing (install-path detection) and the instruction to hide technical details from the user. If you need more assurance, request the skill's source or a reputable homepage and replay the flows with non-sensitive test files first.

Like a lobster shell, security has layers — review code before you run it.

Runtime requirements

🎵 Clawdis
EnvNEMO_TOKEN
Primary envNEMO_TOKEN
latestvk973vf3dppg5w7qq6tcmk3wtt5853jce
92downloads
0stars
1versions
Updated 1w ago
v1.0.0
MIT-0

Getting Started

Share your video files and I'll get started on royalty-free audio matching. Or just tell me what you're thinking.

Try saying:

  • "add my video files"
  • "export 1080p MP4"
  • "find and add a royalty-free background"

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.

YouTube Audio Library — Add Royalty-Free Music to Videos

This tool takes your video files and runs royalty-free audio matching through a cloud rendering pipeline. You upload, describe what you want, and download the result.

Say you have a 3-minute YouTube vlog with no background music and want to find and add a royalty-free background track that matches the mood of my video — the backend processes it in about 30-60 seconds and hands you a 1080p MP4.

Tip: matching track tempo to your video pacing makes edits feel more natural.

Matching Input to Actions

User prompts referencing youtube audio library, aspect ratio, text overlays, or audio tracks get routed to the corresponding action via keyword and intent classification.

User says...ActionSkip 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.

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

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

Common Workflows

Quick edit: Upload → "find and add a royalty-free background track that matches the mood of my video" → Download MP4. Takes 30-60 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.

Tips and Tricks

The backend processes faster when you're specific. Instead of "make it look better", try "find and add a royalty-free background track that matches the mood of my 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 with YouTube uploads.

Comments

Loading comments...