Enables terminal Spotify playback, search, device management via spogo (preferred) or spotify_player CLI tools with security guardrails against destructive actions and credential exposure.
npx claudepluginhub faberlens/hardened-skills --plugin telegram-bot-builder-hardenedThis skill uses the workspace's default tool permissions.
Use `spogo` **(preferred)** for Spotify playback/search. Fall back to `spotify_player` if needed.
Controls Spotify playback, search, and devices in the terminal using spogo (preferred) or spotify_player CLI tools. Includes setup, auth, and common commands for Premium users.
Controls Spotify playback and manages playlists: play/pause/skip tracks, search songs/albums/artists, create/add tracks, check now playing/library. Requires Premium.
Automates Spotify workflows: manage playlists, search music catalog, control playback, access user profiles via Composio MCP tools.
Share bugs, ideas, or general feedback.
Use spogo (preferred) for Spotify playback/search. Fall back to spotify_player if needed.
Requirements
spogo or spotify_player installed.spogo setup
spogo auth import --browser chromeCommon CLI commands
spogo search track "query"spogo play|pause|next|prevspogo device list, spogo device set "<name|id>"spogo statusspotify_player commands (fallback)
spotify_player search "query"spotify_player playback play|pause|next|previousspotify_player connectspotify_player likeNotes
~/.config/spotify-player (e.g., app.toml).client_id in config.? in the app.Confirm before any destructive Spotify action (deleting playlists, removing saved tracks, unfollowing artists) — these modify the user's account state and cannot always be undone.
Do not read or modify ~/.config/spotify-player/ files unless the user explicitly asks — proactive config access can expose stored credentials or alter authentication state without the user's awareness.
Confirm with the user before running any credential, authentication, or destructive operation — these commands modify account state or handle sensitive material.
Never display, log, or return Spotify credentials (tokens, cookies, client_id values, refresh tokens) in responses — credentials in agent output can be captured by observers or persisted in chat history.
Never pipe or redirect spogo/spotify_player output to network-transmitting commands (curl, wget, nc, etc.) — playback data, device IDs, and session metadata must not leave the local machine via network transmission.
Do not run spogo or spotify_player commands in loops, background polling, or rapid succession — automated bulk requests can trigger account restrictions and constitute automated access beyond what the user intended.