7.8
/ 10
1 evaluations
2.2k Downloads
Overview
Provide programmatic access to a user’s Spotify listening data—recent history, top artists/tracks over various time ranges, and Spotify-based recommendations—via prebuilt Python scripts wrapping the Spotify Web API.
Key Advantages
1.Covers the most common Spotify-personalization workflows out of the box: recent history, top artists, top tracks, and recommendations.
2.Includes a guided setup script to create a Spotify developer app, securely store client credentials, and perform OAuth authorization.
3.Token storage and refresh are handled automatically via a local token file, reducing recurring friction after initial setup.
4.Supports both browser-based and headless authentication flows, making it usable on servers or remote environments.
5.Provides a generic JSON endpoint wrapper so agents can hit arbitrary Spotify Web API endpoints when advanced queries are needed.
Use Cases
- Answer user questions like “What have I been listening to lately?” by fetching recent play history.
- Surface a user’s top artists or tracks over short, medium, or long-term windows to analyze music taste or trends.
- Generate personalized music recommendations based on the user’s top artists/tracks, then enrich with the model’s own music knowledge.
- Build conversational features around current playback state (what’s playing now, playback context) using the supported scopes.
- Perform custom Spotify Web API queries (via the json subcommand) for advanced or niche music data use cases.
Evaluation Scores
7.8
/ 10
Reliability
7.5
Functionality
8.0
Usability
7.5
Safety
7.5
Performance
8.0
Compatibility
8.5
Based on 1 evaluation · Latest: 3/20/2026
Download Trend
Loading...
Evaluation History (1)
7.8/103/20/2026▼
OS: linux-arm64LLM: anthropic/claude-haiku-4.5
**Quick judgement**
A solid, focused Spotify integration skill that gives an agent access to personal listening history, top artists/tracks, and recommendation endpoints with minimal custom coding. It is well-aligned with music-centric assistants and analysis/recommendation tasks, assuming the environment can handle OAuth and local token storage.
**Strengths**
- Good coverage of core Spotify personalization features (recent history, top items, recommendations) plus a raw JSON endpoint mode for flexibility.
- Sensible one-time setup flow with a wizard script and clear manual instructions for credentials and OAuth.
- Token management (storage + refresh) is handled for you, improving day-to-day reliability once configured.
- Supports both browser and headless auth, so it can work on desktops, servers, or remote terminals.
**Risks & limitations**
- **Privacy & security**: Accesses sensitive personal listening data and stores OAuth tokens and client secrets locally; improper filesystem permissions or credential handling by the user could expose accounts.
- **Setup complexity**: Requires creating a Spotify Developer app, configuring redirect URIs exactly, and running auth scripts—non-trivial for non-technical users.
- **External dependency**: Fully dependent on Spotify’s Web API availability, rate limits, and policy changes; breaking API changes or revoked credentials will break the skill.
- **Scope-limited**: Focuses on user-centric endpoints; broader catalog/search or playlist editing workflows would need additional tooling.
**Recommended scenarios**
- Personal assistant setups where the user explicitly wants their Spotify history, top artists, or top tracks queried and discussed.
- Agents that generate or refine music recommendations based on a user’s real listening patterns, augmenting API results with model knowledge.
- Music analytics or journaling workflows (e.g., periodic “monthly listening report” or taste evolution over time) that leverage the time-range top endpoints.
- Integrations that need lightweight access to current playback state or recently played items as context for other actions or content generation.
Comments (0)
No comments yet. Be the first!