spotify-playlist-curator@1.0.4
CAUTION· static onlyPublisher claims: "Create and refine Spotify playlists using the Spotify Web API, with support for track search, recent and top listening lookups, queueing selected tracks, and..." Observed in sandbox: static analysis only — behavior not yet observed.
Coverage
Static only; nothing was run yet.The label rests on the code, the instruction files and the publisher. The honeypot run replaces this verdict when it completes.
Is [email protected] safe to install?
KillerSkills analysed it statically (a sandbox run is pending) on 2026-11-14 and scored it 56/100 (Caution). It is not known to be malicious, but it has behaviour or code a security policy should decide on before install. Notable findings: Privileged sudo command; Access to sensitive file paths; Latin word with Cyrillic or Greek look-alike letters (homoglyph). Summary: static analysis only — behavior not yet observed.
Behavior trace
Queued for honeypot run · static analysis onlyThis version has not been detonated yet. The score above counts behavior as unknown (50/100), so it cannot read Verified until the honeypot run completes and replaces this verdict.
Static findings
echo " Ubuntu: sudo apt install python3 python3-venv" >&2Fix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.… tell the user | |---|---|---| | `invalid_client` or "client ID invalid" | The `.env` file has placeholder values or incorrect credentials | Open `.env` in the skil…Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.ΔenergyFix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.| `credentials not found` or "placeholder values" | Setup ran but user didn't edit `.env` | Same as above — they need to create a Spotify app and paste the credentials |Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.| `credentials not found` or "placeholder values" | Setup ran but user didn't edit `.env` | Same as above — they need to create a Spotify app and paste the credentials |Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose."Create a .env file in the skill root with:\n"Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose."Then fill in .env with SPOTIPY_CLIENT_ID and SPOTIPY_CLIENT_SECRET."Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.script_dir / ".env",Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.echo " 2. Fill in your credentials in .env"Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.echo "Created .env at $ENV_FILE"Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.ENV_FILE="$SKILL_DIR/.env"Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.cwd / ".env",Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.echo "Warning: .env exists but may be missing SPOTIPY_CLIENT_ID or SPOTIPY_CLIENT_SECRET."Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.skill_dir / ".env",Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose."Spotify credentials in .env are still set to placeholder values.\n\n"Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.echo "Fill in your credentials in .env, then authenticate:"Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose." 1. The .env file still has placeholder values (your_client_id_here)\n"Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose." To fix: open the .env file in the skill root, verify your credentials\n"Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.Cost to the agent
Tokens estimated at four characters each. Skills load their instruction text when triggered; the figure is what that costs.
Known vulnerabilities
Vulnerability advisories (OSV) cover npm and PyPI packages; this registry has no advisory database.
What would make this Verified
24 points to 80 · weights: behavior 45%, static 25%, prompt 15%, publisher 15%- Unclaimed publisher≈ +8 on the totalClaim rachel-howell: a verified publisher gets +50 on publisher trust. It is free and usually instant with GitHub sign-in.
- Privileged sudo command≈ +4 on the totalBuild commands from fixed arguments; do not interpolate untrusted strings into a shell.
- Access to sensitive file paths≈ +4 on the totalStop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
- Prompting user to enter sensitive credentials≈ +4 on the totalStop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.