agentleFS
Panchangam18Panchangam18/background-computer-use/skills/spotify/SKILL.md

spotify

Skill4 starsChanged 7 months agoMITView on GitHub

Spotify desktop heuristics for background-computer-use. Use when the user asks you to pause, skip, search, queue, or otherwise control Spotify without stealing focus.

19 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use sonos, heartmula and 10 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.
  • emanueleieloSkill

    sonos

    Control Sonos speakers: discover, play/pause, volume, grouping, favorites, and queue management via sonos CLI.

    Also in 4 projects that use this

  • 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

  • emanueleieloSkill

    imessage

    Send and read iMessage/SMS via Messages.app using the imsg CLI. List chats, view history, send messages to phone numbers or Apple IDs.

    Also in 5 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

  • +1 more from emanueleielo

The file

We split this skill into the rules it gives an agent

1 rule. 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 19 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

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

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

    Always call get_app_state app="Spotify" before interacting.

    line 11

“Common” is measured: kept by at least 6 in 10 of the 19 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

Driving Spotify with background computer use

Spotify is Electron + WebView, so accessibility coverage is partial. Mix element indexes with coordinate and keyboard fallbacks.

  1. Always call get_app_state app="Spotify" before interacting.
  2. Trust post-action snapshots, not pre-action ones — the UI lags real playback state by 300–800 ms.
  3. Transport controls have reliable keyboard shortcuts; prefer them over coordinate clicks:
    • space — play/pause
    • command+Right / command+Left — next / previous
    • command+Up / command+Down — volume up / down
  4. For search, try set_value on the search field first. If it silently fails, click the field, press_key key="command+a", then type_text.
  5. Track rows advertise ShowMenu as a secondary action for queue / add-to- playlist. Re-read state after the menu opens.

Detailed notes live in server/app-hints/Spotify.md; they are injected as <app_hints> on every get_app_state call for Spotify.

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.