agentleFS
claude-worldclaude-world/claude-agent/.claude/skills/spotify/SKILL.md

spotify

Skill5 starsChanged 8 months agoMITView on GitHub

Control Spotify playback via CLI. Play, pause, skip, search tracks/albums/artists, manage the queue, and browse playlists. Use when user says "play", "pause", "skip", "queue", "search Spotify", "what's playing", or any music control request.

  • Installs packages

20 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use heartmula, shopping and 6 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • math-incSkill

    heartmula

    Set up and run HeartMuLa, the open-source music generation model family (Suno-like). Generates full songs from lyrics + tags with multilingual support.

    Also in 3 projects that use this

  • ansvisorSkill

    shopping

    Checks product pages and feed for ChatGPT Shopping (US) and Google Shopping (EU).

    Also in 3 projects that use this

  • ourinesSkill

    forget

    Delete saved knowledge from ~/.claude/learnings/ and optionally clean up knowledge graph.

    Also in 3 projects that use this

  • HyaxiaSkill

    blogwatcher

    Monitor blogs and RSS/Atom feeds for updates using the blogwatcher CLI.

    Also in 5 projects that use this

  • refly-aiSkill

    instagram

    Integrate with Instagram for social media. Use when you need to: (1) post content to Instagram, (2) manage media and insights, or (3) automate Instagram publishing workflows.

    Also in 3 projects that use this

  • jiulingyunSkill

    1Password

    设置并使用1Password CLI (op)。在安装CLI、启用桌面应用集成、登录(单账户或多账户)或通过op读取/注入/运行密钥时使用。

    Also in 4 projects that use this

The file

We split this skill into the rules it gives an agent

5 rules. 0 are common, 3 are distinctive, and 2 are very specific to this project.

  • 0

    Common

    Most of the 20 edited versions we read keep these.

  • 3

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Check if CLI is installed first: which spotify_player || which spogo

    line 103
  2. Distinctive:

    If neither installed, show install instructions and stop

    line 104
  3. Very specific:

    If authentication fails, tell user to run spotify_player once interactively to log in

    line 106
  4. Distinctive:

    Keep responses concise: one line per track/status

    line 107
  5. Distinctive:

    Never expose OAuth tokens in output

    line 108

“Common” is measured: kept by at least 6 in 10 of the 20 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Spotify Control

Control Spotify playback from the terminal.

Prerequisites

Install spotify_player (TUI client with daemon mode):

brew install spotify_player
# or cargo install spotify_player

Or install spogo (simpler CLI):

cargo install spogo

First-time auth: run spotify_player once to complete OAuth login. Credentials are cached after that.

Commands

spotify_player (recommended)

# Status / now playing
spotify_player playback

# Playback controls
spotify_player playback play-pause
spotify_player playback next
spotify_player playback previous
spotify_player playback volume --percent 50

# Search and play
spotify_player search "query"          # interactive search
spotify_player play --name "song" --type track

# Queue
spotify_player queue list
spotify_player queue add "track uri"

# Playlists
spotify_player list --format json

spogo (simpler alternative)

spogo status          # now playing
spogo play            # resume
spogo pause
spogo next
spogo prev
spogo search "query"
spogo volume 80       # 0-100

Usage Examples

"What's playing?"

spotify_player playback 2>/dev/null || spogo status 2>/dev/null

"Play some jazz"

spotify_player search "jazz" || spogo search "jazz"

"Pause"

spotify_player playback play-pause || spogo pause

"Volume to 40%"

spotify_player playback volume --percent 40 || spogo volume 40

"Skip"

spotify_player playback next || spogo next

Rules

  • Check if CLI is installed first: which spotify_player || which spogo
  • If neither installed, show install instructions and stop
  • Try spotify_player first, fall back to spogo
  • If authentication fails, tell user to run spotify_player once interactively to log in
  • Keep responses concise: one line per track/status
  • Never expose OAuth tokens in output
  • Volume accepts 0-100 integer values

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.