The material says there are no environment variables or API keys, but the README mentions importing Spotify-related browser cookies via `spogo auth import --browser chrome`, and `spotify_player` may use a user `client_id` in config. This means the tool can handle account authentication material; while typical for this category, cookie, client_id, and local config leakage should be guarded against.

The checks show no declared remote endpoint, but the tool’s purpose is Spotify playback/search, so the underlying client will inherently communicate with Spotify services. There is no evidence in the material of exfiltration to unknown or unrelated third-party endpoints, so this appears to be ordinary network use consistent with its stated function.

The system classifies it as prompt-only; the material is primarily usage guidance and does not describe the Skill itself installing, downloading, or executing arbitrary code. While it instructs users to invoke locally installed `spogo`/`spotify_player`, the Skill itself does not appear to add execution privileges based on the provided material.

The README explicitly references the config directory `~/.config/spotify-player` and involves browser cookie import plus reading/writing user configuration (such as `app.toml` and `client_id`). This is local data access aligned with its function, and there is no evidence of broader system access beyond the stated use.

The source is an open-source GitHub repository, and the system marks it as open-source with extremely high community adoption (~377k stars), which are strong risk-lowering signals. The license and maintenance status are not explicit, and the README references two external tools (`spogo` and `spotify_player`), so actual install sources should still be verified, but no clear supply-chain red flags are evident from the current material.