skills/spotify-player/SKILL.md
Terminal Spotify playback/search via spogo (preferred) or spotify_player.
npx skillsauth add steipete/clawdis spotify-playerInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
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.tools
# Lobster Lobster executes multi-step workflows with approval checkpoints. Use it when: - User wants a repeatable automation (triage, monitor, sync) - Actions need human approval before executing (send, post, delete) - Multiple tool calls should run as one deterministic operation ## When to use Lobster | User intent | Use Lobster? | | ------------------------------------------------------ | --------------------------
development
Maintainer-only workflow for handling GitHub Secret Scanning alerts on OpenClaw. Use when Codex needs to triage, redact, clean up, and resolve secret leakage found in issue comments, issue bodies, PR comments, or other GitHub content.
development
Maintainer workflow for OpenClaw releases, prereleases, changelog release notes, and publish validation. Use when Codex needs to prepare or verify stable or beta release steps, align version naming, assemble release notes, check release auth requirements, or validate publish-time commands and artifacts.
development
Run, watch, debug, and extend OpenClaw QA testing with qa-lab and qa-channel. Use when Codex needs to execute the repo-backed QA suite, inspect live QA artifacts, debug failing scenarios, add new QA scenarios, or explain the OpenClaw QA workflow. Prefer the live OpenAI lane with regular openai/gpt-5.4 in fast mode; do not use gpt-5.4-pro or gpt-5.4-mini unless the user explicitly overrides that policy.