Last.fm

**Judgement:** This skill is a solid, well-documented Last.fm API wrapper for read-only data. It exposes a broad set of endpoints that cover most practical needs around listening stats and music discovery, with straightforward configuration via environment variables. **Strengths & Benefits** - Broad coverage of Last.fm read-only features: recent tracks, user stats, top artists/albums/tracks, loved tracks, weekly charts, artist/track/album info, similar artists/tracks, search, tags, and global charts. - Clear usage model: all endpoints share the same base URL and common parameters, with many concrete curl examples. - Read-only, API-key–based access (no OAuth) lowers implementation complexity and reduces risk of destructive actions. - Good fit for building music-aware agents that can answer questions like “What have I been listening to?” or “Recommend similar artists.” **Risks & Limitations** - **External dependency:** All functionality depends on Last.fm’s API uptime, latency, and any undocumented rate limits. - **Configuration coupling:** The skill uses a single `LASTFM_USER` value from the environment, making it naturally suited to one primary account; multi-user or per-request user selection is not evident from the docs. - **Error/rate-limit handling:** Implementation details for handling network errors, invalid API keys, or rate limiting are not visible and may require additional guardrails at the caller level. - **Privacy considerations:** Accessing detailed listening history for a user can be sensitive; API keys and user configuration should be stored securely and only used for accounts where you have permission. **Recommended Scenarios** - Personal or single-account assistants that analyze and summarize a user’s Last.fm listening history and trends. - Chatbots that can answer questions about current or recent tracks, top artists over different periods, or “year in review” style summaries. - Music discovery tools that surface similar artists/tracks, tag-based recommendations, or global charts for editorial content. - Data exploration workflows where the raw JSON is further processed (e.g., with `jq` or in notebooks) for custom visualizations or reports.