--- name: win4r-spotify description: "Discover, search, and manage Spotify music, podcasts, and playlists, including deleting shows or episodes you created with Save to Spotify." metadata: decimalai-skill-id: "fa43f1c9-42cf-43c5-be5b-382cd8c4bf58" decimalai-version-id: "31294f68-82b3-488a-9616-dd294f0e93a5" decimalai-version: "1" decimalai-body-sha256: "6c4889a649867fe7ae4bdd73a8a76e916c303c1fe08f0d3c6c87abd44b470801" decimalai-name: "win4r/spotify" decimalai-format: "1" decimalai-invocation: "model" decimalai-category: "design-media" decimalai-source: "https://app.decimal.ai/s/win4r-spotify@1/SKILL.md" --- # Spotify ## Purpose Use `spotify-api` to browse personalized Spotify content, search for music and podcasts, manage the user's library and playlists, and check saveability of items. Use `save-to-spotify` to manage shows and episodes you created through Save to Spotify. ## Tooling Use the installed CLI directly from `PATH`. #### Connection - `spotify-api status` — check OAuth connection status (`status`, `connect_url`, `disconnect_url`) - `spotify-api disconnect` — disconnect Spotify (may return a confirmation URL) - `spotify-api authorize-url` — get the active environment's connect URL #### Browse & Discover - `spotify-api experience --id [--language ]` — get experience by ID (e.g. artist/album/show page). Large sections may include a `next` URL for more results. - `spotify-api next-page --url [--language ]` — fetch the next pagination URL returned as `sections[].next` or `next` by a prior Spotify response. Prefer this over guessing section IDs. #### Search - `spotify-api search --query [--search-type TRACKS,ALBUMS,ARTISTS,PLAYLISTS,EPISODES,PODCASTS] [--language ]` — search for content. For an exact song or album lookup, always format the query as `" by "` so missing originals are distinguished from covers and similarly named content. Use `PODCASTS` to find shows (not `SHOWS` which is invalid). Use `experience --id ` to list episodes of a found show. - Search responses include `spotify_search_url` for opening the same query directly in Spotify. When an exact requested item is unavailable, `catalog_fallback.message` is the fully rendered approved response and must be relayed verbatim; the object also provides `requested_content_label`, `requested_content_url`, `artist_name`, and `artist_url`. #### Filter values - Valid library/browse filter values are `ALBUMS`, `ARTISTS`, `PLAYLISTS`, `EPISODES`, `PODCASTS`, `SHOWS`, and `PODCASTS_AND_SHOWS`. - These filter values are content categories, not field projections. Never use field names such as `title`, `items.title`, `sections`, or `items` as `--filter` values. - `TRACKS` is explicitly rejected for library filtering; use unfiltered `spotify-api library` or `spotify-api search --search-type TRACKS` to find tracks. #### Library - `spotify-api library [--filter ALBUMS|ARTISTS|PLAYLISTS|EPISODES|PODCASTS|SHOWS|PODCASTS_AND_SHOWS] [--language ]` — browse user's library. `TRACKS` is not supported as a library filter; use unfiltered `library` or `search --search-type TRACKS` instead. - `spotify-api save --uri ` — save item to library (track, album, artist, show, episode, playlist) #### Delete Save to Spotify shows or episodes - When the user asks to delete a podcast, show, or episode Muse added through Save to Spotify, use the installed `save-to-spotify` CLI. These are managed by the CLI, not `spotify-api`, `podcasters.spotify.com`, or `creators.spotify.com`. - If `save-to-spotify` reports that show and episode management is unavailable, explain the limitation directly; do not ask the user to reconnect or retry. - Always use JSON mode. Start with `save-to-spotify --json shows`; this inventory contains the shows created through Save to Spotify. Match by title and ask the user to disambiguate if more than one show matches. - Inspect the selected show with `save-to-spotify --json shows get `. List its episodes when needed with `save-to-spotify --json episodes --show-id ` and match episodes by title. - To delete one episode, resolve its title and owning show unambiguously, then run `save-to-spotify --json episodes delete --show-id `. - To delete the whole show, resolve the show unambiguously and tell the user that all of its episodes will be removed, then run `save-to-spotify --json shows delete `. This command deletes the show and its episodes; do not delete each episode first. - A `{"status":"deleted"}` response means Spotify accepted the deletion, but its listings can take about a minute to update. Poll the relevant inventory every 5–10 seconds for up to 60 seconds: use `episodes --show-id ` for an episode or `shows` for a show. Confirm completion only after the deleted ID is absent. If it is still listed after 60 seconds, tell the user the deletion was accepted and is still propagating; do not send the delete again. - Show and episode IDs are internal command handles. Refer to content by title in user-facing replies. A CLI deletion removes the Spotify copy only; it does not delete Muse's local audio or an independently published RSS feed. #### Collections (Playlists) - `spotify-api create-collection --name ` — create a new playlist - `spotify-api add-to-collection --collection-uri --uris [--position-type BEFORE_UID|AFTER_UID --position-uid ] [--revision-id ]` — add items to a playlist - `spotify-api update-collection --collection-uri --name ` — rename a playlist #### Playback Control - `spotify-api play [--context-uri ] [--uid ] [--target-device-id ]` — start playback (optionally of a specific album/playlist/context, starting from a specific item UID, on a specific device) - `spotify-api pause` — pause playback on the active device - `spotify-api resume` — resume paused playback on the active device - `spotify-api skip` — skip to the next item - `spotify-api previous` — go to the previous item - `spotify-api seek --position-ms ` — seek to a position in the currently playing item - `spotify-api set-volume --volume-percent <0-100> [--target-device-id ]` — set playback volume - `spotify-api transfer --target-device-id ` — transfer playback to a different device - `spotify-api now-playing` — get the current playback state (track, progress, device, etc.) - `spotify-api devices` — list available Spotify Connect devices - `spotify-api get-queue` — get the current playback queue - `spotify-api add-to-queue --item-uri ` — add an item to the playback queue #### Wearable (glasses) playback - `spotify-api wearable-play [--query ] [--uri ]` — resolve a track and emit the `music_fulfillment` node-command params for a glasses cold-start. This is the command to use when the playback request originates from wearables/glasses. It does **not** itself start playback: it resolves the request to an allowlisted Spotify URI and returns `node_command` (`"music_fulfillment"`) plus `node_params` (`{action_name:"play", partner_name:"spotify", interaction_id, partner_payload:}`). Pass those straight into `devices invoke music_fulfillment`, which routes to the on-device partner-fulfillment engine (c50 → glasses → Spotify over EA/iAP2). Prefer `--uri` when you already have a Spotify URI. For free text, use the unambiguous form `--query " by "`; this prevents a blocked original from resolving to a cover or karaoke track. Fails closed with `not_connected` if Spotify is not linked. If Spotify returns no matching playable track, it returns `not_found` plus `catalog_fallback`; do not invoke the device in that case. Unlike `play`/`add-to-queue`, this does **not** require a Spotify Connect device — it cold-starts the app on the glasses. - Invoke exactly once on the node whose command list advertises `music_fulfillment`; on the current test VM this is `Meta Glasses 00R9`, not Pixel. Do not try Pixel first unless Pixel explicitly advertises `music_fulfillment`, and do not retry on another device after a timeout — the glasses wake-up path can time out in Muse while still waking c50 and starting playback. Verify with `spotify-api now-playing` or user audio confirmation instead of retrying. #### Known unavailable or conditional commands - `home`, `recommendations`, `check-saved`, `remove`, `section-items`, and `reorder-collection` are not exposed by `spotify-api` because they are unsupported or unreliable with the current Partner API responses/scopes. Use `search`, `library`, `experience`, `next-page`, and playlist create/add/update instead. This does not apply to shows and episodes created through Save to Spotify; delete those with `save-to-spotify` as described above. - `play` and `add-to-queue` require an active Spotify Connect device; use `spotify-api devices` first and prefer an explicit `--target-device-id` where supported. `set-volume` should also prefer `--target-device-id`. ## Auth `spotify-api` owns the Spotify connection workflow. Auth contract: - Run `spotify-api status` first. - If not connected, run `spotify-api authorize-url`. Present the returned URL as a hyperlink with the text `[Connect to Spotify]()`; do not show or paste the raw URL. - If playlist changes stop working after a reconnect, re-link so the token is minted with the latest requested scopes. - If the user wants to disconnect, run `spotify-api disconnect`. When `disconnect_url` is present, replace `` with the returned URL and share only this Markdown link: `[Disconnect Spotify]()`; explain that the user must open it to confirm. When no URL is returned and the command succeeds, `spotify-api status` may be used to verify the disconnection. - Do not pass secrets on the command line. ## Operating Rules 1. Verify connection with `spotify-api status` before `spotify-api` data calls. For Save to Spotify management, start with `save-to-spotify --json shows`; if it reports a token or connection error, ask the user to connect Spotify in Settings → Connections → Spotify, then retry. If it reports that management is unavailable, do not present reconnection as a fix. 2. Browse with `search`, `library`, and `experience`. Extract relevant items; never dump full responses. 3. When a section includes `next`, call `spotify-api next-page --url ` to fetch additional pages. Continue following `next` until it is absent or the user has enough results. 4. The documented Save to Spotify show and episode deletions may proceed from a clear, unambiguous user request without an additional confirmation. Do not promise unsupported `spotify-api` cleanup (unsave/remove, playlist deletion, remove-from-playlist, or reordering). 5. Playback requires an active Spotify Connect device. Run `spotify-api devices` or `spotify-api now-playing` first and prefer an explicit `--target-device-id` where supported. 6. Every response referencing existing Spotify content must include a Spotify deep link. Use `spotify_url`, or construct `https://open.spotify.com/{type}/{id}` from `spotify_uri`. A Save to Spotify deletion confirmation is the exception: the resource no longer exists, so name the deleted title without exposing its internal ID or constructing a dead link. 7. Reference Spotify by name ("on Spotify" / "via Spotify") whenever you surface content or confirm an action. 8. Flag explicit content: when `is_explicit: true`, show `[E]` next to the title. 9. After any playback change (`play`, `skip`, `previous`, `resume`), follow up with `now-playing` and name the track plus creator; never confirm with only a device name. 10. A successful playback response means the action took effect. If playback still errors after CLI retries, surface it once in plain user-facing language. If an action is not available, point the user to the Spotify app rather than speculating. 11. If an exact song or album by an artist is missing from search, or a known Spotify item cannot be resolved for playlist or playback actions, do not substitute a cover, tribute, karaoke, or similarly named item. Relay `catalog_fallback.message` verbatim; it already renders the approved Muse copy with Markdown links to the requested content search and the exact artist page. Do not add a cause, preamble, follow-up, or alternative wording; blame the user's account; suggest reconnecting; or claim the item was removed from Spotify.