菜单
Control Spotify playback: play, pause, skip, search tracks/albums/playlists, manage devices and queue via spogo CLI.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/emanueleielo/ciana-parrot --skill spotify命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
基于 SOC 职业分类
正在显示 SKILL.md
| name | spotify |
| description | Control Spotify playback: play, pause, skip, search tracks/albums/playlists, manage devices and queue via spogo CLI. |
| requires_bridge | spotify |
Use the spotify bridge to control Spotify playback via spogo on the host.
spogo commands through host_execute. Never run sleep, echo, or any non-spogo command through the spotify bridge — they will be blocked by the gateway allowlist.spogo play — run spogo status --json and check that is_playing is true and the correct track is loaded. Never tell the user "it's playing" without verifying.--device flag when targeting a specific device, especially if spogo play fails with "missing device id".All commands run via host_execute(bridge="spotify", command="...").
IMPORTANT: spogo play requires a Spotify URI, not a name. Follow this exact sequence:
spogo search track "song name" --json (or artist/album/playlist)uri field from the first resultspogo play <uri>spogo status --json — check is_playing: true and correct track nameis_playing: false, see "Known Issues" belowspogo status # What's playing (text)
spogo status --json # What's playing (JSON, use for verification)
spogo play <uri> # Play a specific URI
spogo play <uri> --device "MacBook Air" # Play on a specific device
spogo pause # Pause
spogo next # Next track
spogo prev # Previous track
Always use --json to get URIs for playback.
spogo search track "bohemian rhapsody" --json
spogo search album "dark side of the moon" --json
spogo search artist "radiohead" --json
spogo search playlist "chill vibes" --json
spogo device list --json # List devices (use JSON to check is_active)
spogo device set "Living Room" # Switch device
spogo auth status # Check if authenticated
spogo auth import --browser chrome # Import cookies from Chrome
spogo auth import --browser safari # Import cookies from Safari
After Spotify restarts, all devices show is_active: false. In this state:
spogo play <uri> returns "Playback started" but does nothing (false success)Detection: After spogo play <uri>, run spogo status --json. If is_playing is still false or the track didn't change, the device is not active.
Workaround: Tell the user: "Spotify needs to be activated first — press play once in the Spotify app, then I can take over."
spogo play (resume) often fails with 403 Forbidden. This is a spogo/Spotify API bug.
Workaround: Never use spogo play without arguments. Instead:
spogo status --jsonspogo play <item.uri>Happens when no device is active and spogo can't auto-select one.
Workaround:
spogo device list --json to find available devices--device flag: spogo play <uri> --device "Emanuele's MacBook Air"is_active: false, tell the user to open Spotify and press play onceSpotify API has rate limits. If you get a 429 error, wait a moment before retrying. Do NOT try to run sleep via host_execute — just tell the user you'll retry in a moment and try the command again on the next message.
If a Spotify command fails, follow this sequence:
spogo auth status to check authenticationsp_dc cookie is missing/expired, run spogo auth import --browser chromeopen.spotify.com in Chrome, then retryspogo device list --json — if all is_active: false, tell user to activate Spotify manually onceAlways try via host_execute first. Only suggest manual steps if host_execute itself fails.
brew install steipete/tap/spogospogo auth import --browser chrome (or let Ciana do it)