Skill flagged — suspicious patterns detected
ClawHub Security flagged this skill as suspicious. Review the scan results before using.
AI-Music-Stream
v1.0.4Generate AI music from text prompts and stream continuously in-browser with a shareable player URL; all tracks are saved locally in a library.
⭐ 0· 92·0 current·0 all-time
byJu-Chiang Wang@asriverwang
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Suspicious
medium confidencePurpose & Capability
The skill's description and SKILL.md describe a Sonauto-backed music generator and local streaming server. However the registry metadata lists no required environment variables or primary credential, while the code and SKILL.md clearly require a Sonauto API key (SONAUTO_API_KEY) and a config.json. This discrepancy between what is declared and what is actually required is incoherent and should be corrected.
Instruction Scope
Most runtime instructions stay within the stated purpose (start server, call /start, save files). However the docs explicitly encourage replacing 'localhost' with an external IP or using tunnels/reverse proxies to expose the service and recommend the agent perform substitutions — this increases the risk of unwanted external exposure. The SKILL.md also tells the agent to collect contextual info (time, weather, location, traffic, mood) to craft prompts; collecting location/traffic data is privacy-sensitive and should be limited to what the user consents to. Overall the instruction set gives broad discretion to expose the server externally and to collect contextual data, which is beyond a minimal local music-generator scope.
Install Mechanism
This is an instruction-and-code skill (no packaged install). It requires pip installing two common packages (flask, requests) from PyPI and running the included Python script. There are no downloads from unknown hosts, no archive extraction, and the restart script simply runs the included Python program via nohup — install risk is moderate-to-low but you should still review code before running.
Credentials
The code expects and uses SONAUTO_API_KEY (and optional MUSESTREAM_* config values stored in config.json) but the skill metadata declares no required env vars or primary credential. The server will persist logs (log.jsonl) and save generated audio to a user-specified directory. The messenger-bot integration mentioned in docs would likely require additional tokens, but no bot tokens are requested or declared. Requiring an API key and writing files is reasonable for this functionality, but the omission from declared requirements and lack of explicit guidance for secure secret storage is concerning.
Persistence & Privilege
The skill does not request elevated platform privileges and is not always-enabled. It runs a local Flask server, writes saved audio and a JSONL log to the selected output directory, and starts itself via a simple restart script. The biggest persistence/privilege risk is network exposure: the README/SKILL.md encourage exposing the local server (substituting external IP or using tunnels) which materially increases blast radius if done without authentication and TLS. The skill itself does not automatically modify other agent/system configs.
What to consider before installing
Before installing: (1) Understand the missing declaration — the code requires a Sonauto API key (SONAUTO_API_KEY) via config.json or env, but the skill metadata lists none; do not share keys publicly or commit them to source control. (2) Review the musestream_server.py and restart script locally before running; the server will save generated audio and a log file in your chosen directory. (3) Do NOT expose the server to the internet without protections: add token-based auth, TLS reverse proxy, IP firewall rules, and rate-limiting as suggested in the README. (4) Be cautious about providing sensitive context (location, traffic) to the agent; limit context to what you consent to share. (5) If you plan messenger integration, expect to provide additional bot tokens — verify where and how those tokens are stored. (6) Ask the skill owner/registry to update the declared required env/credentials to reflect SONAUTO_API_KEY and any other secrets the code actually needs. If you are uncomfortable with these mismatches or exposing a local server, run the skill in an isolated environment (VM/container) or decline installation.Like a lobster shell, security has layers — review code before you run it.
latestvk97f62v5e8gvtbhy94a86sz6yd83kc7z
License
MIT-0
Free to use, modify, and redistribute. No attribution required.