agentleFS
cpodercpoder/claude-apple-plugin/skills/apple-music/SKILL.md

apple-music

Skill0 starsChanged 30 days agoMITView on GitHub

Apple Music API reference for the apple plugin — catalog search, songs/albums/artists/playlists lookup, charts, storefronts, and (with a Music User Token) the user's library, recently played, recommendations, playlist creation. Load for any music_* tool or Apple Music / MusicKit question.

5 other projects use a version of this.

Adopted by

Most recently taken up by

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 5 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:

    Search hints/suggestions: GET /v1/catalog/{sf}/search/suggestions?term=…&kinds=terms,topResults.

    line 26

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

Apple Music API (tools music_*)

Developer token: ES256 JWT (iss = team id, kid = MusicKit key id) valid up to 6 months — the server mints one for 12 h from music.key_id/team_id/private_key. Catalog calls need only this token. Anything under /v1/me/... additionally needs a Music User Token (music.user_token), obtained in a client with MusicKit (MusicKit.getInstance().authorize() on the web, MusicAuthorization.request() + DefaultMusicTokenProvider on Apple platforms); user tokens expire after ~6 months.

Storefront: two-letter code (fr, us, gb, jp...), default music.storefront; music_library kind=storefront returns the user's own. l=fr-FR localizes names.

Catalog

  • music_search term="…" types=songs,albums,artists,playlists (limit ≤25 per type).
  • music_get resource_type=albums id=<id> relationship=tracks; artists: views=top-songs,latest-release; multi-get with comma-separated ids. Song ISRC lookup: music_request GET /v1/catalog/fr/songs?filter[isrc]=….
  • music_charts types=songs,albums genre=21 (genre ids via music_request GET /v1/catalog/fr/genres), city charts chart=city-chart-paris... (check /v1/catalog/{sf}/charts?types=…&with=cityCharts).
  • Search hints/suggestions: GET /v1/catalog/{sf}/search/suggestions?term=…&kinds=terms,topResults.
  • Stations: types=stations; curators and editorial playlists via curators, apple-curators.
  • Equivalents in another storefront: GET /v1/catalog/{sf}/songs?filter[equivalents]=<id>.

Library (user token)

music_library kind=songs|albums|artists|playlists|recently-added|recently-played|recommendations|heavy-rotation; music_library_add resource_type=songs ids=…; music_playlist_create name=… track_ids=…; music_playlist_add_tracks playlist_id=p.xxx track_ids=…. Rating: PUT /v1/me/ratings/songs/{id} {"attributes":{"value":1}} (1 love, -1 dislike). Library ids start with i. (songs) / p. (playlists) and only work with user-token endpoints.

Output

compact (default) replaces artwork objects by a 300×300 URL and drops playParams/previews. Pass compact: false to music_request for everything. Responses paginate with next (relative URL — pass it as path to music_request).

Errors: 401 → token/team/key mismatch or MusicKit not enabled on the key; 403 on /me → user token missing/expired. Docs: apple_docs_index technology=applemusicapi.

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.