Skill flagged — suspicious patterns detected
ClawHub Security flagged this skill as suspicious. Review the scan results before using.
Bumblebee + R2-DJ
v1.2.0Two modes: (1) BUMBLEBEE — Communicate through music by playing exact lyric lines on Spotify, like Bumblebee from Transformers speaking through radio snippet...
⭐ 0· 90·0 current·0 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Suspicious
medium confidencePurpose & Capability
The code and SKILL.md clearly implement Spotify playback, lyric indexing, and contextual queuing — which matches the description. However the skill metadata claims no required env vars or binaries while the README/SKILL.md and the code require Node.js and Spotify OAuth tokens/client secrets stored in projects/spotify (tokens.json and .env). The registry listing omits these required artifacts, which is an incoherence.
Instruction Scope
Runtime instructions and scripts instruct the agent to read/write local token files, access the user's Spotify history, call LRCLIB and Spotify APIs, and optionally build a lyric index from the user's library. Those actions are within the stated purpose, but they involve retrieving and storing sensitive tokens and reading user listening history — ensure you expect those data flows. Also the README/SETUP recommend an automated agent build flow ("Let Your Agent Build It") which grants the agent permission to fetch your library/lyrics to create index files.
Install Mechanism
There is no formal install spec in the registry (instruction-only), yet the bundle includes multiple Node.js scripts and a large lyric-index.json. The package assumes Node.js 18+ but the registry didn't declare required binaries. Also bumblebee.js expects a local lyrics-db.json file (and the code reads projects/spotify paths); the manifest does not clearly include lyrics-db.json, so the shipped bundle may be incomplete and could fail or behave unexpectedly at runtime.
Credentials
Although the registry lists no required env vars, the SKILL.md and code require SPOTIFY_CLIENT_ID and SPOTIFY_CLIENT_SECRET (in projects/spotify/.env) and a tokens.json containing access_token and permanent refresh_token. The skill reads and writes these files (including persisting refresh_token). Requesting permanent OAuth tokens and client secrets is functionally necessary for Spotify control, but the metadata omission and file-path usage are disproportionate if you weren't warned — treat these as sensitive credentials.
Persistence & Privilege
The skill does not set always:true and does not declare modification of other skills or system configs. It does persist tokens to projects/spotify/tokens.json (including refresh_token) and auto-refreshes them, which is normal for a Spotify integration but increases blast radius if the skill is malicious or compromised. Autonomous invocation is enabled (default) — combine that with credential access and you should be cautious.
What to consider before installing
Do not install blindly. The skill requires Node.js and will read/write sensitive Spotify credentials in projects/spotify/.env and tokens.json (including a permanent refresh_token). Confirm the package actually includes the expected files (lyrics-db.json and the lyric index) and test in a sandbox or VM first. If you grant Spotify credentials, expect the skill to access playback, recent history and modify playback/queues. If you are uncomfortable granting a permanent refresh token or client secrets, don't install or create a Spotify app with limited permissions and revoke the app credentials after testing. Finally, because the registry metadata omits these requirements, ask the publisher to correct the manifest (declare Node and required env vars) before trusting it.Like a lobster shell, security has layers — review code before you run it.
latestvk97e3qs5t1vbmkvtv45ypes0x9844f3x
License
MIT-0
Free to use, modify, and redistribute. No attribution required.