Connector Spotify

by caffeinelabs362f51ae96f0No license2 starsListed Oct 8, 2026Updated Oct 8, 2026Repository updated today

MANDATORY recipe for every Caffeine build that reads Spotify catalog data or drives a user's Spotify account from a canister. The supported path is the `spotify-client` mops package (Spotify Web API) over outbound HTTPS with an OAuth 2.0 bearer token minted off-chain. Hand-rolling `ic.http_request` calls to `api.spotify.com` is a FORBIDDEN anti-pattern — it bypasses the non-replicated-outcall safeguard (player state and `progress_ms` differ per node and fail consensus), the generated JSON decoding, and the bearer handling. Load this skill whenever the user, spec, or any prior task mentions Spotify, a song, track, artist, album, playlist, music search, new releases, genres, markets, "what's playing", recently played, the queue, player controls (play / pause / skip / shuffle / repeat), a saved library, podcasts (shows or episodes), chapters or audiobooks — and BEFORE writing any code that touches a Spotify endpoint.

  1. 362f51ae96f0Currentcommit 362f51aPublished Oct 8, 2026

Source and attribution

Source:caffeinelabs/skillsinskills/connector-spotifyat commit362f51a

License: No license

Content belongs to its original authors. SourceWeft indexes it from a public repository.

Report or request removal